Git : fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists

Question

I am getting this error -

D:\Projects\wamp\www\REPO [master]> git pull origin master
Warning: Permanently added 'github.com,192.30.252.128' (RSA) to the list of known hosts.
ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

The output of git remote -v

D:\Projects\wamp\www\REPO [master]> git remote -v
origin  git@github.com:username/repo.git (fetch)
origin  git@github.com:username/repo.git (push)

Final message of ssh -Tv git@github.com command -

Hi [My Username]! You've successfully authenticated, but GitHub does not provide shell access.

How can I solve it?

Answer 1

change your ssh url by an http url for your remote 'origin', use:

> git remote set-url origin https://github.com/<user_name>/<repo_name>.git

It will ask for your GitHub password on the git push.

Answer 2

I asked in the discussion:

does ssh -T git@github.com ouput the same username (in Hi [My Username]!) as in the one used for the ssh url of your repo (git@github.com:username/repo.git)?

Sorry It not showing same name

That means somehow the credentials have changed.

One solution would be to at least copy %HOME%\.ssh\id_rsa.pub in the SSH keys section of the right GitHub account

The OP adds:

I am working on private repo. So In git@github.com:username/repo.git,

I replied:

If you were able to clone/push to that repo whose username is not your own GitHub account, that must be because you had your previous public ssh key added as a contributor to that repo by the repo's owner.

What next is to ask that same repo owner to add your current public ssh key %HOME%\.ssh\id_rsa.pub to the repo contributor list.
So check with the owner that you (meaning your public ssh key) are declared as a contributor.

Answer 3

For me, I was getting this error because my ssh agent was not running somehow. Doing this worked:

eval `ssh-agent -s`
ssh-add path_to_your_key

Answer 4

Sometimes that (copying the pub ssh key to github/bitbucket) is not enough, particularly with Bitbucket. You also may need to check if your ssh is using the identity you expect rather than messing up with git remote

Check if the agent is using the same identity you pasted on github/bitbucket with ssh-add -l. If missing add it with

ssh-add ~/.ssh/id_rsa_my_git_identity

Further details: https://confluence.atlassian.com/bitbucket/configure-multiple-ssh-identities-for-gitbash-mac-osx-linux-271943168.html

Answer 5

This error happened to me too as the original repository creator had left the company, which meant their account was deleted from the github team.

git remote set-url origin https://github.com/<user_name>/<repo_name>.git

And then git pull origin develop or whatever git command you wanted to execute should prompt you for a login and continue as normal.

Answer 6

Sometimes this happens to me because of network problems. I don't understand the problem fully, but switching to a different sub-network or using VPN solves it

Answer 7

This error can be because of no SSH key on the your local machine. Check the SSH key locally:

$ cat ~/.ssh/id_rsa.pub

If above command do not give any output use below command to create ssh key(Linux/Mac):

$ ssh-keygen 

Now again run cat ~/.ssh/id_rsa.pub This is your SSH key. Copy and add this key to your SSH keys in on git. In gitlab/bitbucket go to

profile settings -> SSH Keys -> add Key

and add the key

Answer 8

ssh-add -D  # Delete all identities.
ssh-add ~/.ssh/your_key

Edit 1
Since I get so many votes, I discovered some issue with this approach and that is that it will remove all your identities so you might have the same issue when you try to read from other repositories and you will need to to this step again for each project...but it might also not be the case for your project

Answer 9

I got the very same errors too. In My case upgrading from Windows 7 to 8 messed up my settings. What helped was to regenerate the private and public SSH keys using PuTTYGen, and change the SSH tool in tortoisegit from SSH to Plink.

I have shared the step by step steps also at http://techblog.saurabhkumar.com/2015/09/using-tortoisegit-on-windows-with.html

Answer 10

Maybe, as in my silly situation, you may somehow created the ssh key by directly typing

ssh-keygen

And so it is created with the local system user credentials so they don't match, use full command like this and recreate

ssh-keygen -t rsa -b 4096 -C "your_email@example.com"

Answer 11

Try:

git config --global credential.helper cache

This command prevents git to ask username and password, not forever but with a default limit to 15 minutes.

git config --global credential.helper 'cache --timeout=3600'

This moves the default limit to 1 hour.

Answer 12

For me none of the solutions here solved it. Frustrated, I restarted my Macbook's iTerm terminal, and voila! My github authorization started working again.

Weird, but maybe iTerm has its own way of handling SSH authorizations or that my terminal session wasn't authorized somehow.

Answer 13

Easy solution for me:

1.) The public SSH Key has to be saved on https://github.com/settings/keys

2.) The email address inside "~/.ssh/id_rsa.pub" (At the end of the file) has to be entered on Github (https://github.com/settings/emails). (This was my problem)

After I saved the email address on GitHub, the problem solved itself.

Answer 14

I had this issue and tried many things but still din't work. Eventually I decided to generate another SSH KEY and boom - it worked. Follow this article by github to guide you on how to generate your SSH KEY.

Lastly don't forget to add it to your github settings. Click here for a guide on how to add your SSH KEY to your github account.

Answer 15

In my case updating GIT helps - I had version 2.23 and with installing version 2.26.2.windows.1 problem disapears.

So if you are sure your SSH key is valid then (see @VonC answer):

1. update GIT
2. update composer
3. run composer clearcache

And it should be ok.

Answer 16

This issue could be related with missing SSH key at Github or any other git server.

In my case I had copied code to another computer and tried to git pull. It failed.

So I had to generate a new SSH key on that machine and update profile on git server with additional SSH key.

Answer 17

Strangely I had this occur with a single repository out of > 20 repositories on my MacBook Pro.

The solution was to upgrade git via homebrew, and everything strangely worked after it finished:

brew install git

Hope this helps someone!

Answer 18

Its not necessary to apply above solutions, I simply changed my internet, it was working fine with my home internet but after 3 to 4 hours my friend suggest me to connect with different internet then I did data package and connect my laptop with it, now it is working fine.

Answer 19

I had the same problem. I tried a couple of solutions mentioned above, it did not work for me. I even restarted my machine and also reconnected my WLAN. But all in vain. Then on the remote repo, I manually made a small change in the readme file of the repo. To pull that change on the local copy of my repo in my machine, I did the usual git pull and then the git push origin. This actually worked.

Answer 20

For me somehow sudo rebooting the fluffing EC2 instance after a fresh ssh-keygen and rm ~/.ssh/known_hosts fixed it! Still not sure how it works but it worked on 4 different EC2 servers with uptime over 700 days. I think it is related to some breaking updates on some processes during the 700 days!! Still not sure what fixed it but for damn its fixed!

Answer 21

I had this same issue and resolved it by adding my SSH key in the ~/.ssh/config file and then updating my git repo url.

~/.ssh/config:

Host github.com-repo-0
    Hostname github.com
    IdentityFile=/home/user/.ssh/repo-0_deploy_key

git repo url:

$ git remote set-url origin git@github.com-repo-1:OWNER/repo-1.git

Note that the Host text exists between the @ and : symbols in the git url.

Source: https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys

Answer 22

same issue I have faced. so here's the way i resolved the same

Step 1:

create a new ssh key:-

ssh-keygen -t ed25519 -C "your_email@example.com"

Step 2:

copy the ssh key on clipboard :-

pbcopy < ~/.ssh/id_ed25519.pub 

Step 3:

now paste copied ssh key to the corresponding git repository

Step 4: Start the ssh-agent in the background.

$ eval "$(ssh-agent -s)"
> Agent pid 59566

Step 5: now try accesing the repo

git clone git@github.com:username/repo-name.git

Step 6:

if still you see the issue then check the ssh config file

vim ~/.ssh/config

the content should look like

Host github.com
  AddKeysToAgent yes
  UseKeychain yes
  IdentityFile ~/.ssh/id_ed25519

Step 7:

Add your SSH private key to the ssh-agent and store your passphrase in the keychain

ssh-add --apple-use-keychain ~/.ssh/id_ed25519

Step 8:

Now try again it should work

git clone git@github.com:username/repo-name.git

Answer 23

The error message you encountered, "Permission denied (publickey)," indicates that you don't have the proper authentication set up to access the remote repository on GitHub. When using the SSH protocol (the default for GitHub), you need to have an SSH key associated with your GitHub account for secure communication and repository access.

To fix this issue and clone the repository successfully, follow these steps:

1. Check for Existing SSH Keys: First, check if you already have an SSH key set up on your computer. Open your terminal or command prompt and run:

   ls -al ~/.ssh
   

   This command will list all files in the ~/.ssh directory. Look for files named id_rsa and id_rsa.pub, which are your private and public SSH keys, respectively.

2. Generate a New SSH Key (If Needed): If you don't have an SSH key or need to generate a new one, use the following command:

   ssh-keygen -t rsa -b 4096 -C "your@email.com"
   

   Replace "your@email.com" with the email associated with your GitHub account. Press Enter to accept the default file location and set a passphrase (or leave it blank for no passphrase).

3. Add the Public Key to Your GitHub Account: After generating the SSH key, you need to add the public key (id_rsa.pub) to your GitHub account. Copy the contents of the public key file using the following command:

   cat ~/.ssh/id_rsa.pub
   

   Copy the output to your clipboard.

   Then, go to your GitHub account's settings and navigate to "SSH and GPG keys." Click "New SSH key," paste the copied public key into the "Key" field, and give it a recognizable title. Finally, click "Add SSH key" to save it.

4. Try Cloning Again: With the SSH key added to your GitHub account, try cloning the repository again using the same git clone <repository_url> command.

   git clone <repository_url>
   

   The cloning process should now work without asking for your username and password.

If you encounter any issues or still face permission problems, double-check your SSH key setup and verify that it's correctly added to your GitHub account. Additionally, make sure you're using the correct repository URL when cloning. The URL should be in the format git@github.com:username/repository.git.