SourceTree can't detect SSH Keys installed on OSX any more - anyone else experiencing this?

I've been using Bitbucket / Hg / SourceTree using SSH on OSX / MacOS for many years.

With the recent upgrade to (SourceTree v2.4) it can't detect the SSH keys installed on the system and has changed all the repo remote settings over to HTTPS.  When I attempt to add the SSH key via SourceTree (SourceTree -> Preferences -> Accounts) it says "no key found", even though I can confirm that the SSH agent is running and the keys I've been using are loaded.

I have no issues using Hg from the CLI when I correct the hgrc remote setting back from https to SSH (SourceTree attempts to 'correct' the error and changes all the SSH remote settings to HTTPS upon opening each repo)

Anyone else experiencing this?  Any ideas on how to solve this issue?  

Thank you.


4 answers

My macbook pro is on 2.6.3. Whenever I make an SSH key it works, then if I exit source tree and return, it doesn't. If I go into my account settings, I can see it pointing to the correct key, but it won't use it (or maybe it forgets the password for the key). I need to add it to ssh agent according to

Yes, I was fighting this problem today and just ended up with an ugly fix:

  1. allowed SourceTree to generate the keys
  2. deleted the newly generated key files right away (in my case ~/.ssh/jacobandersen-Bitbucket and ~/.ssh/
  3. and made copies of the correct key files (in my case ~/.ssh/id_rsa and ~/.ssh/ with the names above.

Thus ending up with two identical sets of keys in my ~/.ssh

Ugly, but it seems to work...

Hope it will help

I'm on SourceTree 2.5.1 and I'm seeing the same buggy behaviour. `ssh-add -l` from  shell shows me several identifies.  Two of which have been loaded up into my Bitbucket account. Using one of those identities I can connect to Bitbucket successfully using `ssh` without problem and get the logged out of the shell as expected. Yet the Bitbucket account in SourceTree refuses to acknowledge/use either of these SSH keys/identieis and simply says, 'No key found', provides no way of selecting one, only giving you the ability to generate one.

@Prem Mariappan to bug report doesn't seem visible?

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

627 views 0 4
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot