'Bitbucket/Github: permission denied public key
when I am trying to clone a rails app repo I have got permission to, I am getting this issue.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Even after adding public key by generating one, I am unable to solve this.
Although I am able to clone using he https method but after making changes, the same error comes while I try to push the code.
Please suggest an answer for this.
Solution 1:[1]
When attempting to clone, push, or pull over SSH with Git, you may receive one of these messages if Bitbucket couldn't authenticate with the keys that your SSH agent offered.
Here are the most common reasons why you may see these messages:
You used sudo when attempting the connection
You shouldn't use sudo when cloning, pushing, or pulling because the ssh-agent runs on the user level, not the root level.
Your public key isn't loaded into Bitbucket
To check if your public key is loaded into Bitbucket, do the following:
From Bitbucket, choose Personal settings from your avatar in the lower left. The Account settings page displays.
Click SSH keys. The SSH keys page shows a list of any existing keys.
If you don't have any keys listed, you can follow our Set up an SSH key documentation to set one up.
Your key isn't loaded into your SSH agent
If your SSH agent doesn't know to offer Bitbucket a key, the connection fails. You may run into this issue if you've recently restarted your system.
You can refer to this Article for more informations: https://support.atlassian.com/bitbucket-cloud/docs/troubleshoot-ssh-issues/
Solution 2:[2]
Check few things.
Is the generated new key is the one your ssh agent using when trying to ssh to server. (Your ssh agent might be using a different key than the one you generated) use this to list currently loaded keys by agent.
ssh-add -LYou properly added public key to your repository hosting location.
The keys corresponding to above 1 and 2 should match.
Solution 3:[3]
Please see this article: GitHub: Generating SSH Keys. What happens when you run:
ssh -T [email protected]
?
You may have added the wrong key to authenticate with.
Solution 4:[4]
I faced this error when I created another repository in my local. My ssh-keys were already set up and I was trying to push code through vs code.
The issue got resolved when I git push-ed through git bash like I was doing before.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | Kiraahmad |
| Solution 2 | Swift Hipster |
| Solution 3 | |
| Solution 4 | Harsh Phoujdar |