Related

Tool [NEW] Bandwidth Pricing Calculator Tool
502 bad gateway after root password reset Question Question
cpu from 13% to 100% in one minute Question Question

Question

SSH does not work for droplet created from a backup

Posted November 20, 2019 525 views
NetworkingBackupsUbuntu 16.04

I created a new droplet from a backup of a production server droplet in the control panel. OS is Ubuntu 16.04

I was expecting to be able to SSH to the new droplet with ssh root@<ip address> but I get ssh: connect to host 168.71.110.191 port 22: Operation timed out

I can access the new droplet via the control panel console. When I run systemctl status ssh I see:
ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enab
Active: inactive (dead)

Any ideas why systemd would kill the SSH service? Why would creating a droplet from a backup “break” SSH?

Add a comment
chdev
By:
chdev
Add a comment
1 comment
  • chdev November 20, 2019
    Reply Report

    If it helps, here’s the output of traceroute 168.71.110.191
    Maybe there is a connection problem? 

    traceroute to 168.71.110.191 (168.71.110.191), 64 hops max, 52 byte packets
 1  192.168.6.1 (192.168.6.1)  6.978 ms *  2.146 ms
 2  192.168.66.240 (192.168.66.240)  0.274 ms  0.391 ms  0.227 ms
 3  201.234.55.17 (201.234.55.17)  1.078 ms  1.537 ms  2.531 ms
 4  201.234.55.1 (201.234.55.1)  7.085 ms  8.624 ms  104.879 ms
 5  ae1-300g.ar5.mia1.gblx.net (67.17.94.249)  84.512 ms
    ae0-300g.ar5.mia1.gblx.net (67.17.99.233)  109.035 ms
    ae1-300g.ar5.mia1.gblx.net (67.17.94.249)  84.430 ms
 6  * * *
 7  * * *
 8  192.205.32.209 (192.205.32.209)  140.407 ms  140.036 ms  142.548 ms
 9  cr1.sffca.ip.att.net (12.122.114.6)  138.941 ms
    sffca22crs.ip.att.net (12.122.149.134)  140.785 ms  145.786 ms
10  12.122.2.77 (12.122.2.77)  139.059 ms
    cr2.sl9mo.ip.att.net (12.122.18.13)  139.646 ms  141.555 ms
11  12.122.160.109 (12.122.160.109)  139.579 ms
    12.122.160.113 (12.122.160.113)  144.961 ms
    12.122.160.109 (12.122.160.109)  138.603 ms
12  12.116.180.114 (12.116.180.114)  145.701 ms  143.292 ms  139.362 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
[...]

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
MelodyM November 21, 2019

Hey there! Is there a Cloud Firewall or software firewall filtering traffic for port 22?

**Nmap scan report for 168.71.110.191
Host is up.

PORT STATE SERVICE
22/tcp filtered ssh**

There’s a guide here regarding the error you’re receiving, and if this does not help please open a support ticket so we can take a closer look!

https://www.digitalocean.com/docs/droplets/resources/troubleshooting-ssh/connectivity/#connection-timeout

Reply Report
  • chdev November 21, 2019

    This morning I got “Connection refused” instead of timeout.

    I worked through the troubleshooting-ssh article with no luck so I opened a support ticket

    Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help