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
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?
At lease for me, the issue was the the ssh agent used by Sourcetree did not have the key loaded.
I fixed this by:
ssh-add -K ~/.ssh/<git_key_name>
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 email@example.com` 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?
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
Yes, I was fighting this problem today and just ended up with an ugly fix:
Thus ending up with two identical sets of keys in my ~/.ssh
Ugly, but it seems to work...
Hope it will help