Proxmox network no longer available after upgrade? Yeah, that’s a punch in the gut. It’s almost always interface renaming or a bridge config that didn’t survive the update. Here’s the checklist I’d run through.
Check what the kernel sees now
After a major upgrade, the kernel can rename your NICs. Your old enp3s0 might now be enp4s0 or something weird. Run ip link show and compare the names to what’s in /etc/network/interfaces. If they don’t match, that’s your problem.
ip link show
cat /etc/network/interfacesIf the names changed, just edit the interfaces file to use the new name. Or better, set a predictable name with a udev rule so it stops happening. But for a quick fix, editing the file works fine.
Bridge config gone stale
Sometimes the upgrade doesn’t rename anything but the bridge loses its port. Check brctl show or bridge link to see if your vmbr0 still has the physical NIC attached. If it’s empty, you need to add it back.
bridge link show
brctl show vmbr0If the port is missing, add it in the interfaces file under vmbr0: bridge-ports enp4s0 (or whatever your NIC is now). Then restart networking with ifreload -a or just reboot.
Driver didn’t load
Less common, but possible: the new kernel doesn’t have your NIC driver built in or it’s blacklisted. Check dmesg | grep -i eth for errors. If you see something like failed to load firmware, you might need to install firmware packages or use an older kernel.
Also check lspci -k to see if a driver is bound to your NIC. If it says Kernel driver in use: none, that’s the issue. Try modprobe the driver manually or install the right package.
My take
This is annoying, but it’s usually a two-minute fix once you see the renamed interface. Don’t go reinstalling Proxmox over it. Just match the config to what the kernel says. And if you’re using ZFS, maybe check out the upgrade path that works before you do another major version bump.
