[SOLVED] /PVE/StdWorkspace.js - 500 (no such file '/PVE/StdWorkspace.js')

M

MisterDeeds

Active Member
Nov 11, 2021
155
35
33
35
Hi everyone,

I recently updated to the latest version of Proxmox VE (currently running 8.4.5), and I'm encountering several issues with the web interface after the upgrade. A reboot did not resolve the problem.

Here are the errors shown in the browser console:

1753871104241.png


The interface partially loads, but some features are broken or not responsive at all.

What I've tried so far:

  • Rebooted the node
  • Cleared browser cache
  • Tried multiple browsers
  • Verified that pve-manager and other related packages are on the latest versions

It seems like some JavaScript files are either corrupted, missing, or not being served correctly. The StdWorkspace.js file specifically returns a 500 error.

Has anyone seen this issue before or knows how to fix it? Could it be related to a botched package update or an incomplete installation?

Thanks in advance for your help!


Code: 
Uncaught SyntaxError: Unexpected token ')' (at proxmoxlib.js?ver=v4…2-t1752618798:751:2)
pvemanagerlib.js?ver=8.4.5:1502 Starting Proxmox VE Manager
pvemanagerlib.js?ver=8.4.5:2065 Uncaught TypeError: Cannot read properties of undefined (reading 'defaultText')
    at pvemanagerlib.js?ver=8.4.5:2065:40
(anonymous)    @    pvemanagerlib.js?ver=8.4.5:2065
ext-all.js?ver=7.0.0:22
 GET https://172.16.10.10:8006/PVE/StdWorkspace.js?_dc=1753870825929 500 (no such file '/PVE/StdWorkspace.js')
fetch    @    ext-all.js?ver=7.0.0:22
fetch    @    ext-all.js?ver=7.0.0:22
loadSync    @    ext-all.js?ver=7.0.0:22
load    @    ext-all.js?ver=7.0.0:22
loadEntries    @    ext-all.js?ver=7.0.0:22
processRequest    @    ext-all.js?ver=7.0.0:22
loadSync    @    ext-all.js?ver=7.0.0:22
load    @    ext-all.js?ver=7.0.0:22
loadScripts    @    ext-all.js?ver=7.0.0:22
load    @    ext-all.js?ver=7.0.0:22
require    @    ext-all.js?ver=7.0.0:22
syncRequire    @    ext-all.js?ver=7.0.0:22
(anonymous)    @    ext-all.js?ver=7.0.0:22
create    @    ext-all.js?ver=7.0.0:22
(anonymous)    @    (index):42
invoke    @    ext-all.js?ver=7.0.0:22
doInvokeAll    @    ext-all.js?ver=7.0.0:22
invokeAll    @    ext-all.js?ver=7.0.0:22
handleReady    @    ext-all.js?ver=7.0.0:22
(anonymous)    @    ext-all.js?ver=7.0.0:22
elevate    @    ext-all.js?ver=7.0.0:22
c    @    ext-all.js?ver=7.0.0:22
setTimeout      
defer    @    ext-all.js?ver=7.0.0:22
handleReadySoon    @    ext-all.js?ver=7.0.0:22
fireReady    @    ext-all.js?ver=7.0.0:22
doReadyEvent    @    ext-all.js?ver=7.0.0:22
onReadyEvent    @    ext-all.js?ver=7.0.0:22
VM110: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):42: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)
eval    @    VM110:3
create    @    ext-all.js?ver=7.0.0:22
(anonymous)    @    (index):42
invoke    @    ext-all.js?ver=7.0.0:22
doInvokeAll    @    ext-all.js?ver=7.0.0:22
invokeAll    @    ext-all.js?ver=7.0.0:22
handleReady    @    ext-all.js?ver=7.0.0:22
(anonymous)    @    ext-all.js?ver=7.0.0:22
elevate    @    ext-all.js?ver=7.0.0:22
c    @    ext-all.js?ver=7.0.0:22
setTimeout      
defer    @    ext-all.js?ver=7.0.0:22
handleReadySoon    @    ext-all.js?ver=7.0.0:22
fireReady    @    ext-all.js?ver=7.0.0:22
doReadyEvent    @    ext-all.js?ver=7.0.0:22
onReadyEvent    @    ext-all.js?ver=7.0.0:22
Code: 
pveversion -verbose
proxmox-ve: 8.4.0 (running kernel: 6.8.12-11-pve)
pve-manager: 8.4.5 (running version: 8.4.5/57892e8e686cb35b)
proxmox-kernel-helper: 8.1.4
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
proxmox-kernel-6.8.12-12-pve-signed: 6.8.12-12
proxmox-kernel-6.8.12-11-pve-signed: 6.8.12-11
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.2
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.2
libpve-cluster-perl: 8.1.2
libpve-common-perl: 8.3.2
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.6
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.3-1
proxmox-backup-file-restore: 3.4.3-1
proxmox-backup-restore-image: 0.7.0
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.4
proxmox-mail-forward: 0.3.3
proxmox-mini-journalreader: 1.5
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.12
pve-cluster: 8.1.2
pve-container: 5.3.0
pve-docs: 8.4.0
pve-edk2-firmware: 4.2025.02-4~bpo12+1
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.2
pve-firmware: 3.16-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.5
pve-qemu-kvm: 9.2.0-7
pve-xtermjs: 5.5.0-2
qemu-server: 8.4.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.8-pve1

1753873165494.png
 
Last edited:
I didn’t notice that this was already discussed in another thread — turns out it’s related to the proxmox-widget-toolkit package.

Running the following command fixed the issue for me:

Code: 
apt-get install proxmox-widget-toolkit=4.3.11

After that, the web UI loaded correctly again and the JavaScript errors disappeared.

The issue was caused by trying to hide the subscription warning using unvetted third-party hooks or patches. These unofficial modifications are fragile and tend to break, especially now that Proxmox uses auto-formatting, which makes such patches unreliable and error-prone.

The better and more stable solution is to simply leave the subscription warning enabled, as officially intended. This avoids any unexpected behavior and ensures your system remains maintainable. If you’ve used third-party scripts to disable the warning, it's best to revert those changes and follow the recommended approach.

t.lamprecht

[SOLVED] Post in thread 'Blank WebUI after Update to 8.4.5'

No, this is just fall-out from installing unvetted third party hooks/packages that try to patch out the no-subscription reminder.

Due to auto-formatting the code now most approaches fail, as they are very brittle and have no sane failure mode, and thus cause these issues, there are zero reports from setups that do not mess with this.

As it's third party stuff you should go complain to the author of these things, this is not a topic for the Proxmox community forum.
  • Like
 
Last edited:
You must log in or register to reply here.
Top Bottom