2017-09-03 15 views
-1

私が作成したばかりのUbuntuインスタンスはAmazon AWSです。 SSH経由で接続するには、その指示にAWS - SSH経由で接続できません - 「権限が拒否されました(公開鍵)」

(彼らはあなた自身の偶然にとの指示を提供する)、彼らは言う:

To access your instance: 
Open an SSH client. (find out how to connect using PuTTY) 
Locate your private key file (my.experiments.com.pem). The wizard automatically detects the key you used to launch the instance. 
Your key must not be publicly viewable for SSH to work. Use this command if needed: 
chmod 400 my.experiments.com.pem 
Connect to your instance using its Public DNS: 
ec2-13-58-23-167.us-east-2.compute.amazonaws.com 

Example: 
ssh -i "my.experiments.com.pem" [email protected] 

その後、私が行います

$ ssh -vvv -i "my.experiments.com.pem" [email protected] 

、その後、私が手:

debug2: resolving "ec2-13-58-23-167.us-east-2.compute.amazonaws.com" port 22 
debug2: ssh_connect_direct: needpriv 0 
debug1: Connecting to ec2-13-58-23-167.us-east-2.compute.amazonaws.com [13.58.23.167] port 22. 
debug1: Connection established. 
debug1: key_load_public: No such file or directory 
debug1: identity file my.experiments.com.pem type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file my.experiments.com.pem-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_7.5 
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu2.2 
debug1: match: OpenSSH_7.2p2 Ubuntu-4ubuntu2.2 pat OpenSSH* compat 0x04000000 
debug2: fd 3 setting O_NONBLOCK 
debug1: Authenticating to ec2-13-58-23-167.us-east-2.compute.amazonaws.com:22 as 'ubuntu' 
debug3: hostkeys_foreach: reading file "/home/George/.ssh/known_hosts" 
debug3: record_hostkey: found key type ECDSA in file /home/George/.ssh/known_hosts:3 
debug3: load_hostkeys: loaded 1 keys from ec2-13-58-23-167.us-east-2.compute.amazonaws.com 
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521 
debug3: send packet: type 20 
debug1: SSH2_MSG_KEXINIT sent 
debug3: receive packet: type 20 
debug1: SSH2_MSG_KEXINIT received 
debug2: local client KEXINIT proposal 
debug2: KEX algorithms: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c 
debug2: host key algorithms: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa 
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc 
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc 
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: compression ctos: none,[email protected],zlib 
debug2: compression stoc: none,[email protected],zlib 
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal 
debug2: KEX algorithms: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1 
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected] 
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected] 
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: compression ctos: none,[email protected] 
debug2: compression stoc: none,[email protected] 
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: [email protected] 
debug1: kex: host key algorithm: ecdsa-sha2-nistp256 
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none 
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none 
debug3: send packet: type 30 
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY 
debug3: receive packet: type 31 
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:8iA/gquNIyDIY9t1CjUTP1GrkEcZs24QZr8LB2v4aEQ 
debug3: hostkeys_foreach: reading file "/home/George/.ssh/known_hosts" 
debug3: record_hostkey: found key type ECDSA in file /home/George/.ssh/known_hosts:3 
debug3: load_hostkeys: loaded 1 keys from ec2-13-58-23-167.us-east-2.compute.amazonaws.com 
debug3: hostkeys_foreach: reading file "/home/George/.ssh/known_hosts" 
debug3: record_hostkey: found key type ECDSA in file /home/George/.ssh/known_hosts:3 
debug3: load_hostkeys: loaded 1 keys from 13.58.23.167 
debug1: Host 'ec2-13-58-23-167.us-east-2.compute.amazonaws.com' is known and matches the ECDSA host key. 
debug1: Found key in /home/George/.ssh/known_hosts:3 
debug3: send packet: type 21 
debug2: set_newkeys: mode 1 
debug1: rekey after 134217728 blocks 
debug1: SSH2_MSG_NEWKEYS sent 
debug1: expecting SSH2_MSG_NEWKEYS 
debug3: receive packet: type 21 
debug1: SSH2_MSG_NEWKEYS received 
debug2: set_newkeys: mode 0 
debug1: rekey after 134217728 blocks 
debug2: key: my.experiments.com.pem (0x0), explicit 
debug3: send packet: type 5 
debug3: receive packet: type 7 
debug1: SSH2_MSG_EXT_INFO received 
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512> 
debug3: receive packet: type 6 
debug2: service_accept: ssh-userauth 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug3: send packet: type 50 
debug3: receive packet: type 51 
debug1: Authentications that can continue: publickey 
debug3: start over, passed a different list publickey 
debug3: preferred publickey,keyboard-interactive,password 
debug3: authmethod_lookup publickey 
debug3: remaining preferred: keyboard-interactive,password 
debug3: authmethod_is_enabled publickey 
debug1: Next authentication method: publickey 
debug1: Trying private key: my.experiments.com.pem 
debug3: sign_and_send_pubkey: RSA SHA256:liwduQln1POAMqbxk05dlG2yYLzGCmb4gTK3ERUYOJs 
debug3: send packet: type 50 
debug2: we sent a publickey packet, wait for reply 
debug3: receive packet: type 51 
debug1: Authentications that can continue: publickey 
debug2: we did not send a packet, disable method 
debug1: No more authentication methods to try. 
Permission denied (publickey). 

私は彼らが何をお勧めしたのですか:

$ chmod 400 my.experiments.com.pem 

私は、ファイルの変換Puttyに接続しようとしました:puttygen.exemy.experiments.com.pemmy.experiments.com.ppkへ(パテ秘密鍵)が、無成功を。パテを使用して、接続しようとするとエラーポップアップウィンドウにDisconnected: No supported authentication methods available (server sent: publickey)が表示されます。

[EDIT 1]

次の画像上で見ることができるように、インスタンスが鍵ペアで発売されました:aws.playmeetup.com。それが言う

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html#TroubleshootingInstancesConnectingMindTerm

:上で示唆したように、あなたがインスタンスを立ち上げたときに選択した鍵のペアに対応する秘密鍵ファイルを使用していることを確認してください。

enter image description here

+0

ワークステーションはWindowsですか? – gview

+0

AWSのUbuntuインスタンスです。だから、彼らは私に上記の接続ユーザを与える理由です: 'SSHを介して接続する' ubuntu '。 – davidesp

+0

@davidespしかし、あなたのワークステーションはどうですか?つまり、どのOSからEC2インスタンスに接続しようとしていますか? –

答えて

1

あなたがやっている:

$ ssh -vvv -i "my.experiments.com" [email protected]

をするときのようになります。

$ ssh -vvv -i "my.experiments.com.pem" [email protected]

+0

ここで質問をStackOverflow(ちょうど)に投稿するときに間違いを犯しました。上記の質問を修正しました。 – davidesp

0

行うことができますすべての誰もが、推測を行うことであるので、ここで地雷だ:

あなたのスクリーンショットは、キーペアの名前がaws.playmeetup.comだったことを示していますが、あなたが使用しようとしているキーがmy.experiments.com.pemであることを数回述べています。

これは正しいキーではありません。

関連する問題