I woke up this morning to find that at 3:30am this morning JetPack informed me that my website was unavailable. A few moments later I received an update from my 3rd-party monitoring that told me that SSH, HTTP, HTTPS were all unavailable on my host.

I had to resort to using my console to connect to my VM, which was running. Upon inspection I found that eth0 was missing on the VM. I ran dmesg and found that eth0 was being renamed to ens4. I changed my interfaces lines from eth0 to ens4 and restarted networking. ens4 now gets the ip address I expect, but I have no network connectivity. I cannot even ping the gateway, it says host unreachable.

I need some advice here, I’m not getting very helpful answers from DO Support other than to check files which all look normal to me.

All I have to go on is at 3:30am or so there is a log of my Droplet powering on - I wasn’t awake at 3:30am. I don’t know who or what authorized a power on of the VM, but what I do know is that I am with a VM with 2 websites that is down.

1 comment
  • Update: I changed eth0 from ens4 which apparently was incorrect. I have changed it to ens3. I then restarted networking.

    I can now ping the gateway, but that’s about it…

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.

×
1 answer

Andddddd I rebooted after changing the /etc/networking/interfaces from eth0->ens4->ens3 and now my droplet is working.

Submit an Answer