79

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?

Napster
  • 2,580
  • 4
  • 30
  • 52
  • 1
    You should verify that you can still `git clone` against the repo. If you cannot even clone then you need to check your authentication tokens. – merlin2011 May 06 '15 at 05:40
  • 4
    Does `ssh -Tv git@github.com` work? – VonC May 06 '15 at 05:41
  • Check your github ssh keys. – uraimo May 06 '15 at 05:42
  • Do you actually have username/repo.git as your branches, or your actual username and repo name? – Steve Chaloner May 06 '15 at 05:46
  • Then try to fix that first: make sure HOME is defined (it is not by default on Windows): https://help.github.com/articles/generating-ssh-keys/#platform-windows – VonC May 06 '15 at 05:46
  • @Napster so it does work? You said "no not work" before. – VonC May 06 '15 at 05:47
  • @VonC : I mean It not solved my problem. What now ? – Napster May 06 '15 at 05:50
  • @Napster check the case (lowercase/uppercase) of your username and repo on GitHub: the url must use the exact username and reponame. – VonC May 06 '15 at 05:52
  • @VonC : I am working on this repo for more then 5 month. Suddenly it stopped to work. Username and repo letter case is also right. I had just changed my profile pic. Is this can be a problem ? I don't know because I am new for github. I know only basic use of git. – Napster May 06 '15 at 05:56
  • Let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/77061/discussion-between-napster-and-vonc). – Napster May 06 '15 at 05:57
  • @Napster 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`)? What version of Git are you using on Windows? – VonC May 06 '15 at 05:59

19 Answers19

82

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.

Siyaram Malav
  • 3,640
  • 1
  • 28
  • 28
  • 8
    I just tried that, it gave me an error: `fatal: No such remote 'origin'` – Rich Dec 06 '16 at 06:44
  • 1
    I don't know what it does but it worked and I can get on with my life! Thanks – Kostas Demiris Jul 14 '17 at 07:54
  • 2
    `origin` is the remote name. If you called your remote something else than origin, this will not work just by copy-pasting. Replace `origin` with your remote name – Zoe stands with Ukraine Jul 28 '17 at 16:23
  • I had the same problem and this solution worked for me, while other solutions did not work for me. Thanks! – Norbert S Mar 04 '18 at 04:20
  • Now, everytime when I want to push, git wants a username and password. how do I fix it? – max Mar 25 '21 at 12:57
  • BTW as of August 13, 2021 this solution will not work as Github as deprecated the use of passwords in all authenticated operations – StonedTensor Sep 01 '21 at 22:08
  • When I try this I get: `fatal: not a git repository (or any of the parent directories): .git` – mikey Oct 15 '21 at 11:42
  • Support for password authentication was removed on August 13, 2021. Please use a personal access token instead. – Ehsan Nov 03 '21 at 18:52
27

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.

Community
  • 1
  • 1
VonC
  • 1,129,465
  • 480
  • 4,036
  • 4,755
27

This usually happens when you use two ssh keys to access two different GitHub account.

Follow these steps to fix this it look too long but trust me it won't take more than 5 minutes:

Step-1: Create two ssh key pairs:

ssh-keygen -t rsa -C "your_email@youremail.com"

Step-2: It will create two ssh keys here:

~/.ssh/id_rsa_account1
~/.ssh/id_rsa_account2

Step-3: Now we need to add these keys:

ssh-add ~/.ssh/id_rsa_account2
ssh-add ~/.ssh/id_rsa_account1
  • You can see the added keys list by using this command: ssh-add -l
  • You can remove old cached keys by this command: ssh-add -D

Step-4: Modify the ssh config

cd ~/.ssh/
touch config

subl -a config or code config or nano config

Step-5: Add this to config file:

#Github account1
Host github.com-account1
    HostName github.com
    User account1
    IdentityFile ~/.ssh/id_rsa_account1

#Github account2
Host github.com-account2
    HostName github.com
    User account2
    IdentityFile ~/.ssh/id_rsa_account2

Step-6: Update your .git/config file:

Step-6.1: Navigate to account1's project and update host:

[remote "origin"]
        url = git@github.com-account1:account1/gfs.git

If you are invited by some other user in their git Repository. Then you need to update the host like this:

[remote "origin"]
            url = git@github.com-account1:invitedByUserName/gfs.git

Step-6.2: Navigate to account2's project and update host:

[remote "origin"]
        url = git@github.com-account2:account2/gfs.git

Step-7: Update user name and email for each repository separately if required this is not an amendatory step:

Navigate to account1 project and run these:

git config user.name "account1"
git config user.email "account1@domain.com"

Navigate to account2 project and run these:

git config user.name "account2"
git config user.email "acccount2@doamin.com"
PHP Worm...
  • 4,712
  • 1
  • 28
  • 50
  • still, i am not able to access it git fetch remote: remote: ======================================================================== remote: remote: The project you were looking for could not be found. remote: remote: ======================================================================== remote: fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. . – Mr Coder Oct 13 '20 at 10:36
  • 2
    It's the best and by far the perfect answer for fixing errors for multiple ssh keys for multiple accounts in same host(gitlab or github) – Al Walid Ashik Nov 09 '20 at 19:29
  • At step 3, I got this error `Could not open a connection to your authentication agent.` – mikey Oct 15 '21 at 11:48
  • @mikey try using sudo – PHP Worm... Oct 18 '21 at 09:37
  • the step of changing the remote origin to include the hostname as it is written in the git config file made this work for me and 99% of other guides are missing this step – Joff May 24 '22 at 02:37
12

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

Jaime Agudo
  • 7,658
  • 4
  • 29
  • 35
8

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.

Muhan Alim
  • 429
  • 1
  • 7
  • 16
  • In my case, I shared my with someone - they had to set *their* on the git path for **push** to work, **pull** worked previously because I had their SSH in the read-only SSH keys section. Confused the heck out of myself but then this finally did the trick! :D – Grant Feb 02 '22 at 01:18
8

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

BSB
  • 1,940
  • 14
  • 24
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

kip2
  • 5,727
  • 3
  • 48
  • 67
6
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

Tudor
  • 1,387
  • 1
  • 17
  • 15
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
Shashank Ks
  • 90
  • 1
  • 7
2

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

Saurabh Kumar
  • 2,289
  • 6
  • 32
  • 50
2

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.

Jonathan Perry
  • 2,793
  • 2
  • 44
  • 48
1

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.

otoloye
  • 538
  • 5
  • 10
1

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"
Erdinç Çorbacı
  • 1,167
  • 14
  • 17
1

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.

Krishna Bagale
  • 11
  • 1
1

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.

Manic Depression
  • 960
  • 1
  • 16
  • 30
0

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.

laimison
  • 1,153
  • 2
  • 13
  • 31
0

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!

Steve Bauman
  • 7,106
  • 6
  • 36
  • 54
0

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.

nafees ahmed
  • 832
  • 1
  • 9
  • 17
0

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.

BZKN
  • 1,267
  • 1
  • 8
  • 23