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

Permission denied (publickey) (sourcetree mac)

hawkun April 7, 2018
Pushing to git@bitbucket.org:(my repo).git

git@bitbucket.org: Permission denied (publickey).

fatal: Could not read from remote repository.

 

Please make sure you have the correct access rights

and the repository exists.

I suddenly started getting this, if I try to change everything thing back to default and try again, I get "device not configured".

 

This suddenly started happening after upgrading to High Sierra

2 answers

12 votes
Manju
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 10, 2018

Please check if the ssh-agent has your keys loaded. If not, please add them to the agent. 

Run below commands in terminal to do so,

To check if keys are loaded:

ssh-add -l

To add keys to agent:

ssh-add <path_to_key>

more like,

ssh-add ~/.ssh/id_rsa

Key in the passphrase used while generating the ssh key and you should be good to go.

hawkun April 10, 2018

It appears this isn't the solution, there's a bug in the latest version of sourcetree.

Downgrading to the previous stable build fixed everything.

Like # people like this
Andrey Streltsov May 23, 2018

@hawkun can you tell which version does work for you?

hawkun May 23, 2018

2.7

Manju
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 24, 2018

Could you please confirm what version you used earlier and what was the result of running those commands on your machine?

Anatoliy Podkladov
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 14, 2018

It helps me.
Thx a lot.

Alex Grafe
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 3, 2023

Thanks, this worked for me:

ssh-add ~/.ssh/_PATH_TO_SOURCETREE_KEY_
3 votes
Andrey Streltsov November 14, 2018

What I did just yesterday to fix this problem:

1. Create "config" file in ~/.ssh

2. Put in this config:

Host = *
UseKeychain yes
AddKeysToAgent yes
IdentifyFile path/to/your/private/key
IdentityFile path/to/your/another/private/key

After that authentication goes smoothly(with help of "ssh-add -K identity"). This seems to be a change related to macOS update: required for Sierra or High Sierra. 

Eric Herrmann
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 29, 2019
IdentityFile, not IdentifyFile
trevortwining
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 18, 2019

Using this on Mojave fixed my problem. I thought those identities got added automatically but I guess that's wrong. Thanks for the suggestion!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events