Canot push to remote repo - "Please make sure you have the correct access rights and the repository exists."

Viewed 13595

I'm constantly facing authentication issues as a consequence of moving between pushing to my private projects and my work ones. Each time I move from a work context to a personal one, I spend some time dealing with my ssh keys and configuration. I often go through the github documentation around generating and adding ssh public keys to the site.

Today, I'm getting:

ERROR: Repository not found.
fatal: Could not read from remote repository.

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

I tried generating a new ssh key pair and submitting the public key to github but github says "key already in use". I googled that for a bit but could not fully make sense of that error message.

Switching gears I noticed that when running the command ssh -T git@github.com, the output greets me as the Github user associated with my personal account username and not my work one.

My understanding of ssh was that it was in some sense "accountless". No username or password is part of the ssh connection process. So now that I believe the authentication issue revolves around some system believing I'm logged in as my private github account's username, what can I do?

1 Answers
Related