New router, PVE host can’t connect to network at all: fix it from the console

New router, PVE host can’t connect to network at all? Yeah, that’s a fun one. The fix is almost always in /etc/network/interfaces — the bridge lost its IP or the gateway is wrong. Here’s how to get back online from the console.

Why the host goes dark after a router swap

Your Proxmox host has a bridge (usually vmbr0) that carries the management IP. When you swap the router, the DHCP server changes, and if your bridge was set to DHCP, it gets no address. If it was static, the gateway IP is probably different now. Either way, the web UI is unreachable and every VM behind that bridge is offline.

Get to the physical console

You need a keyboard and monitor on the host. SSH won’t work because the network is down. Log in as root at the console — that’s the only way to edit the network config.

Check the current bridge config

Run cat /etc/network/interfaces. You’ll see something like:

auto vmbr0
iface vmbr0 inet static
    address 192.168.1.100/24
    gateway 192.168.1.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0

If the gateway is the old router’s IP, that’s your problem. If it says inet dhcp, the host never got an address from the new router.

Fix it: set a static IP that matches the new subnet

Edit the file with nano /etc/network/interfaces. Change the address and gateway to match the new router’s subnet. For example, if the new router is at 192.168.50.1:

auto vmbr0
iface vmbr0 inet static
    address 192.168.50.100/24
    gateway 192.168.50.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0

Then restart networking with systemctl restart networking. That should bring the bridge up with the new IP.

If you’d rather use DHCP

Change the stanza to iface vmbr0 inet dhcp and remove the address and gateway lines. Then restart networking. The host will get an IP from the new router — but you’ll have to find it on the router’s DHCP lease table to access the web UI.

What if the bridge itself is missing?

Sometimes the interface name changes after a hardware swap. Run ip link show to see the actual interface names. If the bridge-ports line references eno1 but the interface is now enp3s0, update that line. Then restart networking.

My take

This is a stupid situation to be in, but it’s easy to fix once you’re at the console. The key is to match the bridge config to the new router’s subnet. Don’t bother trying to fix it remotely — you can’t. Also, keep a static IP on the host if you can; it makes router swaps less painful because you only change one number instead of hunting for a DHCP lease.

If the web UI still won’t load after this, check out Cannot Connect to Port 8006 to Access Browser GUI for the next steps.