Permission denied (publickey)

[daiyam]

Hi,

I'm using SourceTree v2.5.2 (111) to clone and push to Bitbucket.

When I trying the clone a project or to push, I'm getting the error:

Please make sure you have the correct access rights
and the repository exists.
Permission denied (publickey).
fatal: Could not read from remote repository.

I've tried to re-add the account, checked the ssh key, I'm still getting the error.

Any thought? Can anybody help me?

Thx

[daiyam · Accepted solution]

Hi,

I was able to fix it!

I've tried to re-authorize SourceTree in the OAuth or regenerate the ssk key with `ssh-keygen`. Both didn't worked.

I did follow the documentation configure-multiple-ssh-identities-for-osx-linux

$ ssh -Tv git@bitbucket.org
OpenSSH_6.9p1, LibreSSL 2.1.8
...
Permission denied (publickey).

$ ssh-add -l 
2048 SHA256:... /Users/user/.ssh/id_rsa (RSA)

$ ssh-add ~/.ssh/user-Bitbucket
Enter passphrase for /Users/user/.ssh/user-Bitbucket: 
Identity added: /Users/user/.ssh/user-Bitbucket (/Users/user/.ssh/user-Bitbucket)

$ ssh-add -l 
2048 SHA256:... /Users/user/.ssh/id_rsa (RSA)
2048 SHA256:... /Users/user/.ssh/user-Bitbucket (RSA)

$ ssh -Tv git@bitbucket.org
OpenSSH_6.9p1, LibreSSL 2.1.8
...
logged in as user.

Then, I was able to push my commits. It's working!

The issue might have come after the reboot of the mac. The first one since I had install SourceTree v2.5.2 (110) for a better support of OAuth...

[Nilesh Jaiswal]

Thank You,  I had the same issue and this was helpful.  

[bver]

I had the same issue in the same scenario (after reboot I think) and this resolved it.  Thank you!

[guy_silva]

same issue here. The solution worked like a charm!
thanks

[umar21]

thnx my issue fix by above work.

[vicentkarl]

thanks a lot!!!!

[sammorala]

I had the same issue, and this solution saved me a time and energy :D thank you very much.

[murraycollingwood]

I had this problem and this solution worked.

I am on Sourcetree 2.7.3 (no recent updates).

Problem happened after an OSX update to High Sierra, osx 10.13.5 

[ralphilius]

This solves my issue for ages!

[patrikroh]

This worked like a charm, thank you!

[Deleted user]

Thanks.

[Arildo Junior]

If I restart the computer I need to do this again, how to avoid this?

[daiyam]

@Arildo Junior you only need to do it once.

[AndrewB]

Worked for me but I only needed to do the first step, 

ssh -Tv git@bitbucket.org

[Vitaly Krivoshapkin]

Thanks man!

[Iftikhar Ahmad Dar]

Solved my issue as well. 

[Nam Lu]

Spot on! Thank you

[krotedev]

Thank you ! In my case i had to start the agent with command:

eval `ssh-agent -s`

And then run the commands listed on your answer.

[Rock Pineda]

If you encountered this on 

ssh-add -l
The agent has no identities.

run this 

ssh-add -K ~/.ssh/id_rsa

to add the key into ssh agent. after this, run

ssh-add -l

fyi, i'm using macOS Mojave 

[VinylRoads]

This solved my issue.

[Rashad Valliyengal]

Wow! You save me. Thanks a lot.

[meierjo]

Great solution!

[Mayank Mathur]

For people like me who do not understand what do you mean by "user-Bitbucket" in 

ssh-add ~/.ssh/user-Bitbucket 

I used id_rsa again and then I was able to do all actions like fetch, pull, or push.

NOTE: I was able to fetch/pull/push from XCODE or terminal but for some reason source tree was unable to do so.

Thanks for the great answer above. Worked :)

[Chandima Gunawardhana]

Thanks for info, this works for me

[Annalaura Tezzon]

For me too, thank you so much!

[wagnermelo]

i was having the same problem but i was able to solve it with your tip, and i just had to use ssh -Tv git@bitbucket.org

[qi ren]

you are great man!

to make it clear, please check all the ssh private key names in your mac then add it using the command

[Brian Farias]

Thanks man!! This works for me. 

[Howard Lovatt]

This didn't work for me because it asks for a passphrase - which I don't know because the key was generated by Sourcetree - what does Sourcetree use?

[curt a]

Sometimes it has to do with the ssh url in the config.

Change the url settings in the config file located under your .git folder inside your project.

i.e.

[remote "origin"]

url =git@Bitbucket.org:clicurt/appname.git

                  👇
url = https://username@Bitbucket.org/username/appname.git

This should get you connected to git using the ssh key pairs you set earlier on.

• *Bold Italicized should be changed to your values accordingly.

[Darron Smith]

Solved it for me in, despite everything in order above. There was one small note due to the fact that I was logging in to a "company" workspace that was not named for my account.

So where you have:

url = https://username@Bitbucket.org/username/appname.git

you might need to read it as this instead:

url = https://username@Bitbucket.org/workspace_name/appname.git

[jcooper]

This worked for me on my windows 10 machine, running tortoisegit with pageant.  Making sure to use my bitbucket username in the clone url.  

[Arpi.Patel]

Thank you for the ans.

Your answer worked me with the help of Darron Smith's answer.

[Jan Paul Dahlke]

Coming from fedora redhat OS > 33 this is actually the soultion:

https://www.reddit.com/r/Fedora/comments/jhxbdh/no_ssh_public_key_auth_after_upgrade_to_fedora_33/ 

[Pere]

This is also what worked for me in fedora 33 https://confluence.atlassian.com/bitbucketserverkb/ssh-rsa-key-rejected-with-message-no-mutual-signature-algorithm-1026057701.html

[Pratyusha Simharaju]

Faced the similar issue. Thanks for sharing

[danielperon]

For me solved running:

eval `ssh-agent -s`
ssh-add 

[Ramya Devi]

I also got the same error.

Permission denied (publickey).

fatal: Could not read from remote repository.

Solution: i regenerated key and added the identitiy by using the below command

ssh-add ~/.ssh/id_rsa 

then i tried giving git pull. it started working!

[Bilal Haidar]

Hello,

I followed all the steps above and I still get the following when I try to 'get fetch':

```

Permission denied (publickey).

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

and the repository exists.

```

I am running on Google Cloud Compute Engine.

I generated a key, added it to the BitBucket, added the key to the chain etc. When I run `ssh -T git@bitbucket.org` I get the message `authenticated via a deploy key.`

I did try to git clone a repository on a different folder on the file system and it works fine. For this folder seems not working.

Thanks

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

[Mohau R]

Thank You!

[Aftab Hafeez]

I have to push my repository to bitbucket but whenever i try to push it or clone my local repo with server it gives me error "permission denied(publickey)" i am using git tortoise on windows 8... any idea what i am doing wrong???

[daiyam]

@Aftab Ahmed Minhas have you tried:

- https://gist.github.com/svanas/87330eeb17313ea50d5cf9c265ab693f

- http://guganeshan.com/blog/setting-up-git-and-tortoisegit-with-bitbucket-step-by-step.html

[Y Joy Meetei]

Refer this you can do it. Thanks

Ssh issue:

https://confluence.atlassian.com/bitbucket/set-up-an-ssh-key-728138079.html

https://www.flynsarmy.com/2017/09/fix-permission-denied-publickey-git/

To check ssh folder. Ctrl + h

https://stackoverflow.com/questions/29179149/ubunutu-ssh-folder-exists-but-i-cannot-see-it-only-through-terminal

https://confluence.atlassian.com/bitbucket/troubleshoot-ssh-issues-271943403.html

[Christian Schober]

Thank you very much, the solution proposed in this post https://www.flynsarmy.com/2017/09/fix-permission-denied-publickey-git/ worked for me!

[magedhamid]

Solved my issue, Thank You.

[jredmond]

Which operating system are you using?

[daiyam]

macOS v10.11.6

[andrew kerr]

Same occurs for me. Has happened since the upgrade to 2.5.2. Switched back to https however that keeps asking for my password constantly. Atleast I can work though.

I've also switched to GitKraken which has no issues with the same repos and ssh. Might be worth switching everything over.