部署 heroku 代码时权限被拒绝(公钥).致命:远端意外挂断 [英] Permission denied (publickey) when deploying heroku code. fatal: The remote end hung up unexpectedly

问题描述

我正在尝试使用以下命令行将我的代码部署到 heroku:

I'm attempting to deploy my code to heroku with the following command line:

git push heroku master

但得到以下错误:

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

我已经上传了我的公共 SSH 密钥，但它仍然出现这个错误.

I have already uploaded my public SSH key, but it still comes up with this error.

推荐答案

您必须将您的公钥上传到 Heroku:

You have to upload your public key to Heroku:

heroku keys:add ~/.ssh/id_rsa.pub

如果您没有公钥，Heroku 会提示您自动添加一个可以无缝工作的公钥.只需使用:

If you don't have a public key, Heroku will prompt you to add one automatically which works seamlessly. Just use:

heroku keys:add

要清除所有以前的键，请执行以下操作:

To clear all your previous keys do :

heroku keys:clear

要显示您现有的所有密钥，请执行以下操作:

To display all your existing keys do :

heroku keys

以上似乎对我不起作用.我弄乱了 HOME 环境变量，所以 SSH 在错误的目录中搜索密钥.

The above did not seem to work for me. I had messed around with the HOME environment variable and so SSH was searching for keys in the wrong directory.

要确保 SSH 检查正确目录中的密钥，请执行以下操作:

To ensure that SSH checks for the key in the correct directory do :

ssh -vT [e-mail]

这将显示以下(示例)行

Which will display the following ( Sample ) lines

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/Wrong/Directory/.ssh/identity type -1
debug1: identity file /c/Wrong/Directory/.ssh/id_rsa type -1
debug1: identity file /c/Wrong/Directory/.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->client aes128-cbc hmac-md5 none
debug1: kex: client->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/Wrong/Directory/.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/Wrong/Directory/.ssh/identity
debug1: Trying private key: /c/Wrong/Directory/.ssh/id_rsa
debug1: Trying private key: /c/Wrong/Directory/.ssh/id_dsa
debug1: No more authentication methods to try.

权限被拒绝(公钥).

从上面你可以观察到 ssh 在 /c/Wrong/Directory/.ssh 目录中寻找密钥，这不是我们刚刚添加到 heroku 的公钥(using heroku keys:add ~/.ssh/id_rsa.pub ) ( 请注意在windows OS中~指的是HOMEwin 7/8 中的路径是 C:UsersUserName )

From the above you could observe that ssh looks for the keys in the /c/Wrong/Directory/.ssh directory which is not where we have the public keys that we just added to heroku ( using heroku keys:add ~/.ssh/id_rsa.pub ) ( Please note that in windows OS ~ refers to the HOME path which in win 7 / 8 is C:UsersUserName )

要查看您当前的主目录，请执行:echo $HOME 或 echo %HOME% (Windows)

To view your current home directory do : echo $HOME or echo %HOME% ( Windows )

要正确设置您的 HOME 目录(正确地我指的是 .ssh 目录的父目录，以便 ssh 可以在正确的目录中查找密钥)请参考这些链接:

To set your HOME directory correctly ( by correctly I mean the parent directory of .ssh directory, so that ssh could look for keys in the correct directory ) refer these links :

1. SO 答案关于如何永久设置 Unix 环境变量

关于 ssh 在错误目录中寻找密钥的问题及其解决方案.

这篇关于部署 heroku 代码时权限被拒绝(公钥).致命:远端意外挂断的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！