Blank Web admin page

[François Vivet]

Hi, I installed a proxmox server 1 month ago and everything looked fine until yesterday when I rebooted it. Since that time, the web admin interface is blank. I made an upgrade using apt-get dist-upgrade this morning for the same result (I did not restart the proxmox server after the upgrade as this server is a single one and VM running on it are in production ...).
If someone have a suggestion, do not hesitate.

Here is the result of pveversion -v :

proxmox-ve: 7.2-1 (running kernel: 5.15.39-4-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-helper: 7.2-12
pve-kernel-5.15: 7.2-11
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.39-4-pve: 5.15.39-4
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.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.6-1
proxmox-backup-file-restore: 2.2.6-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-3
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1

 

[mira]

Which browser do you use and which version of it?

 

[François Vivet]

Hi, I tried different web browsers (Firefox 105.0.1 , Opera 91.0.4516.20 and Microsoft Edge) on different OS (Ubuntu and Windows10). The trick is that I have 2 other Proxmox servers which are in the same version and it works fine for them. The diference is only the constructors (DELL and HP).
I don't have for now a commercial Support Subscription but I'm thinking about it: I'm trying Proxmox with the aim to change all our Xen servers for Proxmox.

 

[mira]

Do you get the same blank page if you open the PVE GUI in a new private session without any extensions?

Can you provide the output of systemctl status pvedaemon.service and systemctl status pveproxy.service?

 

[François Vivet]

Thanks for your help. I already tried in a private session and it changed nothing. Here are the outputs asked:

Command systemctl status pvedaemon.service

● pvedaemon.service - PVE API Daemon
     Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-10-03 11:26:56 CEST; 1 day 3h ago
    Process: 361878 ExecReload=/usr/bin/pvedaemon restart (code=exited, status=0/SUCCESS)
   Main PID: 1803 (pvedaemon)
      Tasks: 4 (limit: 154204)
     Memory: 142.6M
        CPU: 16.557s
     CGroup: /system.slice/pvedaemon.service
             ├─  1803 pvedaemon
             ├─361890 pvedaemon worker
             ├─361891 pvedaemon worker
             └─361892 pvedaemon worker

Oct 04 10:55:50 proxmix2 pvedaemon[1803]: starting 3 worker(s)
Oct 04 10:55:50 proxmix2 pvedaemon[1803]: worker 361890 started
Oct 04 10:55:50 proxmix2 pvedaemon[1803]: worker 361891 started
Oct 04 10:55:50 proxmix2 pvedaemon[1803]: worker 361892 started
Oct 04 10:55:55 proxmix2 pvedaemon[1805]: worker exit
Oct 04 10:55:55 proxmix2 pvedaemon[1806]: worker exit
Oct 04 10:55:55 proxmix2 pvedaemon[1804]: worker exit
Oct 04 10:55:55 proxmix2 pvedaemon[1803]: worker 1806 finished
Oct 04 10:55:55 proxmix2 pvedaemon[1803]: worker 1804 finished
Oct 04 10:55:55 proxmix2 pvedaemon[1803]: worker 1805 finished

Command systemctl status pveproxy.service

● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-10-03 11:26:58 CEST; 1 day 3h ago
    Process: 361888 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
   Main PID: 1812 (pveproxy)
      Tasks: 4 (limit: 154204)
     Memory: 235.3M
        CPU: 25.376s
     CGroup: /system.slice/pveproxy.service
             ├─  1812 pveproxy
             ├─361920 pveproxy worker
             ├─361921 pveproxy worker
             └─361922 pveproxy worker

Oct 04 10:55:50 proxmix2 pveproxy[1812]: starting 3 worker(s)
Oct 04 10:55:50 proxmix2 pveproxy[1812]: worker 361920 started
Oct 04 10:55:50 proxmix2 pveproxy[1812]: worker 361921 started
Oct 04 10:55:50 proxmix2 pveproxy[1812]: worker 361922 started
Oct 04 10:55:55 proxmix2 pveproxy[189337]: worker exit
Oct 04 10:55:55 proxmix2 pveproxy[189338]: worker exit
Oct 04 10:55:55 proxmix2 pveproxy[189339]: worker exit
Oct 04 10:55:55 proxmix2 pveproxy[1812]: worker 189337 finished
Oct 04 10:55:55 proxmix2 pveproxy[1812]: worker 189339 finished
Oct 04 10:55:55 proxmix2 pveproxy[1812]: worker 189338 finished

 

[mira]

Those look good. And the update ran without any errors?
What do you get when you run `apt update` and `apt -f install`?


Do you see anything when you load the GUI with the debug console (F12) active?

 

[François Vivet]

I get normal message as far as I guess:

apt update
Hit:1 http://ftp.fr.debian.org/debian bullseye InRelease
Get:2 http://ftp.fr.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:3 http://security.debian.org bullseye-security InRelease                   
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease
Fetched 44.1 kB in 0s (113 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

apt -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.