[SOLVED] Fresh PVE install: Web UI unreachable after reboot (pveproxy SSL key error)

[TheBigZamora]

Hi all,
I’ve just completed a fresh Proxmox VE setup on a new mini-PC. After the first reboot I can only get in via SSH; the WebGUI doesn’t load at all.
When I check the proxy logs with:

 "journalctl -b -u pveproxy"

I repeatedly see lines like:

 "pveproxy[]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 200
pveproxy[]: worker #### finished
pveproxy[]: starting 1 worker(s)
pveproxy[]: worker #### started"

I also tried refreshing the certs:

 "pvecm updatecerts --force"

but I get:

 "ipcc_send_rec[1..3] failed: Connection refused
Unable to load access control list: Connection refused"

Network looks fine (I can ping external hosts and internal IPs). Any ideas what I’m missing?
Thanks in advance!

 

[pcarone]

It looks like your cluster filesystem wasn’t available (pmxcfs stuck behind a stale lock), which breaks pve-cluster and, as a result, certificate handling for pveproxy. Restarting the cluster service after clearing the lock fixes it.
Run these in order:

 "systemctl stop pve-cluster
rm -f /var/lib/pve-cluster/.pmxcfs.lockfile
systemctl start pve-cluster"

After pve-cluster is up again, pveproxy should load its certs and the WebGUI should respond normally. If you still see SSL key errors, recheck the status:

 "systemctl status pve-cluster pveproxy"

but in most cases the three commands above resolve it.

 

[TheBigZamora]

Got it working, thank you very much!