Proxmox Cannot Access Web GUI: Fix It Fast

Proxmox cannot access web GUI? It’s usually the pveproxy service, a firewall rule, or a full disk. Here’s the checklist that fixes it fast.

Check pveproxy first

The web GUI runs through pveproxy. If it’s dead, you get nothing. SSH into the host and run:

systemctl status pveproxy

If it’s not active, start it:

systemctl start pveproxy

And if it fails, check the logs:

journalctl -u pveproxy -f

Common error: pveproxy[1234]: /etc/pve/local/pve-ssl.pem: failed to load local private key. That means your SSL cert is broken. You can regenerate it with pvecm updatecerts -f.

Firewall and port 8006

The GUI listens on port 8006. If you have a firewall on the host or in front of it, make sure TCP 8006 is open. On the host, check iptables:

iptables -L -n | grep 8006

If you see a DROP rule, flush it or add an ACCEPT. Also check if you have a pve-firewall enabled on the datacenter or node level. Disable it temporarily to test:

pve-firewall stop

If the GUI comes back, you know it’s the firewall. Then re-enable and fix the rules.

Storage full? That’ll do it

If the root filesystem is 100% full, pveproxy can’t write temp files and dies. Check with df -h /. If it’s full, clean up old logs or move backups. I’ve seen this bite people after a big vzdump backup filled the local disk.

Another storage gotcha: if you have a mount point that’s not responding (like a dead NFS share), the web GUI can hang or time out. Check mount and unmount any stale shares.

DNS and hostname

If the hostname doesn’t resolve to the host’s IP, pveproxy can fail to bind. Check /etc/hosts and make sure your hostname is there. Also verify hostname --ip-address returns the right IP.

What I’d do

Start with pveproxy status and logs. That catches 80% of cases. Then firewall, then disk space. Don’t go reinstalling Proxmox until you’ve checked these three things.

If you’re still stuck, there’s a more detailed post on Can’t Access Proxmox Web GUI: Fix It Fast that covers some edge cases.