Proxmox 7.0-9 Web UI unable to launch GUI Windows

Anguskon

New Member
Jun 13, 2020
3
1
3
33
Hello,

I have just upgraded to proxmox 7 (from 6.4.3) and my WUI (Web UI) is not functioning properly. I can console without issue, view logs without issue. However whenever I try to Create a new VM, container, or edit VM properties it doesn't work. It launches what looks like a minimized window but freezes the Web UI and I have to refresh the page to get any control back.

I have tried accessing the WUI multiple ways, all of them have the same exact issue.
  • Windows 10
    • Chrome and Edgium
    • Internet Explorer (ya I know)
    • Firefox
  • Mac OS
    • Safari
    • Chrome
I've also rebooted the server and restarted the pveproxy service.

Here is what it looks like whenever I try to Create a VM, container, or edit properties of a device. However the logs window launches without issue.
1626325376674.png1626325376674.png
 
Hi,

could you please post your package versions pveversion -v and maybe check in the developer console (F12) if any errors are displayed during the not working interactions?
 
Hi,

i experienced something similar to what the OP said after upgrading from 6.4 to 7.0. In my case it happens only when trying to add a new Metric Server. Most other windows/menues (didn´t test all so far) show up fine. It only happens in Chromium-based browsers (Chrome/Edge) but not in Firefox. Hope that helps shedding some more light on the problem / solution.

Output of developer console:

ext-all.js:22 Uncaught TypeError: Cannot read property 'scope' of undefined
at F.addListener (ext-all.js:22)
at F.e.<computed> [as on] (ext-all.js:22)
at g.onRender (proxmoxlib.js?ver=3.3-4:1743)
at g.finishRender (ext-all.js:22)
at F.finishRenderItems (ext-all.js:22)
at F.finishRender (ext-all.js:22)
at F.finishRenderChildren (ext-all.js:22)
at F.afterRender (ext-all.js:22)
at F.finishRender (ext-all.js:22)
at F.finishRenderItems (ext-all.js:22)


# pveversion -v

proxmox-ve: 7.0-2 (running kernel: 5.11.22-2-pve)
pve-manager: 7.0-9 (running version: 7.0-9/228c9caa)
pve-kernel-5.11: 7.0-5
pve-kernel-helper: 7.0-5
pve-kernel-5.4: 6.4-4
pve-kernel-5.3: 6.1-6
pve-kernel-5.11.22-2-pve: 5.11.22-3
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.119-1-pve: 5.4.119-1
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.103-1-pve: 5.4.103-1
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 14.2.21-1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.0.0-1+pve6
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-5
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-9
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
openvswitch-switch: 2.15.0+ds1-2
proxmox-backup-client: 2.0.4-1
proxmox-backup-file-restore: 2.0.4-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-4
pve-cluster: 7.0-3
pve-container: 4.0-8
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-10
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1


Proxmox_70_Window.jpg
 
I have not been able to reproduce the problem so far. Could you please try
Code:
apt update
apt install --reinstall pve-manager proxmox-widget-toolkit
and hard refresh the browser?

@Nefariousparity @Anguskon What exact versions of pve-manager and proxmox-widget-toolkit do you have installed?
 
apt update apt install --reinstall pve-manager proxmox-widget-toolkit
Worked like a charm. Now all glitches are gone. :)

I did hard reset of the browser before so reinstalling the packages you mentioned did the trick.
Thanks Dominic. Keep up the good work.
 
  • Like
Reactions: Dominic
I had the same problem.
Had to write a lot of css in to insider just to be able to clone one vm.
Then i found this answer and tried to reinstall just the proxmox-widget-toolkit and its working perfect without any errors
 
Code:
apt update
apt install --reinstall pve-manager proxmox-widget-toolkit
Hello,

unfortunately I still get the incorrect display as seen in the screenshots of Katharsis.

Are there any other possible causes?
I have upgraded from 6.4-13 to 7.0-11.

Dev Console
Code:
Uncaught TypeError: Cannot read property 'scope' of undefined
    at F.addListener (ext-all.js:22)
    at F.e.<computed> [as on] (ext-all.js:22)
    at g.onRender (proxmoxlib.js?ver=3.3-6:1743)
    at g.finishRender (ext-all.js:22)
    at F.finishRenderItems (ext-all.js:22)
    at F.finishRender (ext-all.js:22)
    at F.finishRenderChildren (ext-all.js:22)
    at F.afterRender (ext-all.js:22)
    at F.finishRender (ext-all.js:22)
    at F.finishRenderItems (ext-all.js:22)

#pveversion -v
Code:
proxmox-ve: 7.0-2 (running kernel: 5.4.34-1-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-6
pve-kernel-helper: 7.0-6
pve-kernel-5.4: 6.4-5
pve-kernel-5.11.22-3-pve: 5.11.22-6
pve-kernel-5.4.128-1-pve: 5.4.128-1
pve-kernel-5.4.124-1-pve: 5.4.124-2
pve-kernel-5.4.119-1-pve: 5.4.119-1
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.103-1-pve: 5.4.103-1
pve-kernel-5.4.101-1-pve: 5.4.101-1
pve-kernel-5.4.98-1-pve: 5.4.98-1
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-5.4.60-1-pve: 5.4.60-2
pve-kernel-5.4.55-1-pve: 5.4.55-1
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.44-1-pve: 5.4.44-1
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 14.2.22-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.2.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-5
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-10
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.8-1
proxmox-backup-file-restore: 2.0.8-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-13
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1
 

Attachments

  • Screenshot 2021-08-24 155437.jpg
    Screenshot 2021-08-24 155437.jpg
    106.3 KB · Views: 24
Last edited:

About

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!