Unable to Git-push master to Github – ‘origin’ does not appear to be a git repository / permission denied

by

What does

$ git config --get-regexp '^(remote|branch)\.'

returns (executed within your git repository) ?

Origin is just a default naming convention for referring to a remote Git repository.

If it does not refer to GitHub (but rather a path to your teammate repository, path which may no longer be valid or available), just add another origin, like in this Bloggitation entry

$ git remote add origin2 [email protected]:myLogin/myProject.git
$ git push origin2 master

(I would actually use the name ‘github’ rather than ‘origin’ or ‘origin2’)

Permission denied (publickey).
fatal: The remote end hung up unexpectedly

Check if your gitHub identity is correctly declared in your local Git repository, as mentioned in the GitHub Help guide. (both user.name and github.name — and github.token)

Then, stonean blog suggests (as does Marcio Garcia):

$ cd ~/.ssh
$ ssh-add id_rsa

Aral Balkan adds: create a config file

The solution was to create a config file under ~/.ssh/ as outlined at the bottom of the OS X section of this page.

Here’s the file I added, as per the instructions on the page, and my pushes started working again:

Host github.com
User git
Port 22
Hostname github.com
IdentityFile ~/.ssh/id_rsa
TCPKeepAlive yes
IdentitiesOnly yes

You can also post the result of

ssh -v [email protected]

to have more information as to why GitHub ssh connection rejects you.

Check also you did enter correctly your public key (it needs to end with ‘==‘).
Do not paste your private key, but your public one. A public key would look something like:

ssh-rsa AAAAB3<big string here>== [email protected]

(Note: did you use a passphrase for your ssh keys ? It would be easier without a passphrase)

Check also the url used when pushing ([email protected]/..., not git://github.com/...)

Check that you do have a SSH Agent to use and cache your key.

Try this:

 $ ssh -i path/to/public/key [email protected]

If that works, then it means your key is not being sent to GitHub by your ssh client.

More Related Contents:

  1. Set up git to pull and push all branches
  2. How do I rename a local Git branch?
  3. How can I reset or revert a file to a specific revision?
  4. How to change the author and committer name and e-mail of multiple commits in Git?
  5. Definition of “downstream” and “upstream”
  6. Recovering added/staged file after doing git reset –hard HEAD^?
  7. Git Push Error: insufficient permission for adding an object to repository database
  8. Insert a commit before the root commit in Git?
  9. How can I get a list of Git branches, ordered by most recent commit?
  10. How do I find the next commit in Git? (child/children of ref)
  11. Changing git commit message after push (given that no one pulled from remote)
  12. How do you make Git ignore files without using .gitignore?
  13. Are Git’s pack files deltas rather than snapshots?
  14. View a file in a different Git branch without changing branches
  15. Should composer.lock be committed to version control?
  16. Flexible vs static branching (Git vs Clearcase/Accurev)
  17. Git keyword substitution like those in Subversion?
  18. Git push: “fatal ‘origin’ does not appear to be a git repository – fatal Could not read from remote repository.”
  19. Git rebase – commit select in fork-point mode
  20. How can I push a local Git branch to a remote with a different name easily?
  21. Git On Custom SSH Port
  22. Should I add the Visual Studio 2015 .vs folder to source control?
  23. How to change git ssh user for a remote push temporarily?
  24. Git: How to squash all commits on branch
  25. Git: add vs push vs commit
  26. git reset asks ‘more?’
  27. Git push failed, “Non-fast forward updates were rejected”
  28. How does git track source code moved between files?
  29. Push and pull my conda environment using git
  30. Why does ‘git commit’ not save my changes?

Leave a Comment