Unable to click master on hero

Question

I can not use git push in github as well as heroku, I tried various methods as suggested on this question . Pls help solve this problem .. i see the following report while i try to click.

D:\My\weblog>git push heroku master Permission denied (publickey). fatal: The remote end hung up unexpectedly D:\My\weblog>ssh -v [e-mail] OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007 debug1: Connecting to heroku.com [50.16.232.130] port 22. debug1: Connection established. debug1: identity file /.ssh/identity type -1 debug1: identity file /.ssh/id_rsa type -1 debug1: identity file /.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debia n-5pgsql1 debug1: match: OpenSSH_5.1p1 Debian-5pgsql1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'heroku.com' is known and matches the RSA host key. debug1: Found key in /.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: /.ssh/identity debug1: Trying private key: /.ssh/id_rsa debug1: Trying private key: /.ssh/id_dsa debug1: No more authentication methods to try. Permission denied (publickey). 

Am uses windows 7.

Answer 1

type gem install heroku

Then upload rsa key from github to heroku

 $ heroku keys:add Uploading ssh public key /Users/adam/.ssh/id_rsa.pub 

As soon as you enter the configuration with the hero and github with the team, all your code goes to github, and from there to Heroku

 git push heroku master 

and soon you will see these messages

 -----> Heroku receiving push -----> Ruby/Rails app detected -----> Detected Rails is not set to serve static_assets 

Answer 2

It seems that the hero does not accept your public car keys. Make sure you provide your public key to the hero. The Heroku SSH Key Guide should help.

Answer 3

you can try this

http://devcenter.heroku.com/articles/keys

Answer 4

I ran into a similar problem on OSX using heroku-toolbelt / 2.32.8. Even after the next heroic, I was not successful until I used the key in the default path - IE ~ / .ssh / id_rsa.pub.

Answer 5

I had the same problem - it turned out that I forgot that Windows 8 does not start the command line with administrator rights by default, as Windows 7 did. Running as administrator fixed my problem.

Answer 6

On ubuntu, sudo su solved this for me.

When I used ssh to generate the key, then if you read the contents of "id_rsa.pub" there will be a username at the end of the file. For me it was "root @ pc-name", but without sudo su current username is "username @ pc-name" instead of "root @ pc-name". sudo su decides by going to "root @ pc-name".

Answer 7

If you use Windows and Cygwin, I had to run Cygwin with administrator privileges before he let me click on Heroku.

Answer 8

I ran into the same problem. I solved this with the change cmd command with Git Bash. Do it all on Git.