Github Authentication Failed - … GitHub does not provide shell access

44
votes
$ git remote add origin [email protected]:lut/EvolutionApp.git
fatal: remote origin already exists.

$ git push -u origin master
fatal: 'EvolutionApp' does not appear to be a git repository
fatal: Could not read from remote repository.

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

My keys were added succesfully

 $ ssh -T [email protected]
 Hi lut! You've successfully authenticated, but GitHub does not provide shell access.

The Github article https://help.github.com/articles/generating-ssh-keys/ says that "Shell access" should not be an issue? What could the problem be?

5
gitgithubssh-keys
What do you see from git remote show origin? – SLaks
$ git remote show origin fatal: 'EvolutionApp' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. – Lut
@SLaks it says is does not appear to be a Git repository, but previously it said that it already exists. I dont get it. – Lut

5 Answers

65
votes

Try and redefine the ssh url for remote origin:

git remote set-url origin [email protected]:lut/EvolutionApp.git

And try again.

Only git remote set-url can change an existing remote URL (as opposed to git remote add, to add a new remote name and URL)
Here, is issue was the URL of the existing origin: EvolutionApp: it needed to be replaced by a valid one.
Using git config url."ssh://[email protected]/".insteadOf https://github.com/ would not have helper, considering there was no HTTPS URL in the first place.

2
votes

You might have to add the remote again. That error message happens when Git doesn't know where to push to.

Use git remote -v check if the remote exists, if not, add it.

Even then if it doesn't work try removing the GIT_SSH environment variable, this maybe causing the problem.

1
votes

This can happen if you have an incomplete remote entry in your global config.

Run git config -e --system, comment out any [remote entries, re-add the remote, and try again.

1
votes

check if you are using https as remote url instead of ssh. I set my remote url to http and encountered this issue. After resetting the url to ssh protocol the problem is gone.

1
votes

You can add this in the ~/.gitconfig file.

[url "ssh://[email protected]/"]
        insteadOf = https://github.com/

Now ssh will be used instead of https.