Can’t Access Proxmox Web GUI: Fix It Fast

Can’t access Proxmox web GUI? It’s usually the pveproxy service, a firewall rule, or a stale browser cache. Here’s how to fix it without reinstalling.

Check if pveproxy is running

The web interface runs on pveproxy. If it’s dead, you get nothing. SSH into the node and run:

systemctl status pveproxy

If it’s not active, start it:

systemctl start pveproxy

Still nothing? Check the logs:

journalctl -u pveproxy -f

Look for bind errors or certificate issues. A common one is a missing or expired SSL cert. You can regenerate it with:

pvecm updatecerts --force

Then restart pveproxy.

Port 8006 and firewall

The GUI listens on TCP 8006. If you changed the firewall or iptables, that’s the next suspect. On the node, check:

ss -tlnp | grep 8006

You should see pveproxy listening. If not, something’s blocking it. If you use the Proxmox firewall, make sure the host has a rule allowing 8006 from your IP. Or just disable the firewall temporarily to test:

pve-firewall stop

If the GUI comes up, you know where to look.

Browser cache and cookies

This one’s stupid but common. The Proxmox GUI uses a lot of JavaScript and sometimes the cached version breaks after an update. Clear your browser cache for the Proxmox host, or try an incognito window. If that works, you’re done.

Check the host’s network config

If you can’t even SSH, the problem is deeper. See No SSH and GUI Access on Proxmox: Recover from the Console for console recovery. But if SSH works and GUI doesn’t, it’s likely one of the above.

Also check /etc/hosts and /etc/network/interfaces for any recent changes. A misconfigured bridge can break the web UI while leaving SSH up.

What I’d do

Start with pveproxy status and logs. That fixes 80% of cases. Then check the firewall. Then clear the browser cache. Don’t reinstall Proxmox over this—it’s almost always a simple service or network issue.