I’ve seen cases where when you reboot the droplet via ssh the network interface will fail to boot and you will need to do a power off and then power on via the control panel.

It’s rather odd that the resolv.conf needs to be altered as well.

If this is not sorted, I will still recommend to contact our fantastic team and explain that the issue is still present and you would like someone to check this further in order to prevent further issues.

Let me know if you have any questions.

Hello, Harry

May I ask if you’ve made any changes on the droplet itself, e.g installing/uninstalling any packages and have you recently rebooted your droplet as well?

Have you tried contacting Digital Ocean’s support team and ask them to check this on your behalf?

Hello @alexdo

Did I make any changes? No, my droplet was almost 6 months old and everything was normal till last August 2019.

Have I tried contacting support? Yes, [#02897579] and [#02956586].
Did I get some answers? Yes, but it was circling around, it wasn’t solved my problem till I found that’s a link to solve a temporary problem.

It’s been 23 days since my first problem, and it appears again this day.

Did my web still down? No, changing nameserver at /etc/resolv.conf and make eth0 up was solving my problem. But I’m afraid when server reboot, it happens again.

What I need is a permanent solution, not just temporary. Is there any suggestion or link to read?

Regards,
Harry