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

Authentication via SSH keys failed

Just installed Sourcetree 3.3.8

I followed these directions for linking to my bitbucket account.

I opened a repo on disk that I had already previously cloned using exist SSH keys I setup a long time ago in bitbucket.

Any time I try to push or pull I get this dialog.

Why is sourcetree popping this up? I already have valid SSH keys.. There should be zero problems performing operations repos I've already cloned.


1 answer

1 accepted

Wow this app is hot-garbage.

So you have to:

  1. Generate a new SSH key using PuTTY
  2. Run through a bunch of unnecessary hoops ( to save the public and private keys to disk.
  3. Go to your bitbucket account and add the public key, but the one displayed in PuTTY - if you try to open the .pub from disk and paste that it will fail with "Invalid key".
  4. Then you have to double click the Pageant app from your system tray and add the key you just created. 
  5. image.png


Not enough steps Atlassian. Add at least 10 more. l33t fails..

Why this app cannot connect using existing standard SSH keys, which are already added to bitbucket and being used by the git CLI, is ridiculous.

That sounds like your keys were messed up somehow since that process basically describes a basic SSH key pair setup: Generate keys, provide public key to end host, configure applications to use private key.

I'd check your public key and known_hosts for changes in IP or hostname since this can cause a common SSH authentication issue.

This works, but after a while I need to re-do it again.  Just for fun's sake I guess.  I had to re-set it the 4th time today.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events