I'm facing a strange issue with my Proxmox cluster and would appreciate some guidance. After a recent update on two of my nodes, the desktop version of the web GUI is blank, while the mobile version works perfectly.
Background / Recent Changes:
I have a cluster of several Proxmox servers.
Yesterday, I ran apt update followed by apt upgrade on two of the nodes. I was working via SSH and didn't check the GUI at that time.
Today, I can no longer access the desktop Web GUI on those two updated nodes.
Crucially, one node in the cluster that I did not update still has a perfectly working desktop GUI. This strongly suggests the update caused the issue.
Symptoms on the Updated Nodes:
When I navigate to https://<server-ip>:8006, I get the usual self-signed certificate warning, which I accept.
After that, the screen is completely blank/white. No login prompt ever appears.
This happens on multiple browsers (Chrome, Firefox) and different computers, even after clearing the cache.
SSH access to the nodes works perfectly.
All guest VMs and containers are running without any problems.
The mobile version of the UI works correctly when I access it from my phone.
If I use browser developer tools to force a mobile user agent on my desktop, the mobile UI loads successfully. The problem is specific to the desktop UI.
Troubleshooting Steps I've Already Taken:
Confirmed that pveproxy and pvedaemon services are active (running) using systemctl status.
Rebooted the affected nodes multiple times.
Attempted to reinstall key packages with apt install --reinstall pve-manager proxmox-widget-toolkit, which did not solve the issue.
pveversion -v
proxmox-ve: 9.0.0 (running kernel: 6.14.11-3-pve)
pve-manager: 9.0.10 (running version: 9.0.10/deb1ca707ec72a89)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.14.11-3-pve-signed: 6.14.11-3
proxmox-kernel-6.14: 6.14.11-3
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 19.2.3-pve2
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx10
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.11
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 1.1.8
libpve-rs-perl: 0.10.10
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-1
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.15-1
proxmox-backup-file-restore: 4.0.15-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.2
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-widget-toolkit: 5.0.6
pve-cluster: 9.0.6
pve-container: 6.0.13
pve-docs: 9.0.8
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.17-1
pve-ha-manager: 5.0.4
pve-i18n: 3.6.0
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.22
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve2
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1
Does anyone have any idea what component might have failed during the update to cause this specific behavior? Any suggestions on what to check next would be a great help.
Thanks in advance!
Background / Recent Changes:
I have a cluster of several Proxmox servers.
Yesterday, I ran apt update followed by apt upgrade on two of the nodes. I was working via SSH and didn't check the GUI at that time.
Today, I can no longer access the desktop Web GUI on those two updated nodes.
Crucially, one node in the cluster that I did not update still has a perfectly working desktop GUI. This strongly suggests the update caused the issue.
Symptoms on the Updated Nodes:
When I navigate to https://<server-ip>:8006, I get the usual self-signed certificate warning, which I accept.
After that, the screen is completely blank/white. No login prompt ever appears.
This happens on multiple browsers (Chrome, Firefox) and different computers, even after clearing the cache.
SSH access to the nodes works perfectly.
All guest VMs and containers are running without any problems.
The mobile version of the UI works correctly when I access it from my phone.
If I use browser developer tools to force a mobile user agent on my desktop, the mobile UI loads successfully. The problem is specific to the desktop UI.
Troubleshooting Steps I've Already Taken:
Confirmed that pveproxy and pvedaemon services are active (running) using systemctl status.
Rebooted the affected nodes multiple times.
Attempted to reinstall key packages with apt install --reinstall pve-manager proxmox-widget-toolkit, which did not solve the issue.
pveversion -v
proxmox-ve: 9.0.0 (running kernel: 6.14.11-3-pve)
pve-manager: 9.0.10 (running version: 9.0.10/deb1ca707ec72a89)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.14.11-3-pve-signed: 6.14.11-3
proxmox-kernel-6.14: 6.14.11-3
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 19.2.3-pve2
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx10
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.11
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 1.1.8
libpve-rs-perl: 0.10.10
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-1
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.15-1
proxmox-backup-file-restore: 4.0.15-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.2
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-widget-toolkit: 5.0.6
pve-cluster: 9.0.6
pve-container: 6.0.13
pve-docs: 9.0.8
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.17-1
pve-ha-manager: 5.0.4
pve-i18n: 3.6.0
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.22
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve2
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1
Does anyone have any idea what component might have failed during the update to cause this specific behavior? Any suggestions on what to check next would be a great help.
Thanks in advance!
