[Solved] PVE Web interface not working

J

javito1081

Member
Jan 4, 2024
42
8
8
Hi,

I have PBS installed on my PVE server, after updating the repositories with the no subscription one to update my PBS, all hell broke loose on my server, iv been trying to google for possible fixes but havent found any so far, hope i can get some help here to get my pve web interface back to normal.

So after updating my PBS, for some reason both my pve and my pbs interfaces stopped working, i was able to enter the interface but i was getting a blank page, trying to login from a dif browser showed me the certificate warning, but after that no login webpage.

Tried to restart pveproxy.service pvedaemon.service and they were all working fine, but after trying to reinstall proxmox-widget-toolkit now none of them want to start, getting this from the journal

root@JavitoVE:~# systemctl status pvedaemon.service
× pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sun 2025-08-10 10:53:23 CST; 14s ago
Duration: 20min 5.700s
Process: 227738 ExecStart=/usr/bin/pvedaemon start (code=exited, status=17)
CPU: 448ms

Aug 10 10:53:24 JavitoVE systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
Aug 10 10:53:25 JavitoVE systemd[1]: pvedaemon.service: Start request repeated too quickly.
Aug 10 10:53:25 JavitoVE systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Aug 10 10:53:25 JavitoVE systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
Aug 10 10:53:26 JavitoVE systemd[1]: pvedaemon.service: Start request repeated too quickly.
Aug 10 10:53:26 JavitoVE systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Aug 10 10:53:26 JavitoVE systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
Aug 10 10:53:27 JavitoVE systemd[1]: pvedaemon.service: Start request repeated too quickly.
Aug 10 10:53:27 JavitoVE systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Aug 10 10:53:27 JavitoVE systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
Click to expand...

i also tried to reinstall proxmox ve and all i get is this

root@JavitoVE:~# apt install --reinstall proxmox-ve
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 5,244 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-ve all 8.4.0 [5,244 B]
Fetched 5,244 B in 0s (20.8 kB/s)
(Reading database ... 78764 files and directories currently installed.)
Preparing to unpack .../proxmox-ve_8.4.0_all.deb ...
Unpacking proxmox-ve (8.4.0) over (8.4.0) ...
Setting up proxmox-ve (8.4.0) ...
Click to expand...

saw a lot of posts asking users to post theyr cat /var/log/syslog but i dont have that directory

root@JavitoVE:~# cat /var/log/syslog
cat: /var/log/syslog: No such file or directory
Click to expand...

So other than just format and do a fresh install of my pve server, i have no clue what else i can do to make it work again, so please any help would be apreciated.

Also i forgot to mention that my vms and lxc's are still working, cause i have access to all of them, but i cant access the interface and if i try to do pct list or pct enter 101 for example over ssh i get

root@JavitoVE:~# pct enter 101
Attempt to reload PVE/HA/Config.pm aborted.
Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 20.
Compilation failed in require at /usr/share/perl5/PVE/API2/LXC/Status.pm line 24.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/LXC/Status.pm line 29.
Compilation failed in require at /usr/share/perl5/PVE/CLI/pct.pm line 24.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/pct.pm line 24.
Compilation failed in require at /usr/sbin/pct line 6.
BEGIN failed--compilation aborted at /usr/sbin/pct line 6.
Click to expand...

Btw my PBS interface is still showing a blank page on the login screen even tho my PVE one is now refusing to connect
 
Last edited:
Hi!

Assuming that JavitoVE is the Proxmox VE host, could you post the output of pveversion -v on that host?
 
please also provide "apt policy", thanks!
 
dakralex said:
Hi!

Assuming that JavitoVE is the Proxmox VE host, could you post the output of pveversion -v on that host?
Click to expand...
Sure, here it is

root@JavitoVE:~# pveversion -v
proxmox-ve: 8.4.0 (running kernel: 6.14.8-2-pve)
pve-manager: 8.4.9 (running version: 8.4.9/649acf70aab54798)
proxmox-kernel-helper: 9.0.3
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
proxmox-kernel-6.14: 6.14.8-2
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-9-pve-signed: 6.8.12-9
ceph-fuse: 17.2.8-pve2
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
frr-pythontools: 10.2.3-1+pve1
glusterfs-client: 10.3-5
ifupdown2: 3.3.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 1.5.2
libproxmox-rs-perl: 0.3.5
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.9
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 9.0.13
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-3
proxmox-backup-client: 3.4.4-1
proxmox-backup-file-restore: 3.4.3-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 9.0.3
proxmox-mail-forward: 0.3.3
proxmox-mini-journalreader: 1.5
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 5.0.5
pve-cluster: 8.1.2
pve-container: 5.3.0
pve-docs: 9.0.8
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.2
pve-firmware: 3.16-3
pve-ha-manager: 5.0.4
pve-i18n: 3.5.2
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
Click to expand...
 
fabian said:
please also provide "apt policy", thanks!
Click to expand...
Here

root@JavitoVE:~# apt policy
\Package files:
100 /var/lib/dpkg/status
release a=now
500 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 Packages
release o=Proxmox,a=stable,n=bookworm,l=Proxmox Debian Repository,c=pve-no-subscription,b=amd64
origin download.proxmox.com
500 http://security.debian.org/debian-security bookworm-security/contrib amd64 Packages
release v=12,o=Debian,a=oldstable-security,n=bookworm-security,l=Debian-Security,c=contrib,b=amd64
origin security.debian.org
500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
release v=12,o=Debian,a=oldstable-security,n=bookworm-security,l=Debian-Security,c=main,b=amd64
origin security.debian.org
500 http://deb.debian.org/debian bookworm-updates/main amd64 Packages
release v=12-updates,o=Debian,a=oldstable-updates,n=bookworm-updates,l=Debian,c=main,b=amd64
origin deb.debian.org
500 http://deb.debian.org/debian bookworm/contrib amd64 Packages
release v=12.11,o=Debian,a=oldstable,n=bookworm,l=Debian,c=contrib,b=amd64
origin deb.debian.org
500 http://deb.debian.org/debian bookworm/main amd64 Packages
release v=12.11,o=Debian,a=oldstable,n=bookworm,l=Debian,c=main,b=amd64
origin deb.debian.org
Pinned packages:
shim-signed -> 1.44+pmx1+15.8-1+pmx1 with priority 900
shim-signed -> 1.42+pmx1+15.8-1+pmx1 with priority 900
shim-signed -> 1.40+pmx1+15.8-1+pmx1 with priority 900
shim-signed -> 1.39+pmx1+15.7-1+pmx1 with priority 900
Click to expand...
 
I made the mistake to restart my server and now nothing boots up, i still have access over ssh, but nothing else :-(

Anyway this is what i get when i do journalctl -xeu pvedaemon.service

root@JavitoVE:~# systemctl restart pveproxy.service pvedaemon.service
Job for pvedaemon.service failed because the control process exited with error code.
See "systemctl status pvedaemon.service" and "journalctl -xeu pvedaemon.service" for details.
Job for pveproxy.service failed because the control process exited with error code.
See "systemctl status pveproxy.service" and "journalctl -xeu pveproxy.service" for details.
root@JavitoVE:~# journalctl -xeu pvedaemon.service
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvedaemon.service has entered the 'failed' state with result 'exit-code'.
Aug 11 07:25:47 JavitoVE systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
░░ Subject: A start job for unit pvedaemon.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvedaemon.service has finished with a failure.
░░
░░ The job identifier is 11788 and the job result is failed.
Aug 11 07:25:48 JavitoVE systemd[1]: pvedaemon.service: Start request repeated too quickly.
Aug 11 07:25:48 JavitoVE systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvedaemon.service has entered the 'failed' state with result 'exit-code'.
Aug 11 07:25:48 JavitoVE systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
░░ Subject: A start job for unit pvedaemon.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvedaemon.service has finished with a failure.
░░
░░ The job identifier is 11927 and the job result is failed.
Aug 11 07:25:49 JavitoVE systemd[1]: pvedaemon.service: Start request repeated too quickly.
Aug 11 07:25:49 JavitoVE systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvedaemon.service has entered the 'failed' state with result 'exit-code'.
Aug 11 07:25:49 JavitoVE systemd[1]: Failed to start pvedaemon.service - PVE API Daemon.
░░ Subject: A start job for unit pvedaemon.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvedaemon.service has finished with a failure.
░░
░░ The job identifier is 12066 and the job result is failed.
lines 1168-1210/1210 (END)
Click to expand...
 
please post the full output of "apt update" and "journalctl -b -u pvedaemon -u pveproxy"
 
fabian said:
please post the full output of "apt update" and "journalctl -b -u pvedaemon -u pveproxy"
Click to expand...
Here it is

root@JavitoVE:~# apt update && apt upgrade -y
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Click to expand...
 
okay, what if you do

"systemctl stop pveproxy pvedaemon; systemctl reset-failed pveproxy pvedaemon; systemctl start pveproxy pvedaemon"

?
 
fabian said:
okay, what if you do

"systemctl stop pveproxy pvedaemon; systemctl reset-failed pveproxy pvedaemon; systemctl start pveproxy pvedaemon"

?
Click to expand...
I think i found the culprit of my issues, since i updated proxmox backup server with the trixie repositories, aparently something broke, i wasnt aware there was a major release of proxmox ve and backup in the recent days, i just found out hehe, right now im following the procedure to upgrade from 8 to 9 and see if that helps, ill post my updates, if not ill run ur comands and post the results, but if yesterday when i ran those, i was getting exit code 17 annd both services were unable to start :-(
 
fabian said:
okay, what if you do

"systemctl stop pveproxy pvedaemon; systemctl reset-failed pveproxy pvedaemon; systemctl start pveproxy pvedaemon"

?
Click to expand...
Ok so heres an update, after upgrading everything to the newest versions proxmox ve to 9.0.4 and proxmox backup server to 4.0.12, everything started to work like a charm, but after every upgrade, im use to just reboot my system, now it doesnt wants to boot, all i get is a black screen, i can enter bios and all that just fine, but after that i get nothing, i use to get the blue boot proxmox screen, but now im getting nothing at all :-( i guess something broke with the boot system after the upgrade? what can i do now?

Edit: I disable Secure Boot and everything is back to work :-)

Guess ill pay more attention from now on b4 runing any updates to see if theres any major release so this doesnt happen again, thanks all for ur help :-)
 
Last edited:
You must log in or register to reply here.
Top Bottom