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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

SourceTree can not login with Bitbucket

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.

Very painful.

1 answer

0 votes
Ana Retamal
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 01, 2019

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:

ssh-add -l

If the key is not there, you can re-add it doing:

ssh-add <path_to_key>

Let us know if that worked!

Kind regards,


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events