Question

My network has stopped working since the latest reboot

My droplet must have rebooted because all of a sudden the network stopped working on it. I’ve tried several things. I can access it via the console, but i’m unable to ping it’s ip, nor am I able to ping 8.8.8.8 from inside the droplet itself.

I have a support ticket out, but they haven’t answered me in over 2 days so I’m getting desperate. Here are a few of the commands they asked me to send them.

$ iptables -L
Chain INPUT (policy ACCEPT)
target      prot opt source             destination

Chain FORWARD (policy ACCEPT)
target      prot opt source             destination

Chain OUTPUT (policy ACCEPT)
target      prot opt source             destination

$ iptables -t nat -L
same thing as above except PREROUTING and POSTROUTING are there too

$ ip route
default via 104.236.128.1 dev eth0
10.12.0.0/16 dev eth0 proto kernel scope link src 10.122.0.5
104.236.128.0/18 dev eth0 proto kernel scope link src {MY IP which starts with 104.236 but then is different from the gateway}

$ ip addr show
this has an lo and an eth0, but i'm not going to type it out :)

$ cat /etc/resolv.conf
# comments
nameserver 8.8.8.8
nameserver 8.8.4.4

$ ls -lah /lib/modules
4.4.0-28-generic

$ uname -a
Linux dev-box.localdomain 4.4.0-28-generic #...

If you have any ideas please let me know.

Show comments

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

I’ve made it a point to keep two snapshots of each droplet. After I take a snapshot, I reload that snapshot instead of booting. That is, I want to know that the snapshot is bootable and hopefully functional.

I say hopefully functional because daemonized (sp) programs sit in ram and sometimes don’t work when reloaded. I only mention this because I’m in amavisd-new hell, or more correctly, perl5 hell.

Specific to your problem, the ifconfig as someone requested would be useful. When I screw up the network, generally my IP does not appear in inconfig even though the vtnet is present.

This comment has been deleted