Report this

What is the reason for this report?

SSH does not work for droplet created from a backup

Posted on November 20, 2019

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?



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

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.

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

I have also encountered this, it is a really pain in the butt

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.