[SOLVED] Can't find Proxmox GUI

P

PedanticDan

New Member
Aug 6, 2026
3
1
3
I've been running Home Assistant for while in a Promo VM. I decided I wanted to add another VM, but I can't find the GUI. The Proxmox machine is on Debian 13, pve-manager is 9.2, and teh machine is only listening on ports 22, 25, 85, 111, and 3128.

Over the last couple days. I've searched for information on how to enable/disable the GUI, but I have not found anything.

Can someone point to docs, or troubleshottig info to figure why there is nothing listeing on port 8006?
 
The web interface is provided by pveproxy and should listen on HTTPS port 8006, so there isn’t a separate GUI switch.

Check why the proxy is not running:

systemctl status pveproxy
journalctl -b -u pveproxy

Then try:

systemctl restart pveproxy
The GUI should be at:

https://<server-ip>:8006/
If it still doesn’t start, please post the output of the first two commands plus pveversion -v.
 
  • Like
Reactions: d.oishi, Johannes S and JohnnieKF
It appears that pveproxy is running:
Code: 
root@proxmox:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/usr/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
     Active: active (running) since Thu 2026-08-06 13:58:53 MDT; 1min 22s ago
 Invocation: f9bc4c6224104629b71327a5b451d054
    Process: 530531 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 530534 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
    Process: 530540 ExecStartPost=sh -c [ ! -e /var/log/pveam.log ] && /usr/bin/pveupdate (code=exited, status=1/FAILURE)
   Main PID: 530535 (pveproxy)
      Tasks: 4 (limit: 34839)
     Memory: 164.1M (peak: 187.2M)
        CPU: 2.008s
     CGroup: /system.slice/pveproxy.service
             ├─530535 pveproxy
             ├─530536 "pveproxy worker"
             ├─530537 "pveproxy worker"
             └─530538 "pveproxy worker"

Aug 06 13:58:51 proxmox systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Aug 06 13:58:53 proxmox pveproxy[530535]: starting server
Aug 06 13:58:53 proxmox pveproxy[530535]: starting 3 worker(s)
Aug 06 13:58:53 proxmox pveproxy[530535]: worker 530536 started
Aug 06 13:58:53 proxmox pveproxy[530535]: worker 530537 started
Aug 06 13:58:53 proxmox pveproxy[530535]: worker 530538 started
Aug 06 13:58:53 proxmox systemd[1]: Started pveproxy.service - PVE API Proxy Server.

"journalctl -b -u pveproxy" results in this output:

Code: 
Aug 06 14:04:00 proxmox systemd[1]: Stopping pveproxy.service - PVE API Proxy Server...
Aug 06 14:04:01 proxmox pveproxy[530535]: received signal TERM
Aug 06 14:04:01 proxmox pveproxy[530535]: server closing
Aug 06 14:04:01 proxmox pveproxy[530537]: worker exit
Aug 06 14:04:01 proxmox pveproxy[530536]: worker exit
Aug 06 14:04:01 proxmox pveproxy[530538]: worker exit
Aug 06 14:04:01 proxmox pveproxy[530535]: worker 530537 finished
Aug 06 14:04:01 proxmox pveproxy[530535]: worker 530538 finished
Aug 06 14:04:01 proxmox pveproxy[530535]: worker 530536 finished
Aug 06 14:04:01 proxmox pveproxy[530535]: server stopped
Aug 06 14:04:02 proxmox systemd[1]: pveproxy.service: Deactivated successfully.
Aug 06 14:04:02 proxmox systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Aug 06 14:04:02 proxmox systemd[1]: pveproxy.service: Consumed 3.618s CPU time, 373.2M memory peak.
Aug 06 14:04:16 proxmox systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Aug 06 14:04:18 proxmox pveproxy[531531]: starting server
Aug 06 14:04:18 proxmox pveproxy[531531]: starting 3 worker(s)
Aug 06 14:04:18 proxmox pveproxy[531531]: worker 531532 started
Aug 06 14:04:18 proxmox pveproxy[531531]: worker 531533 started
Aug 06 14:04:18 proxmox pveproxy[531531]: worker 531534 started
Aug 06 14:04:18 proxmox systemd[1]: Started pveproxy.service - PVE API Proxy Server.

Still, nothing is listening on port 8006 even after "systemctl restart pveproxy":

Code: 
root@proxmox:~# nmap -sS 10.24.86.54
Starting Nmap 7.95 ( https://nmap.org ) at 2026-08-06 14:05 MDT
Nmap scan report for proxmox.local (10.24.86.54)
Host is up (0.0000060s latency).
Not shown: 997 closed tcp ports (reset)
PORT     STATE SERVICE
22/tcp   open  ssh
111/tcp  open  rpcbind
3128/tcp open  squid-http

Nmap done: 1 IP address (1 host up) scanned in 0.07 seconds
 
samuel-rufi said:
The web interface is provided by pveproxy and should listen on HTTPS port 8006, so there isn’t a separate GUI switch.

Check why the proxy is not running:

systemctl status pveproxy
journalctl -b -u pveproxy

Then try:

systemctl restart pveproxy
The GUI should be at:

https://<server-ip>:8006/
If it still doesn’t start, please post the output of the first two commands plus pveversion -v.
Click to expand...

Apparently, restarting pveproxy solved the problem. Thanks!
 
  • Like
Reactions: samuel-rufi
You must log in or register to reply here.
Top Bottom
Back