[SOLVED] Broken WebUI after upgrading pve-container


New Member
Oct 7, 2023
Hello everyone,

after doing some miscellaneous work we were upgrading systemd via WebUI and pve-container via console (both only on node1 of a two nodes setup), we are now using the following setup (node1):

proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve)
pve-manager: 7.4-17 (running version: 7.4-17/513c62be)
pve-kernel-helper: 7.2-2
pve-kernel-5.15: 7.2-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.1-1
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.4.3-1
proxmox-backup-file-restore: 2.4.3-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.2-1
pve-container: 4.4-6
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-1
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

After upgrading pve-container, our WebUI stopped working properly. Instead, after logging in on the WebUI successfully, we receive the following error message:
Error Undefined subroutine &PVE::Cluster::get_guest_config_properties called at /usr/share/perl5/PVE/GuestHelpers.pm line 284.
This has the effect that we cannot view the WebUI's server list anymore. We only can see our clustername.

/usr/share/perl5/PVE/GuestHelpers.pm lines 283ff:
    if ($user_allow eq 'free' || $user_allow eq 'existing' || $privileged_user) {
        my $props = PVE::Cluster::get_guest_config_properties(['tags']);
        for my $vmid (keys $props->%*) {
            next if !$privileged_user && !$rpcenv->check_vm_perm($user, $vmid, undef, ['VM.Audit'], 0, 1);
            $allowed_tags->{$_} = 1 for split_list($props->{$vmid}->{tags});

So we upgraded pve-container on node2 as well but the problem still remains.

We installed the newer versions systemd and pve-container because we had a problem with restarting a freshly setup debian12 LXC for the first time and we followed the advice of a supporter here in the forums where this (upgrading pve-container, https://forum.proxmox.com/threads/failed-to-run-lxc-hook-pre-start.33260/post-511870) was edited as the long-term solution.

Debian12 container config:
arch: amd64
cores: 2
features: nesting=1
hostname: mc04
memory: 2048
net0: name=eth0,bridge=vmbr3,firewall=1,gw=,hwaddr=FE:32:4C:CE:59:EA,ip=,type=veth
ostype: debian
rootfs: local-lvm:vm-108-disk-0,size=30G
swap: 512
unprivileged: 1

Please help and let me know if you need further information.

Thannks in advance!
Last edited:


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!