Inaccessible, won't stay on the network, completely useless

[Desktop4078]

At my wits end here and extremely frustrated. It seems like, if I have a display plugged in, everything works fine. If I don't it's completely useless. My proxmox box boots up, if I'm quick I can log into the web UI, but then it will freeze and that's the end of it... completely inaccessible. No web UI, no ssh, nothing. It was running just fine for nearly 2 days with a display plugged it, then I unplugged it and now I cannot do anything anymore.

Makes zero sense. None. Not a bit. What is the problem?

IP address is assigned by router with static IP

 

[Desktop4078]

Can't even ping it

 

[Desktop4078]

None of the VMs are accessible either

 

[Kingneutron]

If it works with a display, run it with a display connected. Try not to overthink it too much. Weird s--t happens in life all the time.

You mentioned NOTHING about your hardware details, how is anyone supposed to advise? Maybe your rig needs a fake-display dongle.

https://www.amazon.com/Headless-Display-Emulator-Headless-1920x1080-Generation/dp/B06XT1Z9TF?th=1

 

[waltar]

There's a bios option to boot without keyboard, earlier mention as "halt on error" to disable and then you don't need a display also.

 

[gfngfn256]

IP address is assigned by router with static IP

In PVE you should assign the IP address within the node. Probably choose something out of the DHCP range of the router.

(With the monitor plugged in!) Please post output for the following:

cat /etc/network/interfaces


ip a

if I have a display plugged in, everything works fine

Can you then access via the NW through Web GUI & SSH?

 

[Desktop4078]

If it works with a display, run it with a display connected. Try not to overthink it too much. Weird s--t happens in life all the time.

You mentioned NOTHING about your hardware details, how is anyone supposed to advise? Maybe your rig needs a fake-display dongle.

https://www.amazon.com/Headless-Display-Emulator-Headless-1920x1080-Generation/dp/B06XT1Z9TF?th=1

Not an option, I do not have a display that I can dedicate to it. Other Linux OSs run just fine without a display or dummy adapter connected. If a hypervisor cannot run headless then something is wrong with it. I would venture to guess that MOST proxmox deployments are headless.

It's an Intel nuc 8thgen i3

 

[Desktop4078]

In PVE you should assign the IP address within the node. Probably choose something out of the DHCP range of the router.

(With the monitor plugged in!) Please post output for the following:

cat /etc/network/interfaces


ip a

Can you then access via the NW through Web GUI & SSH?

auto lo
iface lo inet loopback

iface eno1 inet manual

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


source /etc/network/interfaces.d/*

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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 1c:69:7a:02:68:9e brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1c:69:7a:02:68:9e brd ff:ff:ff:ff:ff:ff
    inet 192.188.0.5/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::1e69:7aff:fe02:689e/64 scope link  
       valid_lft forever preferred_lft forever

& yes, I can access the web UI when a screen is connected

 

[Desktop4078]

There's a bios option to boot without keyboard, earlier mention as "halt on error" to disable and then you don't need a display also.

I didn't see anything of the like, and I've had other Linux distros running headless with no issues

 

[Desktop4078]

Seems to be especially an issue if I have a VM configured to start on boot. I see the following in the log, could it have anything to do with proxmox dropping off the network?

Nov 13 21:45:23 vm kernel: tap100i0: entered promiscuous mode
Nov 13 21:45:23 vm kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Nov 13 21:45:23 vm kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Nov 13 21:45:23 vm kernel: fwpr100p0: entered allmulticast mode
Nov 13 21:45:23 vm kernel: fwpr100p0: entered promiscuous mode
Nov 13 21:45:23 vm kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Nov 13 21:45:23 vm kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Nov 13 21:45:23 vm kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Nov 13 21:45:23 vm kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Nov 13 21:45:23 vm kernel: fwln100i0: entered allmulticast mode
Nov 13 21:45:23 vm kernel: fwln100i0: entered promiscuous mode
Nov 13 21:45:23 vm kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Nov 13 21:45:23 vm kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Nov 13 21:45:23 vm kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Nov 13 21:45:23 vm kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Nov 13 21:45:23 vm kernel: tap100i0: entered allmulticast mode
Nov 13 21:45:23 vm kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Nov 13 21:45:23 vm kernel: fwbr100i0: port 2(tap100i0) entered forwarding state

I currently do not have a display connected and did not start any VMs on boot or manually, and I am still able to access the web UI

 

[gfngfn256]

So in fact you do have the static IP correctly setup within the Proxmox node. You should not need/have any reserved address within your router for this. Typically (as I said already above) you should have this address OUTSIDE the DHCP range of your router. Check for conflicts.

Seems to be especially an issue if I have a VM configured to start on boot

Do you have some type of passthrough going on within this VM?