No connection after reboot

Posted April 3, 2015 30k views

I rebooted my droplet, as I’ve done before, but now I can’t connect to it with putty and pinging the IP address from outside results in timeout.

I can use the Console Access feature in Digital Ocean website. Executing e.g. ping results in destination host unreachable messages.

Unfortunately I don’t have skills to troubleshoot this problem any further. Any suggestions for the next steps?

  • Have you recently run updates on your droplet. If the kernel within your filesystem has been updated you may need to change the kernel image being used to boot your droplet in the control panel to match. A mismatch can cause networking to fail. To do this:

    1.) From the console run the following command to list the currently installed kernel version:

    ls /lib/modules

    2.) Make note of the highest version number listed there and in the control panel navigate to Droplet -> Settings -> Kernel and select this version (for your OS) from the drop down and click “Change”.

    3.) Reboot your droplet from the control panel for the change to take effect.

    If after this you continue to encounter networking issues I would recommend opening a ticket with our support team and they can guide you in additional troubleshooting steps.

  • Thanks for the quick reply. I followed the suggested steps but it didn’t solve the problem, so I’ve opened a support ticket.

  • I was able to solve the problem via support ticket. It appears that using a reboot command wasn’t enough, I had to completely power off the droplet and start it again.

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.

Submit an Answer
7 answers

Had this problem a few times lately. One of the reasons was the default networking interface changed from eth0 to something else (don’t remember right now). The steps I took:

ifconfig -a

from there I can see which devices are available (sometimes this only works after a power cycle), in my case ‘eth0’

then edit /etc/network/interfaces with a static IP to correspond to that one, mine looks like this:

auto eth0
iface eth0 inet static
  address # your droplet IP here

your settings may vary, but this should correspond the original configuration that was on the droplet. the main point is to match the interface to whatever ifconfig -a outputs.

then it’s just a matter of calling

sudo service networking restart

This question was answered by @autti:

I was able to solve the problem via support ticket. It appears that using a reboot command wasn’t enough, I had to completely power off the droplet and start it again.

View the original comment

I followed this and loaded the latest kernel.,
And droplet is pinging now.

But im still not able to ping my domain whose DNS is set to DO IP

Ok rebooted the server again and again ping gone.
Bloody hell.

Experiencing the same issue here. A simple reboot from terminal “sudo reboot” caused my server to go nuts. Still no access.

I still had this problem but found a different solution which may help in the future.
Check wether you have allowed ssh in ufw from the console
sudo ufw status
In my case I had not and rebooting the system enabled the firewall.
So, from the console, you just have to

sudo ufw disable

and reboot. You should be able to ssh afterwards and make sur you have configured ufw properly.

I was missing ifupdown package, so I installed it with

apt install ifupdown

Also I needed to add eth0 static conf as stated by @herrmezz above.

To set network up manually, one could run the following commands on console:

ifconfig eth0 # droplet IP
route add default gw # gateway ip
echo 'nameserver' > /etc/resolv.conf