[SOLVED] Blank WebUI after Update to 8.4.5

D

derstandard

New Member
Apr 19, 2024
9
0
1
After updating to 8.4.5 i have the issue, that the WebUI of one of my cluster maschines (was the first one which was updated) is blank after reboot)

Already taken steps:
- flushed browser cache
- used several browsers on several plattforms (Firefox, Chrome at Windows / Linux and MAC)
-reinstalled pve-manager as well as the widget-toolkit
- apt-get install --reinstall proxmox-widget-toolkit
- apt-get install --reinstall pve-manager


root@cube01:~# systemctl status pveproxy pvedaemon pve-cluster
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: active (running) since Mon 2025-07-21 20:07:04 CEST; 1min 36s ago
Process: 58962 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 58965 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 58968 (pveproxy)
Tasks: 4 (limit: 37689)
Memory: 203.1M
CPU: 2.536s
CGroup: /system.slice/pveproxy.service
├─58968 pveproxy
├─58969 "pveproxy worker"
├─58970 "pveproxy worker"
└─58971 "pveproxy worker"

Jul 21 20:07:03 cube01 systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Jul 21 20:07:04 cube01 pveproxy[58965]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
Jul 21 20:07:04 cube01 pveproxy[58968]: starting server
Jul 21 20:07:04 cube01 pveproxy[58968]: starting 3 worker(s)
Jul 21 20:07:04 cube01 pveproxy[58968]: worker 58969 started
Jul 21 20:07:04 cube01 pveproxy[58968]: worker 58970 started
Jul 21 20:07:04 cube01 pveproxy[58968]: worker 58971 started
Jul 21 20:07:04 cube01 systemd[1]: Started pveproxy.service - PVE API Proxy Server.

● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
Active: active (running) since Mon 2025-07-21 20:07:22 CEST; 1min 18s ago
Process: 59130 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 59135 (pvedaemon)
Tasks: 4 (limit: 37689)
Memory: 173.4M
CPU: 909ms
CGroup: /system.slice/pvedaemon.service
├─59135 pvedaemon
├─59136 "pvedaemon worker"
├─59137 "pvedaemon worker"
└─59138 "pvedaemon worker"

Jul 21 20:07:21 cube01 systemd[1]: Starting pvedaemon.service - PVE API Daemon...
Jul 21 20:07:22 cube01 pvedaemon[59135]: starting server
Jul 21 20:07:22 cube01 pvedaemon[59135]: starting 3 worker(s)
Jul 21 20:07:22 cube01 pvedaemon[59135]: worker 59136 started
Jul 21 20:07:22 cube01 pvedaemon[59135]: worker 59137 started
Jul 21 20:07:22 cube01 pvedaemon[59135]: worker 59138 started
Jul 21 20:07:22 cube01 systemd[1]: Started pvedaemon.service - PVE API Daemon.

● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; preset: enabled)
Active: active (running) since Mon 2025-07-21 18:36:43 CEST; 1h 31min ago
Main PID: 1555 (pmxcfs)
Tasks: 6 (limit: 37689)
Memory: 64.3M
CPU: 8.472s
CGroup: /system.slice/pve-cluster.service
└─1555 /usr/bin/pmxcfs


root@cube01:~# pveversion -v
proxmox-ve: 8.4.0 (running kernel: 6.11.11-2-pve)
pve-manager: 8.4.5 (running version: 8.4.5/57892e8e686cb35b)
proxmox-kernel-helper: 8.1.1
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.11.11-2-pve-signed: 6.11.11-2
proxmox-kernel-6.11: 6.11.11-2
proxmox-kernel-6.11.11-1-pve-signed: 6.11.11-1
proxmox-kernel-6.8.12-12-pve-signed: 6.8.12-12
proxmox-kernel-6.8: 6.8.12-12
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
amd64-microcode: 3.20230414.1
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
dnsmasq: 2.90-4~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.1
proxmox-mail-forward: 0.3.3
proxmox-mini-journalreader: 1.5
proxmox-widget-toolkit: 4.3.12
pve-cluster: 8.1.2
pve-container: 5.2.7
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-pve

Chrome-Debugger shows following:

Uncaught SyntaxError: Unexpected token ')'Understand this error
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:40Understand this error 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:22Understand this error
VM41: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)

Firefox Debugger:

Uncaught SyntaxError: missing } after property list
proxmoxlib.js:751:2note: { opened at line 42, column 29proxmoxlib.js:42:29
Starting Proxmox VE Manager pvemanagerlib.js:1502:9

Uncaught TypeError: can't access property "defaultText", Proxmox.Utils is undefined
<anonymous> https://cube01.pve.standi.cc:8006/pve2/js/pvemanagerlib.js?ver=8.4.5:2065
pvemanagerlib.js:2065:13
<anonym> https://cube01.pve.standi.cc:8006/pve2/js/pvemanagerlib.js?ver=8.4.5:2065



any help appreciated
 
derstandard said:
Chrome-Debugger shows following:

Uncaught SyntaxError: Unexpected token ')'Understand this error
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:40Understand this error 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:22Understand this error
VM41: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)
Click to expand...
This seems like something messed with your JavaScript, are you sure you did not install some customizations, like something removing the subscription reminder pop-up? In that case you'll have to complain to the author of that customization.
 
i installed a fresh PVE version in a VM, upgraded to 8.4.5 and copied the files from the VM to the non-working cluster member.
No its working ...

It seems that something prevented the override of the old 8.4.4 files (the files had different sizes and creation dates)
 
Have the same issue on 2 different machines, one on a 2-Machines-PVE-Cluster and one on a standalone machine - the cert is beeing loaded but then i recieve a blank page.
 
term.log:
Bash: 
root@pve:~# tail /var/log/apt/term.log
        Copying kernel and creating boot-entry for 6.8.12-7-pve
        Copying kernel and creating boot-entry for 6.8.8-1-pve
Processing triggers for ca-certificates (20230311+deb12u1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for shim-signed:amd64 (1.44+pmx1+15.8-1+pmx1) ...
Processing triggers for pve-ha-manager (4.0.7) ...
Log ended: 2025-07-22  09:24:27


Debugger:
JavaScript: 
Uncaught SyntaxError: missing } after property list
proxmoxlib.js:751:2note: { opened at line 42, column 29proxmoxlib.js:42:29
Starting Proxmox VE Manager pvemanagerlib.js:1502:9
Uncaught TypeError: can't access property "defaultText", Proxmox.Utils is undefined
    <anonymous> https://192.168.2.5:8006/pve2/js/pvemanagerlib.js?ver=8.4.5:2065
pvemanagerlib.js:2065:13
Synchrone XMLHttpRequests am Haupt-Thread sollte nicht mehr verwendet werden, weil es nachteilige Effekte für das Erlebnis der Endbenutzer hat. Für weitere Hilfe siehe https://xhr.spec.whatwg.org/#sync-warning ext-all.js:22:15694
Failed to get subsystem status for purpose
Object { rejected: true, message: "UNSUPPORTED_OS" }
content-script.js:104:25
XHRGET
https://192.168.2.5:8006/PVE/StdWorkspace.js?_dc=1753171881790
[HTTP/1.1 500 no such file '/PVE/StdWorkspace.js' 26ms]

XML-Verarbeitungsfehler: Syntax-Fehler
Adresse: https://192.168.2.5:8006/PVE/StdWorkspace.js?_dc=1753171881790
Zeile Nr. 1, Spalte 1: StdWorkspace.js:1:1
Uncaught TypeError: c is not a constructor
    ExtJS 2
    <anonymous> https://192.168.2.5:8006/:42
    ExtJS 15
ext-all.js:3:8
    ExtJS 2
    <anonym> https://192.168.2.5:8006/:42
    ExtJS 15
 
Ok, i read the tread one again and i think

This seems like something messed with your JavaScript, are you sure you did not install some customizations, like something removing the subscription reminder pop-up? In that case you'll have to complain to the author of that customization.
Click to expand...

i plead guilty :-) i think that will be it
 
porschecity said:
tail /var/log/apt/term.log
Click to expand...
That's the last ten lines of the upgrade output, as tail defaults to outputting just those. To check all, e.g. open it with less or grep for error and warnings, like:

Code: 
grep -C3 -Ei 'error|warn|fail' /var/log/apt/term.log

porschecity said:
Ok, i read the tread one again and i think



i plead guilty :-) i think that will be it
Click to expand...
...
 
I guess this is the same as was recently discussed in the german section. Give this and this a look.
The essential part is to get rid of the apt hook these nag removal scripts install that would overwrite the file.
In the future please don't run scripts that do things you cannot do yourself or don't know about and complain to their authors if they cause issues.
 
Last edited:
Hi everyone,

i have the same problem after upgrading to the latest version.
i used the post-install helper script to disable the subscription message some months ago.
I know, i will not do that again, but this seems to be the origin of the problem.

I did some steps that seemed to help at first, but after another reboot, the problem is back.
Right now i can't get the web UI to work at all anymore.

Bash: 
#Remove modified files and the apt hook itself
rm -f /etc/apt/apt.conf.d/no-nag-script
rm -f /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js
rm -f /usr/share/pve-manager/js/pvemanagerlib.js
#Reinstall affected packages to recreate the deleted files
apt update
apt install --reinstall pve-manager proxmox-widget-toolkit
#reboot
 
Last edited:
derstandard said:
i installed a fresh PVE version in a VM, upgraded to 8.4.5 and copied the files from the VM to the non-working cluster member.
No its working ...

It seems that something prevented the override of the old 8.4.4 files (the files had different sizes and creation dates)
Click to expand...
Can i ask which files exactly you had to overwrite?
 
Please share ls -l /etc/apt/apt.conf.d/. Also try this to check for modified system/config files
Code: 
apt install debsums
debsums -as

xbluethunderx said:
i can't get the web UI to work at all anymore.
Click to expand...
This requires elaboration.
 
Last edited:
Yeah that looks like a different issue. I see no nag removal hook and no modified webinterface file(s). Probably best to create a separate thread so we can investigate.
 
Last edited:
  • Like
Reactions: xbluethunderx
Hello Community,

i have the same problem here. After Update pve-manager 8.4.4 to 8.4.5
When I call up the WebGUI, a blank screen appears. I cant do anything.

What information can I provide to fix the problem?

Best regards, Thomas

Auswahl_149.png

/var/log/apt/term.log
Code: 
grep -C3 -Ei 'error|warn|fail' /var/log/apt/term.log
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-11-pve
Found initrd image: /boot/initrd.img-6.8.12-11-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Found linux image: /boot/vmlinuz-6.8.12-10-pve
Found initrd image: /boot/initrd.img-6.8.12-10-pve
Found linux image: /boot/vmlinuz-6.5.13-6-pve
Found initrd image: /boot/initrd.img-6.5.13-6-pve
Found linux image: /boot/vmlinuz-6.5.11-8-pve
Found initrd image: /boot/initrd.img-6.5.11-8-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Adding boot menu entry for UEFI Firmware Settings ...
done
Processing triggers for pve-ha-manager (4.0.7) ...
--
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-13-pve
Found initrd image: /boot/initrd.img-6.8.12-13-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Found linux image: /boot/vmlinuz-6.8.12-11-pve
Found initrd image: /boot/initrd.img-6.8.12-11-pve
Found linux image: /boot/vmlinuz-6.8.12-10-pve
--
Found initrd image: /boot/initrd.img-6.5.13-6-pve
Found linux image: /boot/vmlinuz-6.5.11-8-pve
Found initrd image: /boot/initrd.img-6.5.11-8-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up pve-firmware (3.16-3) ...

...

Log ended: 2025-07-18  09:50:40

Log started: 2025-07-29  09:54:46
(Reading database ... 78119 files and directories currently installed.)
Preparing to unpack .../00-libnvpair3linux_2.2.8-pve1_amd64.deb ...
Unpacking libnvpair3linux (2.2.8-pve1) over (2.2.7-pve2) ...
Preparing to unpack .../01-libproxmox-backup-qemu0_1.5.2_amd64.deb ...
Unpacking libproxmox-backup-qemu0 (1.5.2) over (1.5.1) ...
Preparing to unpack .../02-libpve-notify-perl_8.1.2_all.deb ...
Unpacking libpve-notify-perl (8.1.2) over (8.1.1) ...
Preparing to unpack .../03-libpve-cluster-api-perl_8.1.2_all.deb ...
Unpacking libpve-cluster-api-perl (8.1.2) over (8.1.1) ...
Preparing to unpack .../04-libpve-cluster-perl_8.1.2_all.deb ...
Unpacking libpve-cluster-perl (8.1.2) over (8.1.1) ...
Preparing to unpack .../05-libuutil3linux_2.2.8-pve1_amd64.deb ...
Unpacking libuutil3linux (2.2.8-pve1) over (2.2.7-pve2) ...
Preparing to unpack .../06-libzfs4linux_2.2.8-pve1_amd64.deb ...
Unpacking libzfs4linux (2.2.8-pve1) over (2.2.7-pve2) ...
Preparing to unpack .../07-libzpool5linux_2.2.8-pve1_amd64.deb ...
Unpacking libzpool5linux (2.2.8-pve1) over (2.2.7-pve2) ...
Preparing to unpack .../08-proxmox-backup-client_3.4.3-1_amd64.deb ...
Unpacking proxmox-backup-client (3.4.3-1) over (3.4.2-1) ...
Preparing to unpack .../09-proxmox-backup-file-restore_3.4.3-1_amd64.deb ...
Unpacking proxmox-backup-file-restore (3.4.3-1) over (3.4.2-1) ...
Preparing to unpack .../10-pve-firmware_3.16-3_all.deb ...
Unpacking pve-firmware (3.16-3) over (3.15-4) ...
Selecting previously unselected package proxmox-kernel-6.8.12-13-pve-signed.
Preparing to unpack .../11-proxmox-kernel-6.8.12-13-pve-signed_6.8.12-13_amd64.deb ...
Unpacking proxmox-kernel-6.8.12-13-pve-signed (6.8.12-13) ...
Preparing to unpack .../12-proxmox-kernel-6.8_6.8.12-13_all.deb ...
Unpacking proxmox-kernel-6.8 (6.8.12-13) over (6.8.12-11) ...
Preparing to unpack .../13-proxmox-kernel-helper_8.1.4_all.deb ...
Unpacking proxmox-kernel-helper (8.1.4) over (8.1.1) ...
Preparing to unpack .../14-proxmox-widget-toolkit_4.3.12_all.deb ...
Unpacking proxmox-widget-toolkit (4.3.12) over (4.3.11) ...
Preparing to unpack .../15-pve-cluster_8.1.2_amd64.deb ...
Unpacking pve-cluster (8.1.2) over (8.1.1) ...
Preparing to unpack .../16-pve-container_5.3.0_all.deb ...
Unpacking pve-container (5.3.0) over (5.2.7) ...
Preparing to unpack .../17-pve-edk2-firmware-ovmf_4.2025.02-4~bpo12+1_all.deb ...
Unpacking pve-edk2-firmware-ovmf (4.2025.02-4~bpo12+1) over (4.2025.02-3) ...
Preparing to unpack .../18-pve-edk2-firmware-legacy_4.2025.02-4~bpo12+1_all.deb ...
Unpacking pve-edk2-firmware-legacy (4.2025.02-4~bpo12+1) over (4.2025.02-3) ...
Preparing to unpack .../19-pve-edk2-firmware_4.2025.02-4~bpo12+1_all.deb ...
Unpacking pve-edk2-firmware (4.2025.02-4~bpo12+1) over (4.2025.02-3) ...
Preparing to unpack .../20-pve-manager_8.4.5_all.deb ...
Unpacking pve-manager (8.4.5) over (8.4.1) ...
Preparing to unpack .../21-pve-qemu-kvm_9.2.0-7_amd64.deb ...
Unpacking pve-qemu-kvm (9.2.0-7) over (9.2.0-6) ...
Preparing to unpack .../22-spl_2.2.8-pve1_all.deb ...
Unpacking spl (2.2.8-pve1) over (2.2.7-pve2) ...
Preparing to unpack .../23-zfs-initramfs_2.2.8-pve1_all.deb ...
Unpacking zfs-initramfs (2.2.8-pve1) over (2.2.7-pve2) ...
Preparing to unpack .../24-zfsutils-linux_2.2.8-pve1_amd64.deb ...
Unpacking zfsutils-linux (2.2.8-pve1) over (2.2.7-pve2) ...
Preparing to unpack .../25-zfs-zed_2.2.8-pve1_amd64.deb ...
Unpacking zfs-zed (2.2.8-pve1) over (2.2.7-pve2) ...
Setting up proxmox-backup-file-restore (3.4.3-1) ...
Updating file-restore initramfs...
14327 blocks
Setting up libnvpair3linux (2.2.8-pve1) ...
Setting up proxmox-widget-toolkit (4.3.12) ...
Setting up proxmox-kernel-6.8.12-13-pve-signed (6.8.12-13) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.8.12-13-pve /boot/vmlinuz-6.8.12-13-pve
update-initramfs: Generating /boot/initrd.img-6.8.12-13-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/F227-8F14
        Copying kernel and creating boot-entry for 6.5.13-6-pve
        Copying kernel and creating boot-entry for 6.8.12-11-pve
        Copying kernel and creating boot-entry for 6.8.12-13-pve
        Removing old version 6.8.12-10-pve
Copying and configuring kernels on /dev/disk/by-uuid/F227-E17D
        Copying kernel and creating boot-entry for 6.5.13-6-pve
        Copying kernel and creating boot-entry for 6.8.12-11-pve
        Copying kernel and creating boot-entry for 6.8.12-13-pve
        Removing old version 6.8.12-10-pve
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.8.12-13-pve /boot/vmlinuz-6.8.12-13-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.8.12-13-pve /boot/vmlinuz-6.8.12-13-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/F227-8F14
        Copying kernel and creating boot-entry for 6.5.13-6-pve
        Copying kernel and creating boot-entry for 6.8.12-11-pve
        Copying kernel and creating boot-entry for 6.8.12-13-pve
Copying and configuring kernels on /dev/disk/by-uuid/F227-E17D
        Copying kernel and creating boot-entry for 6.5.13-6-pve
        Copying kernel and creating boot-entry for 6.8.12-11-pve
        Copying kernel and creating boot-entry for 6.8.12-13-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.8.12-13-pve /boot/vmlinuz-6.8.12-13-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-13-pve
Found initrd image: /boot/initrd.img-6.8.12-13-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Found linux image: /boot/vmlinuz-6.8.12-11-pve
Found initrd image: /boot/initrd.img-6.8.12-11-pve
Found linux image: /boot/vmlinuz-6.8.12-10-pve
Found initrd image: /boot/initrd.img-6.8.12-10-pve
Found linux image: /boot/vmlinuz-6.5.13-6-pve
Found initrd image: /boot/initrd.img-6.5.13-6-pve
Found linux image: /boot/vmlinuz-6.5.11-8-pve
Found initrd image: /boot/initrd.img-6.5.11-8-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up pve-firmware (3.16-3) ...
Setting up pve-edk2-firmware-ovmf (4.2025.02-4~bpo12+1) ...
Setting up pve-cluster (8.1.2) ...
Setting up proxmox-kernel-helper (8.1.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..
UUID="F227-8F14" SIZE="1073741824" FSTYPE="vfat" PARTTYPE="c12a7328-f81f-11d2-ba4b-00a0c93ec93b" PKNAME="nvme0n1" MOUNTPOINT=""
Mounting '/dev/disk/by-uuid/F227-8F14' on '/var/tmp/espmounts/F227-8F14'.
Installing systemd-boot..
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/F227-8F14/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/F227-8F14/EFI/BOOT/BOOTX64.EFI".
Random seed file /var/tmp/espmounts/F227-8F14/loader/random-seed successfully written (32 bytes).
Created EFI boot entry "Linux Boot Manager".
Configuring systemd-boot..
Unmounting '/dev/disk/by-uuid/F227-8F14'.
Adding '/dev/disk/by-uuid/F227-8F14' to list of synced ESPs..
UUID="F227-E17D" SIZE="1073741824" FSTYPE="vfat" PARTTYPE="c12a7328-f81f-11d2-ba4b-00a0c93ec93b" PKNAME="nvme1n1" MOUNTPOINT=""
Mounting '/dev/disk/by-uuid/F227-E17D' on '/var/tmp/espmounts/F227-E17D'.
Installing systemd-boot..
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/F227-E17D/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/F227-E17D/EFI/BOOT/BOOTX64.EFI".
Random seed file /var/tmp/espmounts/F227-E17D/loader/random-seed successfully written (32 bytes).
Created EFI boot entry "Linux Boot Manager".
Configuring systemd-boot..
Unmounting '/dev/disk/by-uuid/F227-E17D'.
Adding '/dev/disk/by-uuid/F227-E17D' to list of synced ESPs..
Setting up proxmox-backup-client (3.4.3-1) ...
Setting up spl (2.2.8-pve1) ...
Setting up pve-edk2-firmware-legacy (4.2025.02-4~bpo12+1) ...
Setting up libpve-cluster-perl (8.1.2) ...
Setting up libuutil3linux (2.2.8-pve1) ...
Setting up pve-edk2-firmware (4.2025.02-4~bpo12+1) ...
Setting up proxmox-kernel-6.8 (6.8.12-13) ...
Setting up libproxmox-backup-qemu0 (1.5.2) ...
Setting up libzpool5linux (2.2.8-pve1) ...
Setting up libpve-cluster-api-perl (8.1.2) ...
Setting up libpve-notify-perl (8.1.2) ...
Setting up pve-container (5.3.0) ...
Setting up pve-qemu-kvm (9.2.0-7) ...
Setting up pve-manager (8.4.5) ...
Setting up libzfs4linux (2.2.8-pve1) ...
Setting up zfsutils-linux (2.2.8-pve1) ...
Setting up zfs-initramfs (2.2.8-pve1) ...
Setting up zfs-zed (2.2.8-pve1) ...
Processing triggers for pve-ha-manager (4.0.7) ...
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.8.12-13-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/F227-8F14
        Copying kernel and creating boot-entry for 6.5.13-6-pve
        Copying kernel and creating boot-entry for 6.8.12-11-pve
        Copying kernel and creating boot-entry for 6.8.12-13-pve
Copying and configuring kernels on /dev/disk/by-uuid/F227-E17D
        Copying kernel and creating boot-entry for 6.5.13-6-pve
        Copying kernel and creating boot-entry for 6.8.12-11-pve
        Copying kernel and creating boot-entry for 6.8.12-13-pve
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.36-9+deb12u10) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for mailcap (3.70+nmu1) ...
Log ended: 2025-07-29  09:56:39

Code: 
pveversion -v
proxmox-ve: 8.4.0 (running kernel: 6.8.12-13-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-11-pve-signed: 6.8.12-11
proxmox-kernel-6.8.12-10-pve-signed: 6.8.12-10
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
ceph-fuse: 17.2.7-pve2
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
 
Last edited:
Some behaviour with blank screen for me after update on three proxmox installation. Solution for me was
Code: 
apt-get install proxmox-widget-toolkit=4.3.11
It seems that in version 4.3.12 of the promox-widget-toolkit a class is missing.
 
  • Like
Reactions: MisterDeeds
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.
 
Last edited:
  • Like
Reactions: bestho, MisterDeeds and janus57
You must log in or register to reply here.
Top Bottom