nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Prem Mariappan

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.

Accepted answers

All comments

Prem Mariappan

Bug Report: STSP-5957

Jacob Andersen

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

allowed SourceTree to generate the keys
deleted the newly generated key files right away (in my case ~/.ssh/jacobandersen-Bitbucket and ~/.ssh/jacobandersen-Bitbucket.pub)
and made copies of the correct key files (in my case ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub) 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

Tony Coyle

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 git@bitbucket.org` 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?

Steven Smith_9681ji

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 https://confluence.atlassian.com/bbkb/permission-denied-publickey-302811860.html

manolesc_test

At lease for me, the issue was the the ssh agent used by Sourcetree did not have the key loaded.

I fixed this by:

Click the Console button
In the new CLI console, type
```
ssh-add -K ~/.ssh/<git_key_name>
```
Back in the Sourcetree UI, try doing a fetch an verify the log output

Bowofola Fadojutimi

For me, i just had to delete the ssh keys in `~/.ssh` and regenerate new keys. Sourcetree was able to upload them into my github account and clone repositories again.

Saravanakumar P_cj3g95

Hi Bowofola,

Its sounds good.. Even I tried same but key not uploaded to github. Can I know which version of sourcetree you are using ?

Gordon Van Dyke

Where can I find the git_key_name?

Shrikant

Can any one help me with this? I'm using SourceTree version 4.1.8.

Benny Sway

I had the same problem on Sonoma 14.4.1 and I didn't want to delete my previous keys, but I ended up making it work. While Sourcetree is open, click on the menu option left of File, ie the Sourcetree menu option, and click "Install Command Line Tools". It will verify or install, and theres a prompt in the success message saying you can now use the tools by writing the command stree in the console/terminal. I then clicked the Terminal button which is in the main Sourcetree window. I verified my keys with ssh-add -l, and then ran the stree command. It just reopened the normal view again (seemed like it did nothing) I tried to push my failed commits and they went through . For this solution to work you have to be sure that the ssh keys in Github or which ever source control you're using are the same as the ones in your ssh-add -l. Cheers if this helps

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket-cloud

mac