Hi, I'm new to Proxmox. Loving the system and being able to tinker and monitor everything. I've had it up and running for a few days now, and its been flawless. Anytime I've run into something I didn't understand, I was able to figure it out with a quick forums search. However I've seemed to run into a problem I can't figure out on my own. I just an hour ago shutdown my whole server for maintenance, and upon booting it back up I can no longer reach the web interface at all. Just get an unable to connect error, ping gives a host unreachable. Nothing changed while it was down, so I'm very confused why it's no longer connected to my network.
Unable To Connect
- Thread starter Malvazar
- Start date
What was the point of the maintenance? Did you add or remove any PCIe cards or NVMe SSDs? If yes then your NIC name probably has changed because it is named after the used bus and you have to fix the NIC name in your /etc/network/interfaces via local terminal or webKVM.
Last edited:
Can you login to the Proxmox host console (with a physical keyboard and display) and show us the output of
cat /etc/network/interfaces and ip a?Because I'm planning on doing a network upgrade. Wanted to get the machine cleaned out, and ready for new parts.
Yes I can login via the console.
cat /etc/network/interfaces
Code:
auto lo
iface lo inet loopback
iface enp5s0 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.0.122/24
gateway 192.168.0.1
bridge-ports enp5s0
bridge-stp off
bridge-fd 0ip a
Code:
1: lo: <LOOPBACK,UP,LOWER UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp6s0: <BROADCAST, MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether d8:cb:8a:5e:37:50 brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST, MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ca:68:66:ce:a1:bf brd ff:ff:ff:ff:ff:ff
inet 192.168.0.122/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::c868:66ff: fece:a1bf/64 scope link
valid_lft forever preferred_lft forever
4: tap100i0: <BROADCAST, MULTICAST, PROMISC,UP,LOWER UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
link/ether 5a:5a:a3:f4:50:7d brd ff:ff:ff:ff:ff:ff
Last edited:
Did you add a PCI(e) device or enable a device in the BIOS that was disabled before? Did you shuffle add-in cards between PCI(e) slots?
Your network configuration mentions enp5s0 (twice), while the current name of your network controller is enp6s0. Please adjust your network configuration accordingly.
This happens when a new PCI(e) device is inserted/enabled that happens to come earlier in the PCI IDs. (Many threads about that on this forum.)
