Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Troubleshooting: EC2 SSH connection refused after reboot

by | Oct 7, 2021

Was your EC2 SSH connection refused after reboot? You are in luck! The Support Team at Bobcares is well-versed in finding solutions for challenging issues like this one.

If you have been at the receiving end of Connection timed out or Connection refused error messages when attempting to connect to EC2 via SSH, our Support Engineers have a solution for you.

How to fix EC2 SSH connection refused after reboot?

The EC2 SSH connection error often arises due to issues with connecting to the instance. In other words, the request has failed to reach the instance and winds up timing out. This error may also occur if a firewall has blocked access or if SSH is not running on the instance.

Resolving: EC2  SSH instance after reboot connection error

  1. First, stop the broken instance.
  2. Then go to the EC2 Management Console and navigate to Elastic Block Store. After that, select Volumes and right-click on the volume related to the instance you stopped in the previous step.
  3. Next, start a new instance, Make sure it is in the same region and also of the same OS as the instance we stopped earlier. After that, attach the original EBS root volume to the new instance as a secondary volume.
  4. After you have mounted the broken volume on other instance, go to the /etc/sshd_config file and check for duplicate entries with these commands:
    cd /etc/ssh
    sudo nano sshd_config

    Then use ctrl-v a couple of times to go to the bottom of the file.
    After that use ctrl-k on the lines at the bottom that mentions “UseDNS no” and “PermitRootLogin without-password”.
    Following this save the edited file and exit.

  5. The next step is to fix the reason behind the error by running the following commands:
    cd /etc
    sudo nano rc.local

    Then find the lines consisting of “PermitRootLogin without-password” and delete them. Then save the edited file and exit.

  6. After that, unmount the volume.
  7. Then go to the EC2 Management Console and navigate to Elastic Block Store. After that, select Volumes and right-click on the volume related to the instance you stopped in the previous step.
  8. Reattach it to the new instance and start it again.

[In search of help? Try our Server Management Services.]

Conclusion

In brief, we learned what to do when faced with a Connection timed out or Connection refused error message. Our Support Engineers demonstrated how to stop the error by getting to the root cause.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF