- I had an instance which I could smoothly ssh. However, suddenly today I was not able to do it after starting. Since I had an EBS and had edited the /etc/fstab file, some of the answers at stackoverflow said it has some issues with ssh_config file. I detaches the existing EBS, mounted it to a micro instance so as to fix the broken volume. However, I was unable to ssh the new micro.
- I terminated the instance in 1. Created a new one with similar config. Still cannot ssh.
- Just for the sake of it, I created one without an EBS.I can ping both 2 and 3 but not ssh.The exact problem I am facing is this:
Anyone, been there done that?
- Try run ssh with
-vvvvflag to get a sense what is going wrongVor– Vor2015-04-10 17:52:50 +00:00CommentedApr 10, 2015 at 17:52 - This is what it says:pastebin.com/Le0Stjjs Looks like proxy issue. However, I am able to access some other instancesAyushi Dalmia– Ayushi Dalmia2015-04-10 18:17:12 +00:00CommentedApr 10, 2015 at 18:17
2 Answers2
Thanks everyone. It seems that AWS added a new set of IPs which was added to the necessary files since we access it behind a proxy.
Sign up to request clarification or add additional context in comments.
Comments
Looking at the logs, there are chances that your SSH service went down for some reason. I've been there many times in the past few years, and restarting the instance through the EC2 Console did the trick for me sometimes.
My suggestion would be to restart the instance from the EC2 Console, and try SSH-ing into the server again.
Comments
Explore related questions
See similar questions with these tags.

