By using AWS re:Post, you agree to the Terms of Use

Unable to connect to EC2 Instance through Putty

0

Hello,

I am having trouble connecting to my Ubuntu server through PuTTY. It gives me this error message: Network error:Network error: Connection Refused.

I checked my .ppk file and even re-generated it. I checked other forum messages and have been using the user name: ubuntu@\[Public DNS/IP Address]. I ran into this same issue yesterday after performing an Ubuntu OS update and reboot. I had to create another instance.

I have installed software on the server and was able to successfully exit PuTTY, restart the server, and log back in yesterday. Unfortunately, I was not able to log into it today. I was unable to use the support page because my account is an AWS Educate account, so I decided to post on this forum instead.

My instance id: i-03f8c4cec52fe9701

Thank you,
Kenny

Edited by: Kenny-Y on Jun 6, 2019 11:58 AM

asked 3 years ago36 views
2 Answers
0

I made another instance and reinstalled all the software that I would like to use. I now run into the same problem on another new instance where I am unable to SSH into the instance again.

Instance ID: i-0ab43935f43fc87e9

***As of June 7 4:43 pm EST, I have terminated this second instance to save money but kept the first instance to see if there is any solution available from the community

Edited by: Kenny-Y on Jun 7, 2019 1:43 PM

Edited by: Kenny-Y on Jun 7, 2019 1:43 PM

answered 3 years ago
0

Hello,

Looking over the first instance I can see from the console output the following;

You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.
Press Enter for maintenance
(or press Control-D to continue):

With this error I can be due to a number of reasons: incorrect fstab, corrupt filesystem or a incorrect grub configuration.

Going forward you will need to stop the instance, detach the root volume and attach it as a secondary volume to an instance you can connect to. With this you will need to go to the secondary volume and diagnose the issue.

The following link shows other potential causes.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html#FilesystemGeneral-potential-cause

answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions