Proxmox webinterface not working after a shutdown period

Operating Systems & Open Source Open Source & Web-Based
, ,
1

Hi
I haven’t restartd the server for a couple of weeks again. And now it cannot find the LAN, even though it has a correct IP address, default gateway, dns server and networkmask. I am honestly bufled by this.

The server in question is an IBM X3550 M3 with the singe dual port broadcom-NIC connected to switch with CAT6/CAT5e cabling. I didn’t have the issue the last time I used this. It is running proxmox 7.3.
And no response on local pings

Here is my network config

auto lo
iface lo inet loopback

Iface eno1 inet manual

iface eno2 inet manual

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

what does ip link say?

1 Like
3

The interfaces are down
Apart from the loopback interface which is unknown

4

whats in your /etc/hosts file?
also, is there anything on your network that does DHCP for other devices?

1 Like
5

Only the router

127.0.0.1 localhost.localdomain localhost
192.168.1.222 svr.2home svr2

#following lines are desirable IPv6 hosts

::1 ip6-localhost ip6-loopback
fe00::00 ip6-localnet
ff00::0 ip6 mcastprefix
ff02::1 ip6 allnodes
ff02::1ip6 allrouters
ff02::3 ip6-allhosts

That is the full output
I am copying these over manually since I don’t currently have SSH either.

6

did you block out 192.168.1.222 so it does not hand it out?

and do VMs on this also loose connectivity?

7

Currently looking at it, I cannot see it in use
To reserve that IP, I need to tear the Server open and get the MAC address for that…

If I understood you correctly, the server was offline, so were all the VM’s. And none of them are autostart. So I cannot really say…

8

the ‘hacky’ way to do this is to just put 00:00:00:00:00:00 in the reservation field. you are setting the IP on the server manually so it is fine. also you can get the mac from linux with ifconfig or the new ip utility. if the DHCP server hands out your server IP because it does not know about the static device it will cause failure to connect issues.

it is possible for the host to loose network but the VMs not too, this can be used for troubleshooting info.

run the command:
ip address

this will dump a lot of nic info too

1 Like
9

In short, adding the Ip to the whitelist did the job. I cannot see why, but it did it. Seems like my understanding of DHCP is totally off :man_facepalming:

In short, it was that router DHCP setting, and whitelisting it fixed it.

Thanks @Zedicus and @MadMatt for your time and help!
I really appriciate it!

1 Like
10

a network can not use the same IP address on 2 devices.
DHCP does not know about statically configured servers.
DHCP will eventually give out the same IP address as what the server was statically set to, unless you tell DHCP to not to.

1 Like