There are lots of stack articles citing the same error message as I am getting.
I went through the entire heroku setup doc on another computer and everything worked perfectly. Not sure why this one is not working, but I need it to.
When I run:
> git push -v heroku master
Pushing to git@heroku.com:lit-tor-7969.git
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
All of the solutions on Stack involve reseting the ssh keys, and I believe the ssh keys are fine. I am on Mac OSX and have run:
heroku keys:clear
heroku keys:add
So it looks to me like the git is using /Users/bishopz/.ssh keys rather than the keys I generated manually inside the repository folder.
In addition to the answers below, this article seems to be providing a lot of insight:
Cannot push to Heroku because key fingerprint
I tried completely removing the .ssh directory. I ran
heroku keys:clear
ssh-add -D #to remove all ssh identities
ssh-keygen -t rsa -C "email@gmail.com" -f ~/.ssh/id_rsa_heroku
ssh-add ~/.ssh/id_rsa_heroku
heroku keys:add ~/.ssh/id_rsa_heroku.pub
git push heroku master
and now get:
! Your key with fingerprint 27:5f:64:4e:2e:f0:41:5b:62:a9:95:d2:02:df:27:85 is not authorized to access lit-tor-7969.
fatal: The remote end hung up unexpectedly
The response to
ssh -vvv git@heroku.com
is now:
debug1: Host 'heroku.com' is known and matches the RSA host key.
debug1: Found key in /Users/bishopz/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: Offering RSA public key: /Users/bishopz/.ssh/id_rsa_heroku
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: Authentication succeeded (publickey).
Authenticated to heroku.com ([50.19.85.132]:22).
Any help appreciated, I’ll start a new bounty if someone can post an answer that works for me.
Okay, I was able to solve it. Several of these answers were helpful. It seem that two things had happened.
First, based on this article the ssh keys had gotten confused. This was resolved by deleting the .ssh directory (of course this removed all the credentials for other things that use .ssh, but those can be recreated later):
Secondly, based on an answer to this article the app name had somehow changed during the process of troubleshooting the ssh keys. The app name had to be manually edited in /repository_folder/.git/config
To get the correct app name I logged into heroku.com on the web and then updated the config file:
it’s contains
Thanks to all that posted suggestions! I am so happy to finally be on my way to a new app!
–UPDATE–
I have to rerun this command every time I reboot the computer. I can add it my .profile or whatever, but thought it was worth a note.