I'm having trouble connecting to AWS via SSH. I've created a new Ubuntu instance, and tried connecting with the following:
- using ubuntu@, ec2-user@, and root@
- using the amazon DNS name (ec2-[ip address].compute-1.amazonaws.com), and public IP
- both as admin and as normal user on local machine
The weird thing is, I can connect to other EC2 instances on the same AWS account just fine. The new instance is using the same public key as the others, and has the same security group. I've attached a unique Elastic IP to this one (same as the others), still no luck connecting. Any help would be greatly appreciated.
Here's the output I'm getting:
OpenSSH_5.9p1, OpenSSL 0.9.8y 5 Feb 2013
debug1: Reading configuration data /Users/kellen/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 53: Applying options for *
debug1: Connecting to ec2-23-21-192-105.compute-1.amazonaws.com [23.21.192.105] port 22.
debug1: Connection established.
debug1: identity file /Users/kellen/.ssh/id_rsa type 1
debug1: identity file /Users/kellen/.ssh/id_rsa-cert type -1
debug1: identity file /Users/kellen/.ssh/id_dsa type 2
debug1: identity file /Users/kellen/.ssh/id_dsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1.1
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr 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: Server host key: RSA 85:08:d6:22:55:0c:6b:de:3f:17:1d:23:3f:5a:ec:52
The authenticity of host 'ec2-23-21-192-105.compute-1.amazonaws.com (23.21.192.105)' can't be established.
RSA key fingerprint is 85:08:d6:22:55:0c:6b:de:3f:17:1d:23:3f:5a:ec:52.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'ec2-23-21-192-105.compute-1.amazonaws.com,23.21.192.105' (RSA) to the list of known hosts.
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
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: private_key.pem
debug1: Authentications that can continue: publickey
debug1: Offering RSA public key: /Users/kellen/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Offering DSA public key: /Users/kellen/.ssh/id_dsa
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).
I'm having trouble connecting to AWS via SSH. I've created a new Ubuntu instance, and tried connecting with the following:
- using ubuntu@, ec2-user@, and root@
- using the amazon DNS name (ec2-[ip address].compute-1.amazonaws.com), and public IP
- both as admin and as normal user on local machine
The weird thing is, I can connect to other EC2 instances on the same AWS account just fine. The new instance is using the same public key as the others, and has the same security group. I've attached a unique Elastic IP to this one (same as the others), still no luck connecting. Any help would be greatly appreciated.
Here's the output I'm getting:
OpenSSH_5.9p1, OpenSSL 0.9.8y 5 Feb 2013
debug1: Reading configuration data /Users/kellen/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 53: Applying options for *
debug1: Connecting to ec2-23-21-192-105.compute-1.amazonaws.com [23.21.192.105] port 22.
debug1: Connection established.
debug1: identity file /Users/kellen/.ssh/id_rsa type 1
debug1: identity file /Users/kellen/.ssh/id_rsa-cert type -1
debug1: identity file /Users/kellen/.ssh/id_dsa type 2
debug1: identity file /Users/kellen/.ssh/id_dsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1.1
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr 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: Server host key: RSA 85:08:d6:22:55:0c:6b:de:3f:17:1d:23:3f:5a:ec:52
The authenticity of host 'ec2-23-21-192-105.compute-1.amazonaws.com (23.21.192.105)' can't be established.
RSA key fingerprint is 85:08:d6:22:55:0c:6b:de:3f:17:1d:23:3f:5a:ec:52.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'ec2-23-21-192-105.compute-1.amazonaws.com,23.21.192.105' (RSA) to the list of known hosts.
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
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: private_key.pem
debug1: Authentications that can continue: publickey
debug1: Offering RSA public key: /Users/kellen/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Offering DSA public key: /Users/kellen/.ssh/id_dsa
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).
0 commentaires:
Enregistrer un commentaire