The Proxmox VE web interface listens on TCP port 8006, so you open https://your-host-or-ip:8006 and log in as root in the PAM realm. Proxmox Backup Server uses 8007 and Proxmox Datacenter Manager uses 8443. I found no setting in the Proxmox docs that moves the VE web port; a Proxmox wiki page uses a reverse proxy in front instead.
At a glance
- Class
- Homelab
Provenance
- Nov 18, 2026Published
The Proxmox VE web interface is on TCP port 8006. Open https://your-host-or-ip:8006, using the IP address you gave the installer, and log in as root with the realm set to PAM. Proxmox’s own installation chapter gives exactly that form: the installer’s IP address plus port 8006, for example https://youripaddress:8006.
The other two Proxmox products with a web interface use different ports:
| Product | Web interface port | URL form from its docs |
|---|---|---|
| Proxmox VE | TCP 8006 | https://youripaddress:8006 |
| Proxmox Backup Server | TCP 8007 | https://youripaddress:8007 |
| Proxmox Datacenter Manager | TCP 8443 | https://youripaddress:8443 |
If you are following the install from scratch, how to install Proxmox VE and the mini PC setup walkthrough cover the steps before that browser tab.
Every port Proxmox VE documents
Proxmox VE’s firewall chapter has a section called “Ports used by Proxmox VE”. This is that list, with the other ports the manual names elsewhere added underneath.
| Port | Protocol | What it is | Where the docs say so |
|---|---|---|---|
| 8006 | TCP | Web interface (HTTP/1.1 over TLS) and the API | Firewall chapter; pveproxy |
| 5900-5999 | TCP | VNC web console (WebSocket) | Firewall chapter |
| 3128 | TCP | SPICE proxy | Firewall chapter |
| 22 | TCP | sshd, “used for cluster actions” | Firewall chapter; clustering requirements |
| 111 | UDP | rpcbind | Firewall chapter |
| 25 | TCP, outgoing | sendmail | Firewall chapter |
| 5405-5412 | UDP | corosync cluster traffic | Firewall chapter; clustering requirements |
| 60000-60050 | TCP | Live migration (VM memory and local-disk data) | Firewall chapter |
| 5403 | TCP | Default port of the qnetd server, when you use an external QDevice vote | Clustering chapter |
| 80 | TCP | Built-in web server for Let’s Encrypt http-01 certificate validation | System administration chapter |
| 85 (127.0.0.1) | TCP | pvedaemon, the privileged API daemon; local only | Service daemons chapter |
Three notes on that table:
- The cluster ports only matter between nodes. The clustering chapter’s requirements are UDP 5405-5412 for corosync and an SSH connection on TCP 22 between all nodes. The migration range is for moving guests: if you move guests between hosts, Proxmox clustering and HA and moving a VM without a cluster are the pages that use it.
- Port 85 is not reachable from outside. The manual says pvedaemon “listens to a local address only, so you cannot access it from outside”. The web interface on 8006 is served by pveproxy, which forwards anything that needs more privileges to pvedaemon.
- Port 80 is only for certificates. The http-01 plugin needs port 80 of the node reachable from the internet and no other listener on it. If you can’t expose port 80, the docs also describe a dns-01 plugin.
Proxmox Backup Server and Datacenter Manager
Both products publish less than Proxmox VE does. I searched the documentation pages of each for port statements; this is everything I found.
Proxmox Backup Server (documentation 4.2.11-1)
| Port | What it is | Where the docs say so |
|---|---|---|
| TCP 8007 | Web interface and API over HTTPS (the proxmox-backup-proxy daemon) | Installation; Graphical User Interface; Host System Administration |
| 127.0.0.1:82 | Management API of the proxmox-backup daemon, local only | Host System Administration |
| 8007 (default) | The --port option of the client tools, and the port option when Proxmox VE adds a Backup Server as storage | Backup Client Usage; Proxmox VE administration guide |
| TCP 80 | Built-in web server for ACME http-01 validation | Host System Administration |
The Backup Server docs have no firewall port list like the one in Proxmox VE. They do say that installing it directly on the hypervisor is not recommended: it is safer to use a separate physical server, so that if the hypervisor fails you can still reach the backups.
Proxmox Datacenter Manager (documentation 1.1.9)
| Port | What it is | Where the docs say so |
|---|---|---|
| TCP 8443 | Web interface and API over HTTPS (the proxmox-datacenter-api daemon) | Installation; Web Interface; Host System Administration |
| 8443 (default) | The --port default of the command-line client | Command Syntax |
| TCP 80 | Built-in web server for ACME http-01 validation | Host System Administration |
The privileged Datacenter Manager daemon uses a restricted UNIX socket rather than a port, so there is nothing to open there. One discrepancy: the introduction’s technology-stack paragraph says communication “occurs over TCP port 443 (HTTPS)”. Its installation page, web interface page, daemon description and client default all say 8443, so I’d treat 8443 as the answer and check with ss -tlnp on your own install if the difference matters to you.
What Proxmox says about changing or proxying port 8006
Changing the port. I searched the administration guide and the pveproxy manual page for a setting that moves the web interface off 8006 and did not find one. What pveproxy does document, in /etc/default/pveproxy:
LISTEN_IPbinds pveproxy and spiceproxy to one address instead of the wildcard address. The docs say it can restrict the socket to an internal interface for less exposure, and that it is not recommended on clustered systems, because the nodes need access to pveproxy to communicate. Applying it takes a reboot orsystemctl restart pveproxy.service spiceproxy.service, and the docs warn a restart can interrupt long-running workers such as a console or shell.ALLOW_FROM,DENY_FROMandPOLICYset apache2-style access control lists, for exampleALLOW_FROM="10.0.0.1-10.0.0.5,192.168.0.0/22". The subnet calculator will turn a range into a CIDR if you need one.PROXY_REAL_IP_HEADERmakes pveproxy log the client address from a header (for exampleX-Forwarded-For) when a proxy sits in front of it.
Proxying it onto 443. The Proxmox VE wiki page “Web Interface Via Nginx Proxy” is the only Proxmox page I found that addresses it, and it is a wiki page rather than the administration guide. Its stated reason is that “sometimes there is a firewall restriction that blocks port 8006”, and it adds “we shouldn’t touch the port config in proxmox”, so nginx provides the interface on port 443 instead. The 443 server block from that page:
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name _;
ssl_certificate /etc/pve/local/pve-ssl.pem;
ssl_certificate_key /etc/pve/local/pve-ssl.key;
proxy_redirect off;
location / {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_pass https://localhost:8006;
proxy_buffering off;
client_max_body_size 0;
proxy_connect_timeout 3600s;
proxy_read_timeout 3600s;
proxy_send_timeout 3600s;
send_timeout 3600s;
}
}
The page also adds a systemd override so nginx starts only after pve-cluster.service, because those certificates live under /etc/pve. Two cautions from the page itself: it says it was tested from Proxmox 3.4 to 6.3, and it was last edited in July 2024. I have not tested it on a current release, so treat it as a starting point. If you would rather have a general reverse proxy than a hand-written nginx file, Caddy, Nginx Proxy Manager and Traefik compared covers the options. If the real reason you want 443 is reaching the interface from outside your house, my Tailscale remote access guide covers that separately; I’m not drawing on Proxmox’s docs for it.
The firewall and 8006
Proxmox VE’s firewall is off by default. The chapter says it is completely disabled by default; you enable it cluster-wide with enable: 1 in the [OPTIONS] section of /etc/pve/firewall/cluster.fw (or from the web interface). The docs warn to open an SSH connection to a host before enabling it, so you still have access if something goes wrong.
When it is on, traffic to all hosts is blocked by default, with exceptions for traffic coming from the local network to the web interface, SSH and other important services. The chapter’s default-rules list says that, even with the input policy on DROP or REJECT, TCP from management hosts is still allowed to 8006, 5900-5999, 3128, 22 and 60000-60050, along with UDP 5405-5412 in the cluster network. To administer a host from a different network, you need to write rules allowing those remote addresses to port 8006, or add them to the management IP set, which the docs say is allowed to do the normal management tasks (web interface, VNC, SPICE, SSH) and applies to host firewalls only.
Why the browser warns about the certificate
Proxmox’s documentation explains the warning rather than leaving it to guesswork. Each Proxmox VE cluster creates its own self-signed certificate authority and signs a certificate for each node. By default the web interface uses the node certificate at /etc/pve/nodes/NODENAME/pve-ssl.pem, “signed by the cluster CA and therefore not automatically trusted by browsers and operating systems”. Backup Server and Datacenter Manager each generate a self-signed certificate too.
What the Proxmox VE docs give you for removing the warning:
- Trust the cluster CA. Copy
/etc/pve/pve-root-ca.pemfrom any cluster node (for example withscp) and import it into the operating system or browser trust store. The docs say there is no API or web interface endpoint to download it. - Upload a certificate from a commercial CA through the web interface; the key must not be password protected.
- Use ACME (Let’s Encrypt), which is built into the API and web interface. It validates with a built-in web server on port 80 or with a DNS plugin.
The docs warn not to replace or hand-edit the automatically generated node certificate files or the cluster CA files. Backup Server and Datacenter Manager offer the same three options for their own certificates, and Datacenter Manager’s remotes chapter adds one catch: it pins the fingerprint of a self-signed remote’s certificate, so if that remote renews its certificate, connections fail until you update the stored fingerprint.
Frequently asked questions
What is the default port number for Proxmox?
Is Proxmox port 8006 TCP or UDP?
How do I access my Proxmox server?
How to access Proxmox via web?
Does Proxmox have a firewall by default?
What is the Proxmox Backup Server default port?
What is the Proxmox Datacenter Manager default port?
Can I change the Proxmox web interface port?
Sources and corrections
- Last updated
- Methodology
- See our methodology for research and review standards. It draws on 17 cited sources, listed below, each checked against the original page on 2026-11-17. Every port and default on this page was read on 2026-11-17 from Proxmox’s own documentation: the Proxmox VE Administration Guide (version 9.2.14, build date 6 November 2026) and its firewall, installation, clustering and system administration chapters; the Proxmox Backup Server documentation (4.2.11-1); and the Proxmox Datacenter Manager documentation (1.1.9). I searched the Backup Server and Datacenter Manager docs pages for port statements; the ports in the tables below are all I found. I ran no command on a Proxmox host for this page and did not test the nginx configuration. The reverse-proxy section reports what the Proxmox wiki says, with the wiki’s own stated test range and last-edit date.
- Sources
- Proxmox VE Administration Guide: Proxmox VE Firewall (Ports used by Proxmox VE, default rules, enabling the firewall) accessed 2026-11-17
- Proxmox VE Administration Guide: Installation (accessing the management interface) accessed 2026-11-17
- pveproxy(8): Proxmox VE API Proxy Daemon (port, LISTEN_IP, ALLOW_FROM) accessed 2026-11-17
- Proxmox VE Administration Guide: Host System Administration (certificate management, ACME) accessed 2026-11-17
- Proxmox VE Administration Guide: Cluster Manager (requirements, QDevice port 5403) accessed 2026-11-17
- Proxmox VE Administration Guide (full manual: pvedaemon, Proxmox Backup Server storage port) accessed 2026-11-17
- Proxmox VE wiki: Web Interface Via Nginx Proxy accessed 2026-11-17
- Proxmox Backup Server documentation: Installation accessed 2026-11-17
- Proxmox Backup Server documentation: Graphical User Interface accessed 2026-11-17
- Proxmox Backup Server documentation: Host System Administration (certificates, service daemons) accessed 2026-11-17
- Proxmox Backup Server documentation: Backup Client Usage (server port) accessed 2026-11-17
- Proxmox Datacenter Manager documentation: Installation accessed 2026-11-17
- Proxmox Datacenter Manager documentation: Web Interface accessed 2026-11-17
- Proxmox Datacenter Manager documentation: Host System Administration (certificates, service daemons) accessed 2026-11-17
- Proxmox Datacenter Manager documentation: Command Syntax (client --port) accessed 2026-11-17
- Proxmox Datacenter Manager documentation: Introduction (technology stack) accessed 2026-11-17
- Proxmox Datacenter Manager documentation: Remotes (certificate fingerprints) accessed 2026-11-17
- Corrections
- Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.