Question

All Droplets after Snapshot blocks Port 22 london location

Hi, I am using Apache 16.04 with Ispconfig. Every time i do a Snapshot with the following steps

shutdown -h now and then i wait for couple of seconds and then i start doing the snapshot from the digitalocean Control panel . after doing that i power on my droplet from the control panel .

After that i get this issue

  1. cant ssh into the server get ssh: connect to host my-ip-address port 22: Connection refused
  2. site is down on the browser also i get " This site can’t be reached "
  3. Ip is down on the browser

What is the issue over here . after the snapshot does it block all my ports This have happened with 4 of my droplets in this month ( MARCH ) so i had to destroy and Install everything back again. Its time consuming. when i contact the support they put my droplet in recovery mode .

Kindly Please help me figure this issue .

Thanks

Subscribe
Share

Submit an 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.

This comment has been deleted

The issue was that i didnt had setup my firewall and after snapshot and power off and on all the firewall were blocked so to solve this i had to follow this usefull links

https://askubuntu.com/questions/144364/ssh-connect-to-host-myremotehost-com-port-22-connection-refused https://www.howtoforge.com/tutorial/ufw-uncomplicated-firewall-on-ubuntu-15-04/

Hi thanks a lot buddy i fixed that had to start all the ports in the ufw firewall . Can you please help me by checking if all the belwo ports are correct and are not vernuable to any attack

oot@cloud:~# ufw status numbered Status: active

 To                         Action      From
 --                         ------      ----

[ 1] 22 ALLOW IN Anywhere
[ 2] 22/tcp ALLOW IN Anywhere
[ 3] 80 ALLOW IN Anywhere
[ 4] 443 ALLOW IN Anywhere
[ 5] 21/tcp ALLOW IN Anywhere
[ 6] 6000:6007/tcp ALLOW IN Anywhere
[ 7] 6000:6007/udp ALLOW IN Anywhere
[ 8] Anywhere ALLOW IN 15.15.15.51
[ 9] Anywhere ALLOW IN 15.15.15.0/24
[10] 22 ALLOW IN 15.15.15.0/24
[11] 80 on eth0 ALLOW IN Anywhere
[12] 3306 on eth1 ALLOW IN Anywhere
[13] 80,443/tcp ALLOW IN Anywhere
[14] 25 ALLOW IN Anywhere
[15] 143 ALLOW IN Anywhere
[16] 993 ALLOW IN Anywhere
[17] 110 ALLOW IN Anywhere
[18] 995 ALLOW IN Anywhere
[19] 22 (v6) ALLOW IN Anywhere (v6)
[20] 22/tcp (v6) ALLOW IN Anywhere (v6)
[21] 80 (v6) ALLOW IN Anywhere (v6)
[22] 443 (v6) ALLOW IN Anywhere (v6)
[23] 21/tcp (v6) ALLOW IN Anywhere (v6)
[24] 6000:6007/tcp (v6) ALLOW IN Anywhere (v6)
[25] 6000:6007/udp (v6) ALLOW IN Anywhere (v6)
[26] 80 (v6) on eth0 ALLOW IN Anywhere (v6)
[27] 3306 (v6) on eth1 ALLOW IN Anywhere (v6)
[28] 80,443/tcp (v6) ALLOW IN Anywhere (v6)
[29] 25 (v6) ALLOW IN Anywhere (v6)
[30] 143 (v6) ALLOW IN Anywhere (v6)
[31] 993 (v6) ALLOW IN Anywhere (v6)
[32] 110 (v6) ALLOW IN Anywhere (v6)
[33] 995 (v6) ALLOW IN Anywhere (v6)

It sounds like none of the Droplet’s services are being started on reboot. If you try to access your Droplet using the Remote Console in the control panel, do you see any errors?

Try to log in as root (you can reset your password through the control panel if necessary) and run the following command to start OpenSSH:

sudo systemctl start ssh