Question

Networking not working after droplet resize

Hello Everyone, I resized my droplet yesterday and the process went through without any errors or warnings. When I powered on, I discovered that my networking had stopped working. I’m able to access it through the web console but not able to ping my IP from outside and ping from within the droplet doesn’t work. It shows: “Network is unreachable” I’m not even able to ping the gateway.

I checked my routing table and it looks empty. When I try to add a routing rule it says “Error: Nexthop has invalid gateway”

Here’s my /etc/network/interfaces : https://prnt.sc/oygq1e

Anybody tell me what I’m missing or doing wrong?

Thanks!

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.

Sachin Mehta • August 30, 2019
Accepted Answer

So I managed to fix the issue. Turns out my both interfaces eth0 and eth1 are going down after a reboot. I have to run the following after that:

ip link set eth0 up ip link set eth1 up ip addr flush dev eth0 ip addr add X.X.X.X/20 dev eth0 route add default gw Y.Y.Y.Y eth0

X.X.X.X is your droplet’s IP and Y.Y.Y.Y is your gateway

These settings vanish after a reboot. Anyone who know why?

@alexgeorgiev Thank you so much for your help :)

Thanks!

Paul Nowoczynski • February 3, 2022

Twice now I’ve seen this happen and both times my fix has been to (re)install the cloud-init and cloud-guest-utils packages.

pbfall • May 29, 2020

Hi everyone, I have the same problem after resizing my droplet. Do some has a solution for this?

vasiliypupkin • April 13, 2020

Thanks a lot for the solution! Got the same issue on 2 different droplets without any resizing (once in Dec.2019, once in Apr.2020). We were not doing anything to the servers or software, it just happened by itself. DigitalOcean support yet insists it happened due to our actions.