Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Source tree keeps asking for password when execute pull/push commond

When excute git pull/push commond, the source tree keeps asking for my password as the following picture showed, but in the terminal, the git pull/push commond works well and dose not asking for the password, could anyone tell me why, many thanks!

5 answers

Is it possible that your terminal is configured to use a keypair, but SourceTree isn't?

Hey rui,

Looks like your URL format might be wrong. Could you post a redacted version in its current format?

Thanks in advance

I had the same problem and basically just you need to delete the passwords in your keychain.

After that, try to add a repository and click in the icon in the right (world icon)

You will be asket to insert your password and login again...

That's it

;)

I'm having the exact same issue.  I've tried every solution people have posted on the internet:

  • delete keychain pw
  • change the repo url to include the username (https://username@host.com/path/to/rep.git)
  • Go to Repository > Repository Settings > Remotes — click the repo path and hit edit, add your username there so Keychain can find the appropriate pw.
  • In the repo list view, go to Accounts and set the pw there

NOTHING works.  Every time I fetch, push, pull, whatever, it still asks me for my damn password. Every. Single. Time.  The Store Password In Keychain checkbox does nothing, and I'm supplying my username all over the place, so keychain needing that bit of info ahead of time in order to work is also not the solution.  This problem never happened until I recently did an update.  According to the About info, I'm running version 2.4 (88) now.  So, whatever that upgrade did must've introduced this problem.  This is REALLY annoying. 

Did you ever resolve this? I'm having this issue now as well.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in DevOps

Step up your DevOps game webinar Q&A series - Questions answered!

  On October 21st, 2020 we hosted a webinar titled,   Step Up You DevOps Game with 4 Key Integrations for Jira and Bitbucket. We had a great showing and high engagement, but that meant th...

118 views 0 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you