Droplet found to be shutdown suddenly. After restart, no internet connection.

Droplet was found to be shutdown. After restart, it can’t connect to the internet.

From the droplet, no external site can be pinged (including

The droplet was working absolutely fine before and was suddenly found to be shut down and in this disconnected state after restart.

The droplet is an Ubuntu 14.04.2 server instance.


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.

Thanks, I have in fact opened a support ticket already. Following up with Support, and will try out your suggestion about changing the kernel version in the control panel, in case Support is not able to point me in the right direction.

I would recommend opening a ticket with our support team for this issue. There are a couple reasons why your droplet could be found in an off state:

  • A process within the droplet initiated a shutdown
  • Someone with access to your account shut the droplet down via the control panel or API

All other processes that shut down a droplet such as maintaince or a hypervisor migration attempt a restart as soon as the process is completed. Our support team will be able to tell if the droplet was shut down from the control panel or API or if the shutdown came from a process within the droplet.

As far as losing networking, the most common reason for this is if the kernel image used to boot your droplet is not the same kernel version installed within your filesystem. Because kernel changes take effect on a reboot if you had previously updated your kernel but had not updated the kernel in the control panel to match you would find this problem the next time the droplet rebooted.