How to switch a Proxmox server from a static IP to a DHCP-assigned address at boot, which I needed for a machine being shipped to a remote site for non-technical setup. Covers the edit to /etc/network/interfaces to change the vmbr0 bridge from static to DHCP, plus the follow-up task of updating /etc/hosts once the server has its new address...
DNS resolution failed on a fresh Proxmox install during apt updates because /etc/resolv.conf pointed at 127.0.0.1 instead of the router’s DNS server. After comparing configs on other machines and swapping the network cable, I reinstalled Proxmox from scratch, verified the network settings during setup, and everything worked. This was the third networking issue with this machine, following a DHCP address conflict and a misbehaving managed switch...
My attempt to set up a Jellyfin media server on a mini PC turns into a networking detour: after installing Proxmox, an IP address conflict with a Wi-Fi light bulb leaves the host unreachable over SSH, and reserving a new address doesn’t help because Proxmox hardcodes the IP it picks up via DHCP during installation. It ends with the unresolved problem of deploying the machine to a network with unknown configuration, where Proxmox’s expectation of a static IP is inconvenient...
A newly installed Netgear GS108E managed switch became unreachable a day after going into service, failing to respond to pings and dropping its management interface even though traffic through it still worked. I describe the setup, the symptoms, and why existing search results about VLAN lockouts don’t match this failure on a default configuration...
