Proxmox VM unreachable after new install is usually one of three layers: the host, the bridge, or the guest. Don’t guess. Run these commands in order and you’ll know which one.
Check the host first
On the Proxmox host, run ip a. Look for vmbr0 and confirm it has an IP. If it doesn’t, your bridge is down. Bring it up with ifup vmbr0.
Now ping your gateway. If that fails, your host network is broken. Check /etc/network/interfaces for typos. It’s easy to mess up the bridge ports line.
Then the bridge
Run bridge link show. You should see your physical NIC (like eno1) and the VM’s tap interface both listed as members of vmbr0. If the tap interface is missing, the VM isn’t attached to the bridge.
Check the VM’s hardware tab in the web UI. The network device should be set to virtio or e1000 and bridged to vmbr0. If it’s set to NAT or none, that’s your problem.
Finally the guest
If the host and bridge look fine, the issue is inside the VM. Boot it with a console and run ip a there. No IP? Then the guest’s network config is wrong, or the driver didn’t load.
For Linux guests, check /etc/network/interfaces or netplan. For Windows, open Device Manager and look for a yellow bang on the network adapter. Install the virtio drivers if needed.
My take
This is annoying but fixable. Most of the time it’s a simple config mistake. The bridge commands narrow it down fast. If you’re still stuck, this post on fixing a PVE host with no network has more console-level tricks.
