I’ve spent the last several hours trying to figure out what’s going on, but I’m totally stuck.
I was trying to upgrade my droplet from Ubuntu 20.x to Ubuntu 22.x using this guide. Now my networking doesn’t work.
How do I troubleshoot this?
Thanks for any help!
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!
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.
To answer my own question via DO support (thanks Mubashir!)…
The issue was with “systemd’s predictable network interface naming”.
The solution was to turn it off via GRUB.
So the answer above didn’t work for me. What I ended up doing was creating a new YAML file at /etc/netplan/config.yaml with the following content:
If your droplet gateway is on a different subnet (i.e. more than just the last set of numbers in the IP address and gateway IP address are different), you need to include the “on-link” line.
Save the file and then run this command:
followed by
That will set the static IP and gateway address and make it persist past reboots.
If you need to temporarily add the static IP address and gateway, use these commands:
This will give you connectivity in order to run updates and install additional packages, but that connectivity will not persist on reboot.
I hope this helps someone.
In my case the issue was caused by the fact that
eth0
was replaced byens0
. In order to check what your card name is :as you can see I have no
eth0
but I have a “suspicious”ens3
.Cross reference the findings with what’s inside
/etc/network/interfaces.d/50-cloud-init.cfg
At that point I changed the occurrences of
eth0
withens3
incloud-init.cfg
and tried to manually up/down my network :all up and running.
Reboot
njoy :)