2016-05-31 26 views
0

なぜHerokuにプッシュすると突然私は許可が拒否されるのかわからない!SSHの許可の拒否

$ git push staging 19-home-page-video:master 
Permission denied (publickey). 
fatal: Could not read from remote repository. 

Please make sure you have the correct access rights 
and the repository exists. 

ザ・は私だけが見ることができると思いますが、以下のコードであり、trying private keysある下部の3行が存在しないキー...任意の提案ですか?

$ ssh -v [email protected] 
OpenSSH_6.9p1, LibreSSL 2.1.8 
debug1: Reading configuration data /Users/micahsherman/.ssh/config 
debug1: Reading configuration data /etc/ssh/ssh_config 
debug1: /etc/ssh/ssh_config line 21: Applying options for * 
debug1: Connecting to heroku.com [50.19.85.132] port 22. 
debug1: Connection established. 
debug1: identity file /Users/micahsherman/.ssh/id_rsa type 1 
debug1: key_load_public: No such file or directory 
debug1: identity file /Users/micahsherman/.ssh/id_rsa-cert type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /Users/micahsherman/.ssh/id_dsa type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /Users/micahsherman/.ssh/id_dsa-cert type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /Users/micahsherman/.ssh/id_ecdsa type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /Users/micahsherman/.ssh/id_ecdsa-cert type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /Users/micahsherman/.ssh/id_ed25519 type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file /Users/micahsherman/.ssh/id_ed25519-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_6.9 
debug1: Remote protocol version 2.0, remote software version endosome 
debug1: no match: endosome 
debug1: Authenticating to heroku.com:22 as 'git' 
debug1: SSH2_MSG_KEXINIT sent 
debug1: SSH2_MSG_KEXINIT received 
debug1: kex: server->client aes128-ctr hmac-sha2-256 none 
debug1: kex: client->server aes128-ctr hmac-sha2-256 none 
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY 
debug1: Server host key: ssh-rsa SHA256:8tF0wX2WquK45aGKs/Bh1dKmBXH08vxUe0VCJJWOA/o 
debug1: Host 'heroku.com' is known and matches the RSA host key. 
debug1: Found key in /Users/micahsherman/.ssh/known_hosts:12 
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: Offering RSA public key: /Users/micahsherman/.ssh/id_rsa 
debug1: Authentications that can continue: publickey 
debug1: Trying private key: /Users/micahsherman/.ssh/id_dsa 
debug1: Trying private key: /Users/micahsherman/.ssh/id_ecdsa 
debug1: Trying private key: /Users/micahsherman/.ssh/id_ed25519 
debug1: No more authentication methods to try. 
Permission denied (publickey). 
+0

デバッグトレースに従って、クライアントはid_rsaキーをサーバーに提供しましたが、サーバーはそれを受け入れませんでした。鍵が動作すると仮定した場合、サーバ上にはこれを引き起こす可能性のあるものが6つあります。可能であれば、サーバーログでsshdからのエラーメッセージを調べる必要があります。 – Kenster

+0

ありがとう@Kenster、修正は不足しているキーを追加することでした... '$ heroku keys:add'。ありがとうございました。 –

答えて

1

キーを追加する必要がありました。 $ heroku keys:add

関連する問題