Cannot Connect to Port 8006 to Access Browser GUI: A Shell-First Diagnostic Path

Cannot connect to port 8006 to access browser GUI? The fix is almost always one of three things: pveproxy isn’t running, it’s bound to the wrong address, or a firewall rule is blocking you. Here’s how to check each one from the shell, in the order that actually finds the problem.

Check if pveproxy is even running

pveproxy is the daemon that serves the web interface. If it’s dead, port 8006 is closed and you get connection refused. Check its status:

systemctl status pveproxy

If it’s not active, start it and see if it stays up:

systemctl start pveproxy
journalctl -u pveproxy -f

The journal will show you why it’s failing. Missing certs, bad config, whatever. Fix that first.

See what’s actually listening on 8006

Run ss to see if anything is bound to the port:

ss -tlnp | grep 8006

You want a line showing 0.0.0.0:8006 or your specific IP. If it’s bound to 127.0.0.1:8006, that’s your problem — pveproxy is only listening on localhost. Edit /etc/default/pveproxy and set LISTEN_IP to your actual IP or 0.0.0.0, then restart:

systemctl restart pveproxy

If nothing shows up at all, pveproxy isn’t running or it’s crashing on start. Go back to step one.

Firewall: is something dropping the packets?

Proxmox has its own firewall, and you might also have iptables or nftables rules from other stuff. Check if the Proxmox firewall is enabled on the node:

pve-firewall status

If it’s active, check the rules for the host. The web GUI needs port 8006 open from your client IP. You can test with a quick nc from your workstation:

nc -zv your-proxmox-ip 8006

If that fails but ss shows pveproxy listening, it’s a firewall. Disable the Proxmox firewall temporarily to confirm:

pve-firewall stop

Then re-enable and add the proper rule. This is the part that trips people up because the Proxmox firewall is off by default, but maybe someone turned it on.

My take

Nine times out of ten it’s pveproxy not running or bound to localhost. The firewall is a distant third. Check in that order and you’ll spend five minutes instead of an hour. If you’re still stuck, the Proxmox GUI Not Opening but CLI Does post has more on certs and pvedaemon, which can also cause weird failures.