You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Out oif the blue, SourceTree keeps asking about my credentials for Bitbucket repo, even though they were already set. It does not seem to remember the password in Keychain?
So, I removed all the accounts from SourceTree, and added them back, maiking sure to create the SSH key from SourceTree (and copying in Bitbucket Settings).
However, this is still not enough: existing repo in SourceTree can not still connect properly. For one repo, I was able to remove the clone in SourceTree, and re-cloned: this worked.
but for other repo, I have work in progress that I do no want to lose.
Hi Eric, welcome to the Community!
Have you changed your machines recently? If you're using the same machine, it could be that the SSH key agent "forgot" the key for some reason, in that case you'll need to re-add it. To find out, you can run the following command in the terminal and see if it returns anything:
If the key is not there, you can re-add it doing:
Let us know if that worked!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.