Heroku Permission denied publickey fatal Could not read from remote repository woes

Question

I ve searched around for many hours on end looking to a solution to my seemingly easy-to-fix problem  It s not that my search turned up nothing  it s that my search turned up so many different solutions -none of which have worked   Anyways  I am simply unable to push  pull  or fetch from my Heroku repository from my Mac  Every attempt gives me  as if it s mocking me  the following error       Permission denied  publickey   fatal  Could not read from remote   repository     I ve tried  and re-tried  to fix it in many different ways  As I ve said  I ve spent a good chunk of the last two days searching around for an answer  Here are some of the things I ve tried    heroku keys clear followed by heroku keys add Regenerating an ssh key on my own with  ssh-keygen -t rsa  Clearing out my  ssh directory  followed by heroku keys clear  followed by generating an ssh key Deleting my app on heroku and recreating one  fortunately not much was on there    I can fetch from my GitHub repository fine  so I know it s not network connectivity  pinging heroku also works     As a makeshift solution  that I hope doesn t turn into a permanent one   I ve logged in to my Ubuntu Amazon AWS ec2 instance  Pulling and pushing to and from Heroku works perfectly  For this reason  I still feel as if the problem lies with the ssh key on my Mac  Both keys show up under my Heroku account  Does the email address at the end of the key matter   EDIT  I can push and pull from GitHub fine  I m not using ssh  however   so why not Heroku   At this point I m willing to try anything  Thanks

User · Answer

I know this has already been answered  But I would like to add my solution as it may helpful for others in the future    A common key error is  Permission denied  publickey   You can fix this by using keys add to notify Heroku of your new key   In short follow these steps  https   devcenter heroku com articles keys  First you have to create a key if you don t have one   ssh-keygen -t rsa   Second you have to add the key to Heroku   heroku keys add

User · Answer

I had the same issue  And I tried to reset my keys as everyone said  but it still didn t worked  For was because I renamed the app   So what I did was to reset my keys and also rename app from console  Check this question for more information  Heroku push app problem

User · Answer

My way on Windows 8   Add a directory with ssh-keygen to the system PATH variable  usually C  Program Files  x86  Git bin Open CMD  go to C  Users Me  Generate SSH key ssh-keygen -t rsa  Enter file in which to save the key     ssh id rsa    ssh id rsa  change a default incorrect path to  ssh somegoodname rsa  Add the key to Heroku heroku keys add  Select a created key from a list Go to your app directory  write some beautiful code Init a git repo git init git add   git commit -m  chore release   v0 0 1 Create Heroku application heroku create Deploy your app git push heroku master Open your app heroku open

User · Answer

Had a similar issue  and tried lots of things   Ultimately what worked for me  was to have Gnu on Windows installed  https   github com bmatzelle gow releases    and ensure that it was using the ssh tool inside that directory and not the one with Git  Once installed test with  ensure if its in your environment PATH that it preceds Git bin   C  Git htest2 gt which ssh C  Program Files  x86  Gow bin ssh BAT   I used putty and pageant as described here http   rubyonrailswin wordpress com 2010 03 08 getting-git-to-work-on-heroku-on-windows-using-putty-plink-pageant   Once the keys had been sent to heroku   heroku keys add c  Users Person ssh id rsa pub   use  ssh -v  lt username gt  heroku com    and ensure that your stack is showing use of Putty - ie a working stack   Looking up host  heroku com  Connecting to 50 19 85 132 port 22 Server version  SSH-2 0-Twisted Using SSH protocol version 2   We claim version  SSH-2 0-PuTTY Release 0 62   Using Diffie-Hellman with standard group  group1  Doing Diffie-Hellman key exchange with hash SHA-1 Host key fingerprint is  ssh-rsa 2048 8b 48 5e 67 0e c9 16 47 32 f2 87 0c 1f c8 60 ad Initialised AES-256 SDCTR client- gt server encryption Initialised HMAC-SHA1 client- gt server MAC algorithm Initialised AES-256 SDCTR server- gt client encryption Initialised HMAC-SHA1 server- gt client MAC algorithm Pageant is running  Requesting keys  Pageant has 1 SSH-2 keys Using username   --ommitted for security--      Trying Pageant key  0   Authenticating with public key  rsa-key-20140401  from agent Sending Pageant s response Access granted Opened channel for session Server refused to allocate pty Server refused to start a shell command FATAL ERROR  Server refused to start a shell command   One that was running previously and failed   C  Git htest2 gt ssh -v  lt username gt  gmail com heroku com OpenSSH 4 6p1  OpenSSL 0 9 8e 23 Feb 2007 debug1  Connecting to heroku com  50 19 85 156  port 22  debug1  Connection established  debug1  identity file  c Users Person  ssh identity type -1 debug1  identity file  c Users Person  ssh id rsa type 1 debug1  identity file  c Users Person  ssh id dsa type -1 debug1  Remote protocol version 2 0  remote software version Twisted debug1  no match  Twisted 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- gt client aes128-cbc hmac-md5 none debug1  kex  client- gt server aes128-cbc hmac-md5 none debug1  sending SSH2 MSG KEXDH INIT debug1  expecting SSH2 MSG KEXDH REPLY debug1  Host  heroku com  is known and matches the RSA host key  debug1  Found key in  c Users Person  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   c Users Person  ssh identity debug1  Offering public key   c Users Person  ssh id rsa debug1  Server accepts key  pkalg ssh-rsa blen 277 debug1  Trying private key   c Users Person  ssh id dsa debug1  No more authentication methods to try  Permission denied  publickey

User · Answer

I had the exact same error  on windows 7  and the cause was different   I solved it in a different way so I thought I d add the cause and solution here for others     Even though the error seemed to point to heroku really the error was saying  Heroku can t get to the git repository    I swore I had the same keys on all the servers because I created it and uploaded it to one after the other at the same time     After spending almost a day on this I realized that because git was only showing me the fingerprint and not the actual key  I couldn t verify that it s key matched the one on my HD or heroku   I looked in the known hosts file and guess what    it shows the keys for each server and I was able to clearly see that the git and heroku public keys did not match   1  I deleted all the files in my key folder  the key from github using their website  and the key from heroku using git bash and the command heroku keys clear  2  Followed github s instructions here to generate a new key pair and upload the public key to git  3  using git bash- heroku keys add to upload the same key to heroku     Now git push heroku master works   what a nightmare  hope this helped somebody   Bryan

User · Answer

you need to create a new ssh key by typing the following - ssh-keygen -t rsa  Then you need to add  - heroku keys add  Then if you type - heroku open  The problem has been solved   It worked for me anyway  you could give it a try

User · Answer

I just thought I d share that I found the answer to my own question   Writing out my problem made it even more clear to me  and I further investigated into where I thought my problem lay  the ssh key  Turns out I was right  The issue wasn t with the key itself  but rather that I had not added it to my local Mac s list of known ssh keys  So even though my Heroku account had the correct key uploaded  my Mac could not authenticate with it because it could not find that key on my computer  The solution   ssh-add    ssh id rsa  and  to confirm it s been added to the known list of keys ssh-add -l   I would like to give credit to https   help github com articles error-permission-denied-publickey for being a good reference

User · Answer

i had the same case on linux ubuntu and just fixed it  it seems that OS was confused between the  root  ssh  and home user  ssh  dir  what i did was    removed all keys from root and home user  shh directory  generated a new key make sure to pay attention to the path of creation   home you  ssh id rsa  or   root  ssh id rsa  check heroku keys heroku keys if keys in there clear heroku keys clear heroku keys add now in here if heroku couldn t find a key and asked to generate one right no  and this mean you have the same issue as mine  do the add command like this heroku keys add  root  ssh id rsa pub the path that you ll add will be the one that you got in step 2  try git push heroku master now

User · Answer

I use this method to solve this problem Maybe you can try it   Enable ssh-agent    Download git   http   git-scm com    Install it Enable ssh-agent   C  Program Files Git cmd  start-ssh-agent  The message disapper after I agent enabled Hope this will help you

User · Answer

I d like to add another solution since I didn t see it here   My problem was that heroku was linking to the wrong url  since I kept playing around with url names    Editing the remote url solved my problem   git remote set-url heroku  lt heroku-url-here gt

User · Answer

The problem I was having is that I was only using https for my GitHub account  I needed to make sure that my GitHub account was setup for ssh access and that GitHub and heroku were both using the same public keys  These are the steps I took    Navigate to the    ssh directory and delete the id rsa and id rsa pub if they are there  I started with new keys  though it might not be necessary     cd    ssh   rm id rsa id rsa pub  Follow the steps on gitHub to generate ssh keys Login to heroku  create a new site and add your public keys     heroku login       heroku create   heroku keys add   git push heroku master

User · Answer

I got the same error  and because I have 4 ssh-keys  so I tried follow   ssh-keygen -t rsa heroku keys add   then  four options show   1  github rsa pub 2  id boot2docker pub 3  id rsa pub 4  sshkey pub   I choose 3   the newest one  Then  I fix the error

User · Answer

SO So So simple solution   go to c  Users user name  ssh  and delete all pub   private key pairs   this way heroku will generate keys for you

User · Answer

I had a similar heroku ssh error that I could not resolve     As a workaround  I used the new heroku http-git feature  http transport for  heroku  remote instead of ssh    Details here  https   devcenter heroku com articles http-git   Short version  if you have a project already setup the standard way  run heroku git remote --http-init to change  heroku  remote to http    A good quick work around if you don t have time to fix troubleshoot an ssh issue

[git] Heroku 'Permission denied (publickey) fatal: Could not read from remote repository' woes

Examples related to git

Examples related to heroku

Examples related to ssh

Examples related to repository

Examples related to public-key