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
4,368,737
Community Members
 
Community Events
168
Community Groups

Permission denied (publickey) (sourcetree mac)

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 Apr 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.

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

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

Manju Atlassian Team May 24, 2018

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

It helps me.
Thx a lot.

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. 

IdentityFile, not IdentifyFile

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

Atlassian Community Events