All geek questions in one place

EC2 cannot reboot via ssh after reboot

I connected my ec2 instance via ssh, after adding a new EBS volume I restarted the machine using 'sudo shutdown -r now'

And after that I tried to access using the follwing command:

ssh -v -i primary_key.pem ubuntu@ec2-23-22-245-160.compute-1.amazonaws.com

which is rebuilt as shown below:

 OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011 debug1: Reading configuration data /Users/caveman/.ssh/config debug1: Reading configuration data /etc/ssh_config debug1: Applying options for * debug1: Connecting to ec2-23-22-245-160.compute-1.amazonaws.com [23.22.245.160] port 22. debug1: Connection established. debug1: identity file primary_key.pem type -1 debug1: identity file primary_key.pem-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1 debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.6 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: Host 'ec2-23-22-245-160.compute-1.amazonaws.com' is known and matches the RSA host key. debug1: Found key in /Users/caveman/.ssh/known_hosts:31 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: Trying private key: primary_key.pem debug1: read PEM private key done: type RSA debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. Permission denied (publickey).

What's wrong? Any point I'm missing?

+6
source share
2 answers

This is the normal behavior of Amazon EC2. After restarting the instance, the public Ip associated with it will be changed (yours was ec2-23-22-245-160.compute-1.amazonaws.com ).

There are two ways to connect your instance via ssh

  • Log in to your Amazon AWS console and verify that the instance starts up, then copy Public DNS and try connecting to ssh. (the ssk key is the same)

  • If you do not want your IP address of your instance to change each time you restart / terminate, use Elastic IP. Elastic Ips associated with the account (and not with the instance), so you can assign Elastic Ip on any instance you are interested in.

You can connect to ssh ssh -v -i primary_key.pem ubuntu@ <ElasticIp>

+11
source

I had a similar problem. Here is what I did ..!

 ssh -i < .pem file> -vvv <server IP>

The above command will show the debug logs, and after the ECDSA key is accepted, you are located.

0
source

Source: https://habr.com/ru/post/925603/

More articles:


All Articles