Proxmox web ui not reachable after unplug

[Andrei18]

Hey, I know there's a lot of threads on this, but can't find anything to help me fix it. I have a new proxmox instance installed on my old pc for around a week, everything was fine, just playing around with some lxc's and networking stuff, like setting up some cloudflare tunnels, just testing some scenarios, did multiple reboots over the last week, this weekend the pc was shut down, starting without any issue afterwards. Yesterday I had to completely unplug it, had to take out my GPU for some mods, and now after reinstalling it and booting back up, I can't reach the web UI anymore...

Thought this would be some networking stuff, since I didn't have the ip reserved, but I can't figure it out, everything looks perfect...

So I have access to the server manually, and I tried:
ip a -> shows the same address, the old one, 198.162.1.136/24
ping google.com -> works fine
ping 8.8.8.8 -> works fine
added 198.162.1.136 as a reserved address in my router, even tho I also checked connected devices and the server was already showing with this address assigned...but still nothing
ip route list -> default via 192.168.1.1 dev vmbr0 proto kernel onlink \ 192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.136

don't know what else to try...only thing weird are these errors in journalctl, that I can't really find much on:

Sorry in advance if this is wrongly placed or redundant, I'm new here! XD

 

[bbgeek17]

Hi @Andrei18 , welcome to the forum.

Have you played with clustering this system at any point? The screenshot indicates that not all PVE services are starting. You can check "systemctl" for additional information. Also, "journalctl -b0" may be informative.
You mentioned that pings work, are you able to SSH into this server? If you are, providing information in Text format encoded with CODE tags would be more helpful than screenshots.

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Andrei18]

Hi @Andrei18 , welcome to the forum.

Have you played with clustering this system at any point? The screenshot indicates that not all PVE services are starting. You can check "systemctl" for additional information. Also, "journalctl -b0" may be informative.
You mentioned that pings work, are you able to SSH into this server? If you are, providing information in Text format encoded with CODE tags would be more helpful than screenshots.

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

hey man, thanks for taking the time to reply!

I don't think I have, it's just a fresh instance, I have only an LXC with cloudflared, an LXC with an uptime kuma, and a small ubuntu server VM.

I managed to ssh into it now, this is the output of journalctl -b0:
root@pve-node-1:~# journalctl -b0
Mar 31 13:32:34 pve-node-1 kernel: Linux version 6.17.2-1-pve (build@proxmox) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (G>
Mar 31 13:32:34 pve-node-1 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.17.2-1-pve root=/dev/mapper/pve-root ro qui>
Mar 31 13:32:34 pve-node-1 kernel: KERNEL supported cpus:
Mar 31 13:32:34 pve-node-1 kernel: Intel GenuineIntel
Mar 31 13:32:34 pve-node-1 kernel: AMD AuthenticAMD
Mar 31 13:32:34 pve-node-1 kernel: Hygon HygonGenuine
Mar 31 13:32:34 pve-node-1 kernel: Centaur CentaurHauls
Mar 31 13:32:34 pve-node-1 kernel: zhaoxin Shanghai
Mar 31 13:32:34 pve-node-1 kernel: BIOS-provided physical RAM map:
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009d1efff] usable
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x0000000009d1f000-0x0000000009ffffff] reserved
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x000000000a20e000-0x000000000affffff] usable
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000c347bfff] usable
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000c347c000-0x00000000c347cfff] reserved
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000c347d000-0x00000000ca648fff] usable
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000ca649000-0x00000000ca9acfff] reserved
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000ca9ad000-0x00000000cab07fff] ACPI data
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000cab08000-0x00000000caef1fff] ACPI NVS
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000caef2000-0x00000000cbbfefff] reserved
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000cbbff000-0x00000000ccffffff] usable
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000cd000000-0x00000000cfffffff] reserved
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Mar 31 13:32:34 pve-node-1 kernel: BIOS-e820: [mem 0x00000000fd600000-0x00000000fd7fffff] reserved

 

[bbgeek17]

I managed to ssh into it now, this is the output of journalctl -b0:
root@pve-node-1:~# journalctl -b0
Mar 31 13:32:34 pve-node-1 kernel: Linux version 6.17.2-1-pve (build@proxmox) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (G>

Hi. The output you provided is from the very first moments of your PC boot. It contains nothing of value for the question at hand.

I've asked AI to generate a quick list of commands that can assist in troubleshooting a failed PVE instance. Please run them, examine them first on your own. If you do not find anything that helps, post the data here.

Do use CODE tags when pasting text. You can find them in the menu of the reply Text box. The icon is </>.
If the output is long, you can use SPOILER tag, or attach a file.

Good luck

pveversion -v
uname -a
uptime
systemctl list-units --failed
systemctl status pve-cluster
systemctl status corosync
systemctl status pvedaemon
systemctl status pveproxy
systemctl status pvestatd
journalctl -b -p err
journalctl -u pve-cluster -b
journalctl -u corosync -b
journalctl -u pvedaemon -b
journalctl -u pveproxy -b
journalctl -u pvestatd -b
pvecm status
pvecm nodes
qm list
pct list
lsblk
df -h
mount | grep -E "pve|lvm|zfspool"
zpool status
zfs list
cat /etc/pve/.members
cat /etc/pve/storage.cfg
ip a
ip r
ss -tulnp
free -h
dmesg | grep -i error

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox