[SOLVED] Can't access the Proxmox Web GUI from LAN

meni44

New Member
Aug 25, 2025
9
1
1
Hello folks,

I’m in need of some assistance regarding a Proxmox setup issue.

Background:​

I recently bought new hardware and migrated my Proxmox setup to a new server. On the new server, I installed Debian 13 with the GNOME Desktop Environment and then installed Proxmox. I replicated the configuration from my previous server and restored all my virtual machines. I understand that this is a special setup, but it serves a purpose for the environment where I’m using it.

Everything works fine:​

All VMs are running without issues, and they are accessible both externally and from the LAN via SSH and their respective web GUIs.

The issue:​

The problem I’m facing is that I can only access the Proxmox Web GUI (port 8006) from the server itself (the host). When trying to access it from any other machine in the LAN, I get a connection error (192.168.8.2:8006).

Here’s what I’ve tried so far:
  • Checked firewall settings and ensured that port 8006 is not blocked.
  • Verified the network configuration and confirmed that I can ping the Proxmox host from other LAN machines.
  • Tried disabling and configuring firewall rules, both on the host and via Proxmox.
  • Ensured that the hostname and /etc/hosts file are correct.
To confirm that the issue is specifically with Proxmox and not the network, I deployed a simple DokuWiki instance using Docker on the host itself (192.168.8.2:8080) and it works perfectly on port 8080, accessible from the same LAN (WebGUI).

Here are the relevant configuration files:​

  • /etc/network/interfaces
    • Code:
      source /etc/network/interfaces.d/*
      
      auto lo
      iface lo inet loopback
      
      auto enp45s0
      iface enp45s0 inet manual
      
      auto vmbr0
      iface vmbr0 inet static
              address 192.168.8.2/24
              gateway 192.168.8.1
              bridge-ports enp45s0
              bridge-stp off
              bridge-fd 0
      
      auto vmbr1
      iface vmbr1 inet manual
              bridge-ports none
              bridge-stp off
              bridge-fd 0
      
      auto vmbr103
      iface vmbr103 inet manual
              bridge-ports none
              bridge-stp off
              bridge-fd 0
      
      auto vmbr102
      iface vmbr102 inet manual
              bridge-ports none
              bridge-stp off
              bridge-fd 0
      
      auto vmbr999
      iface vmbr999 inet manual
              bridge-ports none
              bridge-stp off
              bridge-fd 0
      
      auto vmbr104
      iface vmbr104 inet manual
              bridge-ports none
              bridge-stp off
              bridge-fd 0
      
      auto vmbr105
      iface vmbr105 inet manual
              bridge-ports none
              bridge-stp off
              bridge-fd 0
      
      auto vmbr199
      iface vmbr199 inet manual
              bridge-ports none
              bridge-stp off
              bridge-fd 0
      
      auto vmbr106
      iface vmbr106 inet manual
              bridge-ports none
              bridge-stp off
              bridge-fd 0
  • /etc/hosts
    • Code:
      hosts: 127.0.0.1 localhost
      192.168.8.2 debian-proxmox
      
      # The following lines are desirable for IPv6 capable hosts
      ::1 localhost ip6-localhost ip6-loopback
      ff02::1 ip6-allnodes
      ff02::2 ip6-allrouters
  • /etc/hostname
    • Code:
      debian-proxmox
  • pveproxy service status logs
    • Code:
      Aug 10 23:56:55 debian-proxmox systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: Generating public/private rsa key pair.
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: Your identification has been saved in /root/.ssh/id_rsa
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: Your public key has been saved in /root/.ssh/id_rsa.pub
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: The key fingerprint is:
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: SHA256:xxxxx root@debian-proxmox
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: The key's randomart image is:
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: +---[RSA 4096]----+
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: |                 |
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: |       o         |
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: |..  E . o .      |
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: |oo o.  + o       |
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: |o =o=.o S        |
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: |o..B+o = o       |
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: |oo=o +o =..      |
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: |.++ *.o. .o.     |
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: |+o.=++.+=o..     |
      Aug 10 23:56:56 debian-proxmox pvecm[15068]: +----[SHA256]-----+
      Aug 10 23:56:56 debian-proxmox pvecm[15065]: got inotify poll request in wrong process - disabling inotify
      Aug 10 23:56:56 debian-proxmox pvecm[15065]: Error checking request extension section v3_req
      Aug 10 23:56:56 debian-proxmox pvecm[15065]: 4017D18E00740000:error:11000076:X509 V3 routines:a2i_GENERAL_NAME:bad ip address:../crypto/x509/v3_>
      Aug 10 23:56:56 debian-proxmox pvecm[15065]: 4017D18E00740000:error:11000080:X509 V3 routines:X509V3_EXT_nconf_int:error in extension:../crypto/>
      Aug 10 23:56:56 debian-proxmox pvecm[15064]: unable to generate pve certificate request:
      Aug 10 23:56:56 debian-proxmox pvecm[15064]: command 'openssl req -batch -new -config /tmp/pvesslconf-15065.tmp -key /etc/pve/nodes/debian-proxm>
      Aug 10 23:56:57 debian-proxmox pveproxy[15099]: starting server
      Aug 10 23:56:57 debian-proxmox pveproxy[15099]: starting 3 worker(s)
      Aug 10 23:56:57 debian-proxmox pveproxy[15099]: worker 15100 started
      Aug 10 23:56:57 debian-proxmox pveproxy[15099]: worker 15101 started
      Aug 10 23:56:57 debian-proxmox pveproxy[15099]: worker 15102 started
Has anyone experienced this or has an idea what might be causing this issue? I’ve tried everything I can think of but still can’t get the Proxmox Web GUI accessible from the LAN. On my old server, I can reach the Proxmox Web GUI without any issues from my LAN. Any help would be much appreciated!
 
Last edited:
Have you tried to explicitly put the "https" before the ip address ?
Thanks for your response. Yes, I tried it with HTTPS before the IP address. I also tried different clients and browser but nothing works. I only can reach the web GUI from the host itself (192.168.8.2).
 
Have you tried to change the host's IP address ? Or can you be sure that there is no IP conflict ?
 
Have you tried to change the host's IP address ? Or can you be sure that there is no IP conflict ?
Not yet but, the fact that DokuWiki on 192.168.8.2:8080 (just for test purpose) is reachable from other LAN clients should confirm there is no IP conflict on my network. I can also connect to ssh from the LAN without any issues.
 
I noticed some certificates error from your first post. try to recerts :

pvecm updatecerts -f
systemctl restart pveproxy

Sadly, it doesn't fix the issue, but the error is gone.

journalctl -u pveproxy -f
Code:
Aug 25 18:05:19 debian-proxmox systemd[1]: pveproxy.service: Deactivated successfully.
Aug 25 18:05:19 debian-proxmox systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Aug 25 18:05:19 debian-proxmox systemd[1]: pveproxy.service: Consumed 1.609s CPU time, 364.9M memory peak.
Aug 25 18:05:19 debian-proxmox systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Aug 25 18:05:20 debian-proxmox pveproxy[375229]: starting server
Aug 25 18:05:20 debian-proxmox pveproxy[375229]: starting 3 worker(s)
Aug 25 18:05:20 debian-proxmox pveproxy[375229]: worker 375230 started
Aug 25 18:05:20 debian-proxmox pveproxy[375229]: worker 375231 started
Aug 25 18:05:20 debian-proxmox pveproxy[375229]: worker 375232 started
Aug 25 18:05:20 debian-proxmox systemd[1]: Started pveproxy.service - PVE API Proxy Server.
 
Here is also a TCP dump from the host (192.168.8.2)

Code:
18:12:08.594436 enp45s0 In  IP 192.168.8.114.60124 > 192.168.8.2.8006: Flags [S], seq 4182423679, win 64240, options [mss 1460,sackOK,TS val 2607143607 ecr 0,nop,wscale 7], length 0
18:12:08.594456 vmbr0 In  IP 192.168.8.114.60124 > 192.168.8.2.8006: Flags [S], seq 4182423679, win 64240, options [mss 1460,sackOK,TS val 2607143607 ecr 0,nop,wscale 7], length 0
18:12:08.949234 enp45s0 In  IP 192.168.8.114.60128 > 192.168.8.2.8006: Flags [S], seq 1469793140, win 64240, options [mss 1460,sackOK,TS val 2607143961 ecr 0,nop,wscale 7], length 0
18:12:08.949252 vmbr0 In  IP 192.168.8.114.60128 > 192.168.8.2.8006: Flags [S], seq 1469793140, win 64240, options [mss 1460,sackOK,TS val 2607143961 ecr 0,nop,wscale 7], length 0
18:12:09.198200 enp45s0 In  IP 192.168.8.114.60136 > 192.168.8.2.8006: Flags [S], seq 1111006383, win 64240, options [mss 1460,sackOK,TS val 2607144210 ecr 0,nop,wscale 7], length 0
18:12:09.198219 vmbr0 In  IP 192.168.8.114.60136 > 192.168.8.2.8006: Flags [S], seq 1111006383, win 64240, options [mss 1460,sackOK,TS val 2607144210 ecr 0,nop,wscale 7], length 0
18:12:09.485983 enp45s0 In  IP 192.168.8.114.60146 > 192.168.8.2.8006: Flags [S], seq 545273017, win 64240, options [mss 1460,sackOK,TS val 2607144498 ecr 0,nop,wscale 7], length 0
18:12:09.486000 vmbr0 In  IP 192.168.8.114.60146 > 192.168.8.2.8006: Flags [S], seq 545273017, win 64240, options [mss 1460,sackOK,TS val 2607144498 ecr 0,nop,wscale 7], length 0
18:12:09.682885 enp45s0 In  IP 192.168.8.114.60162 > 192.168.8.2.8006: Flags [S], seq 2945280427, win 64240, options [mss 1460,sackOK,TS val 2607144695 ecr 0,nop,wscale 7], length 0
18:12:09.682899 vmbr0 In  IP 192.168.8.114.60162 > 192.168.8.2.8006: Flags [S], seq 2945280427, win 64240, options [mss 1460,sackOK,TS val 2607144695 ecr 0,nop,wscale 7], length 0
18:12:09.867989 enp45s0 In  IP 192.168.8.114.60166 > 192.168.8.2.8006: Flags [S], seq 2852754886, win 64240, options [mss 1460,sackOK,TS val 2607144880 ecr 0,nop,wscale 7], length 0
18:12:09.867997 vmbr0 In  IP 192.168.8.114.60166 > 192.168.8.2.8006: Flags [S], seq 2852754886, win 64240, options [mss 1460,sackOK,TS val 2607144880 ecr 0,nop,wscale 7], length 0
18:12:10.044339 enp45s0 In  IP 192.168.8.114.60178 > 192.168.8.2.8006: Flags [S], seq 3746132554, win 64240, options [mss 1460,sackOK,TS val 2607145056 ecr 0,nop,wscale 7], length 0
18:12:10.044354 vmbr0 In  IP 192.168.8.114.60178 > 192.168.8.2.8006: Flags [S], seq 3746132554, win 64240, options [mss 1460,sackOK,TS val 2607145056 ecr 0,nop,wscale 7], length 0
18:12:10.220066 enp45s0 In  IP 192.168.8.114.60194 > 192.168.8.2.8006: Flags [S], seq 3156802252, win 64240, options [mss 1460,sackOK,TS val 2607145232 ecr 0,nop,wscale 7], length 0
18:12:10.220082 vmbr0 In  IP 192.168.8.114.60194 > 192.168.8.2.8006: Flags [S], seq 3156802252, win 64240, options [mss 1460,sackOK,TS val 2607145232 ecr 0,nop,wscale 7], length 0
18:12:10.392720 enp45s0 In  IP 192.168.8.114.60208 > 192.168.8.2.8006: Flags [S], seq 514404798, win 64240, options [mss 1460,sackOK,TS val 2607145405 ecr 0,nop,wscale 7], length 0
18:12:10.392725 vmbr0 In  IP 192.168.8.114.60208 > 192.168.8.2.8006: Flags [S], seq 514404798, win 64240, options [mss 1460,sackOK,TS val 2607145405 ecr 0,nop,wscale 7], length 0
18:12:10.571221 enp45s0 In  IP 192.168.8.114.60210 > 192.168.8.2.8006: Flags [S], seq 2498399800, win 64240, options [mss 1460,sackOK,TS val 2607145583 ecr 0,nop,wscale 7], length 0
18:12:10.571236 vmbr0 In  IP 192.168.8.114.60210 > 192.168.8.2.8006: Flags [S], seq 2498399800, win 64240, options [mss 1460,sackOK,TS val 2607145583 ecr 0,nop,wscale 7], length 0
 
you need to change the Network management and use the Proxmox VE way.
don't use Networksetup with Desktop-Gnome-Tools. Sorry i can't remember the name.
 
you need to change the Network management and use the Proxmox VE way.
don't use Networksetup with Desktop-Gnome-Tools. Sorry i can't remember the name.
I think you mean the NetworkManager? I already disabled it. Likewise, I only configured the network from the proxmox web GUI.
 
To summarize: you deployed a desktop version of Debian with X interfaces (and likely many other “workstation” tools), then installed PVE, and finally added Docker on the same host.

You are able to run curl -k https://192.168.8.2:8006 directly from the hypervisor via SSH, but your browsers fail with a “connection error.”

It would be useful to clarify exactly what this “connection error” is and whether tools like curl or nc can successfully connect.

My recommendation is to start from scratch using either the PVE ISO or a vanilla Debian server installation. Confirm that PVE works as expected first, and then add any additional components at your own risk.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
To summarize: you deployed a desktop version of Debian with X interfaces (and likely many other “workstation” tools), then installed PVE, and finally added Docker on the same host.

You are able to run curl -k https://192.168.8.2:8006 directly from the hypervisor via SSH, but your browsers fail with a “connection error.”

It would be useful to clarify exactly what this “connection error” is and whether tools like curl or nc can successfully connect.

My recommendation is to start from scratch using either the PVE ISO or a vanilla Debian server installation. Confirm that PVE works as expected first, and then add any additional components at your own risk.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Thanks for your reply. Yes, that's pretty much what I did :D
I installed a vanilla Debian 13 with GNOME and workstation utilities, then added Proxmox. After I noticed the issue, I installed Docker later on for testing purposes. The problem I’m facing is that no connection can be established to port 8006 at all. In the browser, I get a "Can't establish a connection" error. However, port 8080 works fine (I tested it with a Dockerized DokuWiki instance). Everything works fine locally on the host as well with 8006.

Regarding your suggestion to start from scratch (debian iso), it makes sense, and I’ll likely do that in the coming days.

Here are the outputs from my tests from a client 192.168.8.122:
Code:
curl -k https://192.168.8.2:8006
curl: (7) Failed to connect to 192.168.8.2 port 8006 after 0 ms: Could not connect to server

nc -zv 192.168.8.2 8006
Ncat: Version 7.92 ( https://nmap.org/ncat )
Ncat: No route to host.

nc -zv 192.168.8.2 8080
Ncat: Version 7.92 ( https://nmap.org/ncat )
Ncat: Connected to 192.168.8.2:8080.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.

Here are the outputs from the host (192.168.8.2):
Code:
curl -k https://192.168.8.2:8006
<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
    <title>debian-proxmox - Proxmox Virtual Environment</title>
    <link rel="icon" sizes="128x128" href="/pve2/images/logo-128.png" />
    <link rel="apple-touch-icon" sizes="128x128" href="/pve2/images/logo-128.png" />
    <link rel="stylesheet" type="text/css" href="/pve2/ext6/theme-crisp/resources/theme-crisp-all.css?ver=7.0.0" />
    <link rel="stylesheet" type="text/css" href="/pve2/ext6/crisp/resources/charts-all.css?ver=7.0.0" />
    <link rel="stylesheet" type="text/css" href="/pve2/fa/css/font-awesome.css" />
    <link rel="stylesheet" type="text/css" href="/pve2/font-logos/css/font-logos.css" />
    <link rel="stylesheet" type="text/css" href="/pve2/css/ext6-pve.css?ver=9.0.5" />
    <link rel="stylesheet" type="text/css" href="/pwt/css/ext6-pmx.css?ver=v5.0.5-t1754474621" />
    <link rel="stylesheet" type="text/css" media="(prefers-color-scheme: dark)" href="/pwt/themes/theme-proxmox-dark.css?ver=v5.0.5-t1754474621" />
    
    <script type='text/javascript'>
        function gettext(message) { return message; }
        function ngettext(singular, plural, count) { return count === 1 ? singular : plural; }
    </script>
    
    <script type="text/javascript" src="/pve2/ext6/ext-all.js?ver=7.0.0"></script>
    <script type="text/javascript" src="/pve2/ext6/charts.js?ver=7.0.0"></script>
    
    <script type="text/javascript" src="/pve2/js/u2f-api.js"></script>
    <script type="text/javascript" src="/qrcode.min.js"></script>
    <script type="text/javascript">
    Proxmox = {
        Setup: { auth_cookie_name: 'PVEAuthCookie' },
        defaultLang: 'en',
        NodeName: 'debian-proxmox',
        UserName: '',
        CSRFPreventionToken: 'null',
        ConsentText: ''
    };
    </script>
    <script type="text/javascript" src="/proxmoxlib.js?ver=v5.0.5-t1754474621"></script>
    <script type="text/javascript" src="/pve2/js/pvemanagerlib.js?ver=9.0.5"></script>
    <script type="text/javascript" src="/pve2/ext6/locale/locale-en.js?ver=7.0.0"></script>

    <script type="text/javascript">
    if (typeof(PVE) === 'undefined') PVE = {};
    Ext.History.fieldid = 'x-history-field';
    Ext.onReady(function() { Ext.create('PVE.StdWorkspace');});
    </script>

  </head>
  <body>
    <!-- Fields required for history management -->
    <form id="history-form" class="x-hidden">
    <input type="hidden" id="x-history-field"/>
    </form>
  </body>
</html>


nc -zv 192.168.8.2 8006
debian-proxmox [192.168.8.2] 8006 (?) open
 
but the second test is successfull ;-)

Code:
nc -zv 192.168.8.2 8080
Ncat: Version 7.92 ( https://nmap.org/ncat )
Ncat: Connected to 192.168.8.2:8080.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.

also tcpdump shows packets are coming to the host -> but there is no answer - so my guess would be firewall....

did you really check no iptables or maybe nftables are running?
 
but the second test is successfull ;-)

Code:
nc -zv 192.168.8.2 8080
Ncat: Version 7.92 ( https://nmap.org/ncat )
Ncat: Connected to 192.168.8.2:8080.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.

also tcpdump shows packets are coming to the host -> but there is no answer - so my guess would be firewall....

did you really check no iptables or maybe nftables are running?
Yes, I checked everything. I performed now a full reinstall and started from scratch. Everything works now also the web GUI from the LAN. So sadly I can't provide really a solution to that problem nor the root cause. Nerveless, thanks to everyone for your awesome help <3
 
  • Like
Reactions: UdoB