[SOLVED] Web GUI is broken since update and or restart

M

mariofehr

Member
Dec 29, 2022
6
2
8
I can visit the web GUI but there are errors in the webconsole


Code: 
proxmoxlib.js:751  Uncaught SyntaxError: Unexpected token ')'
pvemanagerlib.js?ver=9.0.5:1524 Starting Proxmox VE Manager
pvemanagerlib.js?ver=9.0.5:2087  Uncaught TypeError: Cannot read properties of undefined (reading 'defaultText')
    at pvemanagerlib.js?ver=9.0.5:2087:40
ext-all.js?ver=7.0.0:22   Failed to load resource: the server responded with a status of 500 (no such file '/PVE/StdWorkspace.js')
fetch @ ext-all.js?ver=7.0.0:22
VM40:3  Uncaught TypeError: c is not a constructor
    at eval (eval at getInstantiator (ext-all.js?ver=7.0.0:22:114222), <anonymous>:3:8)
    at Object.create (ext-all.js?ver=7.0.0:22:116004)
    at (index):45:34
    at Object.invoke (ext-all.js?ver=7.0.0:22:143801)
    at Object.doInvokeAll (ext-all.js?ver=7.0.0:22:144172)
    at Object.invokeAll (ext-all.js?ver=7.0.0:22:143917)
    at Object.handleReady (ext-all.js?ver=7.0.0:22:143490)
    at ext-all.js?ver=7.0.0:22:143632
    at Object.elevate (ext-all.js?ver=7.0.0:22:31447)
    at c (ext-all.js?ver=7.0.0:22:64430)

Would be nice if someone knows whats going on and could help me out.
 
Hi @mariofehr , welcome to the forum.

It looks like a failed upgrade. There has been more than a few similar threads over the last couple of weeks.

Here is an example thread with a number of steps that may be helpful if not in resolving the problem, then at providing more information for others to help:
A

Thread 'broke my install with PVE 9.0 upgrade attempt'

Hi- I'm sure I did something stupid but I'm messing around on a homelab that was running PVE 8.4 and I attempted to upgrade to 9.0 this morning. After rebooting, the webinterface didn't start. I ssh'd in and after doing some quick googling, I tried
Code: 
systemctl restart pvedaemon pveproxy pvestatd pvescheduler
and was greeted with the following: Screenshot 2025-08-06 at 10.06.13 AM.png
(all of the other errors are similar)

I've gone through and disabled repos associated with Debian 13 and attempted to remove Proxmox 9 apt sources and downgrade but nothing has worked so far. Any help would be much appreciated.

Cheers

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
not the same issue have. I had this issue also with the latest 8 release and hoped to fix if with installing version 9. What more infos can I provide you guys for better helping me?
 
mariofehr said:
not the same issue have.
Click to expand...
The issue is not the same, but some of the commands and troubleshooting steps are applicable.

mariofehr said:
I had this issue also with the latest 8 release and hoped to fix if with installing version 9
Click to expand...
So you had a pre-existing broken installation and hoped that an upgrade might fix it but it didn't?

Have you, by chance, used one of the community scripts that "optimizes" PVE installation?

You can try: debsums -c
You can also try "apt update -y && apt dist-upgrade -y" and post the entire output here.
You can also try: apt install --reinstall proxmox-ve pve-manager pve-cluster pve-ha-manager
Did you check that the repositories are correct?

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
  • Like
Reactions: Johannes S
Thank you very much for your help.

bbgeek17 said:
So you had a pre-existing broken installation and hoped that an upgrade might fix it but it didn't?
Click to expand...
yes silly I know but I thought maybe there is a little change that this could help.
bbgeek17 said:
Have you, by chance, used one of the community scripts that "optimizes" PVE installation?
Click to expand...
yes but on first installation from 2 years ago or so.


Code: 
root@home-lab:~# apt update -y && apt dist-upgrade -y
Get:1 http://security.debian.org/debian-security trixie-security InRelease [43.4 kB]
Hit:2 http://deb.debian.org/debian trixie InRelease
Get:3 http://deb.debian.org/debian trixie-updates InRelease [47.1 kB]
Hit:4 http://download.proxmox.com/debian/ceph-squid trixie InRelease
Get:5 http://download.proxmox.com/debian/pve trixie InRelease [2,771 B]
Hit:6 http://download.proxmox.com/debian/pve bookworm InRelease
Get:7 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 Packages [170 kB]
Fetched 264 kB in 1s (221 kB/s)
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
Upgrading:
  proxmox-firewall  proxmox-kernel-helper  pve-manager

Summary:
  Upgrading: 3, Installing: 0, Removing: 0, Not Upgrading: 0
  Download size: 1,353 kB
  Space needed: 56.3 kB / 86.9 GB available

Get:1 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 proxmox-firewall amd64 1.1.2 [755 kB]
Get:2 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 proxmox-kernel-helper all 9.0.4 [17.0 kB]
Get:3 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 pve-manager all 9.0.6 [581 kB]
Fetched 1,353 kB in 1s (1,585 kB/s)
apt-listchanges: Reading changelogs...
(Reading database ... 76356 files and directories currently installed.)
Preparing to unpack .../proxmox-firewall_1.1.2_amd64.deb ...
Unpacking proxmox-firewall (1.1.2) over (1.1.1) ...
Preparing to unpack .../proxmox-kernel-helper_9.0.4_all.deb ...
Unpacking proxmox-kernel-helper (9.0.4) over (9.0.3) ...
Preparing to unpack .../pve-manager_9.0.6_all.deb ...
Unpacking pve-manager (9.0.6) over (9.0.5) ...
Setting up pve-manager (9.0.6) ...
Setting up proxmox-kernel-helper (9.0.4) ...
Installing new version of config file /etc/kernel/postinst.d/zz-proxmox-boot ...
Installing new version of config file /etc/kernel/postrm.d/zz-proxmox-boot ...
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
Setting up proxmox-firewall (1.1.2) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for initramfs-tools (0.148.3) ...
update-initramfs: Generating /boot/initrd.img-6.14.8-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
masking the systemd-gpt-auto-generator systemd generator unit to avoid problems with the ESP and updates in certain setups.

bbgeek17 said:
You can also try: apt install --reinstall proxmox-ve pve-manager pve-cluster pve-ha-manager
Click to expand...
Thats one of the first things I tried

bbgeek17 said:
Did you check that the repositories are correct?
Click to expand...
yes looks fine I think.
 
You missed "debsums -c" request.

What does "pveversion --verbose" show?

You can also try to force reinstall all pve* and proxmox* packages in the list above.

The starting point is that there are hundreds of thousands of users for whom PVE works fine. That means something is broken in your specific environment: it could even be something as simple as a corrupted filesystem caused by a bad disk. There’s no single-click fix here. The only way forward is to methodically check one thing after another while keeping an eye on the logs.

Since your system was already in a broken state and no root cause has been identified, you might also want to consider starting fresh. Ultimately, only you can decide whether it’s worth investing more time in troubleshooting versus rebuilding.

Good luck!

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: Johannes S
Code: 
root@home-lab:~# debsums -c
/usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js


Code: 
root@home-lab:~# pveversion --verbose
proxmox-ve: 9.0.0 (running kernel: 6.14.8-2-pve)
pve-manager: 9.0.6 (running version: 9.0.6/49c767b70aeb6648)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
proxmox-kernel-6.14: 6.14.8-2
proxmox-kernel-6.14.8-2-bpo12-pve-signed: 6.14.8-2~bpo12+1
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
amd64-microcode: 3.20230808.1.1
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: not correctly installed
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.9
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 1.1.6
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.4-2
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.14-1
proxmox-backup-file-restore: 4.0.14-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.0
proxmox-widget-toolkit: 5.0.5
pve-cluster: 9.0.6
pve-container: 6.0.9
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.16-3
pve-ha-manager: 5.0.4
pve-i18n: 3.5.2
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.18
smartmontools: 7.4-pve1
spiceterm: 3.4.0
swtpm: 0.8.0+pve2
vncterm: 1.9.0
zfsutils-linux: 2.3.3-pve1
 
okay I did reinstall all PVE/Proxmox packages with this little comand
Code: 
apt update
apt install --reinstall $(dpkg -l | awk '/^ii/ && ($2 ~ /^pve/ || $2 ~ /^proxmox/){print $2}')

and now the gui works like before.

Thanks for your patience and help
 
Okay litte update after a bit more testing. I found out that my system brakes after the post script run. After a bit more digging I found out that I had some realy old comunity scripts installed I totaly forgot about. after cleaning up and a reinstall just in case everything works just fine.
 
  • Like
Reactions: Johannes S and UdoB
Thank you for sharing your findings. The "community" scripts are indeed number one cause of GUI breakage in 99% of reports.
mariofehr said:
/usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js
Click to expand...
In fact, this ^ was pretty much the guarantee that the scripts were the cause.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: Johannes S
Hi All. Thanks to everyone for the suggestions. For me, it was definitely the "/usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js" that was causing the issue. I tried a gazillion other fixes first, but in the end, it was reinstalling the Proxmox-widget-toolkit and the restarting the pveproxy service is what did it

apt install --reinstall proxmox-widget-toolkit
systemctl restart pveproxy

Hope this helps someone else!
 
  • Like
Reactions: UdoB
You must log in or register to reply here.
Top Bottom