Unable to see WebGUI

W

waggs15

New Member
Oct 2, 2025
5
0
1
Pretty randomly unable to access the WebGUI. Worked yesterday, doesn't work today. There was no reboot prior to attempting to access it. Assumed a reboot might help, but it did not. The webpage shows an attempt to load, screen goes grey and nothing shows up. Containers and VMs are still working, as is evidence by Plex still working. I found an old thread with the follow questions so I'll answer those first and post some pictures here to hopefully find a solution to this.

What is the IP of the PVE server? 10.0.0.10
What is the IP of your workstation? Any on the network, but main computer used to access would be 10.0.0.102 (DHCP address)
What is the IP of your gateway? 10.0.0.1
Can you ping the PVE server? Yep, pings just fine
Can you ssh into PVE server? Yes.
What is the output of "ip a" on PVE? Pictures attached (there's quite a few in there that are from the LXCs running, but the main ones used are at the top included in the photo.)
What is the corresponding output from your workstation? (ipconfig /all ; ip a) Can get this info if absolutely necessary.
What is the output of "curl -k https://127.0.0.1:8006" when run directly from PVE (over SSH or physical console?) Pictures attached
What is the output of "curl -k https://LAN_IP:8006" when run directly from PVE (over SSH or physical console?) Pictures attached

PVE 8, whatever the most recent version was. Again, no updates, no reboots, nothing of significance was done to the server from my end. Was able to access yesterday, and then unable to today. I've been attempting for a few hours now just incase something was being worked on in the background, but it's the same. I've since rebooted the entire server once, and all VMs and LXCs still came back up with no issue. I'm also not seeing any major flaws with any of the commands from above, so unless I'm overlooking something, I'm just stumped. Any insight?
 

Attachments

  • curl-127-output.png
    curl-127-output.png
    145.5 KB · Views: 9
  • curl-ip-output.png
    curl-ip-output.png
    144.9 KB · Views: 8
  • ip-a-output.png
    ip-a-output.png
    125 KB · Views: 8
Hi!

You could try reinstalling pve-manager and proxmox-widget-toolkit as a first step: apt install --reinstall pve-manager proxmox-widget-toolkit. Then reload the web GUI in Firefox using Ctrl+Shift+R (Ctrl+F5 in Chrome, I think).

If that does not help, please post the output of pveversion -v. Also, have you tried a different browser?
 
mkoeppl said:
Hi!

You could try reinstalling pve-manager and proxmox-widget-toolkit as a first step: apt install --reinstall pve-manager proxmox-widget-toolkit. Then reload the web GUI in Firefox using Ctrl+Shift+R (Ctrl+F5 in Chrome, I think).

If that does not help, please post the output of pveversion -v. Also, have you tried a different browser?
Click to expand...
Will get both of those installed now. I'm mainly using chrome, but yes, I've tried different browsers, and different computers all together just to be sure.
 
Here's the output of pveversion Quick edit: The reinstall did not work.

Code: 
[root@pve network]# pveversion -v
proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-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.11-2-pve-signed: 6.14.11-2
proxmox-kernel-6.14.11-1-pve-signed: 6.14.11-1
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
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
intel-microcode: 3.20250512.1~deb12u1
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-offline-mirror-helper: 0.7.2
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
 
Onslow said:
Just to be sure: you didn't install any unofficial packages or unofficial "improvements", did you? :)
Click to expand...
Oof I'd have to say yes to that one. Proxmenu. I've had it for quite sometime with no issues though. Looking through it, it doesn't effect anything on the GUI side (that I know of)
 
I don't know this tool, so I can't comment whether it may affect the GUI.

If uninstalling it isn't very time-consuming, you could try to do it (and again reinstalling pve-manager and proxmox-widget-toolkit, just in case) and seeing whether it fixes the issue.
 
Onslow said:
I don't know this tool, so I can't comment whether it may affect the GUI.

If uninstalling it isn't very time-consuming, you could try to do it (and again reinstalling pve-manager and proxmox-widget-toolkit, just in case) and seeing whether it fixes the issue.
Click to expand...
Your words don't go unheard. I didn't uninstall the entire suite, figured I'd start small and work big. I uninstalled one "Optimization" that is supplied with it, specifically removing the subscription banner. Immediately following, Ctrl+F5 on chrome and the GUI pulled up. After getting in, I reinstalled the optimization and the GUI is still accessible. I'd like to believe that this one change didn't make the GUI inaccessible, but since that was the fix... I don't know.
 
You must log in or register to reply here.
Top Bottom