[SOLVED] Need Help! Cannot access web interface

cahsobo

New Member
Feb 28, 2023
21
1
3
Hi, I'm new to Proxmox VE. I've setup Proxmox server using automated IP 192.168.0.13. And I'm trying to access the web interface from 192.168.0.10. But the browser still can't find it. I can login by SSH with no problem.
ip a command gave this output:

Code:
11: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:e0:0a:47:02:b4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.13/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::2e0:aff:fe47:2b4/64 scope link
       valid_lft forever preferred_lft forever
 
Hi,

what error exactly does the browser produce and what address did you type in exactly?
The web GUI only uses HTTPS and runs on port 8006; did you navigate to https://192.168.0.13:8006?

Otherwise, are there any error messages in the syslog (journalctl -b -e) that might be relevant? And what does systemctl status pveproxy.service report?
 
Hi,

what error exactly does the browser produce and what address did you type in exactly?
The web GUI only uses HTTPS and runs on port 8006; did you navigate to https://192.168.0.13:8006?

Otherwise, are there any error messages in the syslog (journalctl -b -e) that might be relevant? And what does systemctl status pveproxy.service report?
yes. i did
here's the output for journalctl -b -e
Code:
Feb 28 18:07:24 vm systemd[1598]: Reached target Basic System.
Feb 28 18:07:24 vm systemd[1598]: Reached target Main User Target.
Feb 28 18:07:24 vm systemd[1598]: Startup finished in 201ms.
Feb 28 18:07:24 vm systemd[1]: Started User Manager for UID 0.
Feb 28 18:07:24 vm systemd[1]: Started Session 1 of user root.
Feb 28 18:08:01 vm chronyd[1289]: Selected source 202.65.114.202 (2.debian.pool>
Feb 28 18:10:02 vm kernel: r8169 0000:07:00.0 enp7s0: Link is Down
Feb 28 18:10:02 vm kernel: vmbr0: port 1(enp7s0) entered disabled state
Feb 28 18:10:08 vm kernel: r8169 0000:07:00.0 enp7s0: Link is Up - 100Mbps/Full>
Feb 28 18:10:08 vm kernel: vmbr0: port 1(enp7s0) entered blocking state
Feb 28 18:10:08 vm kernel: vmbr0: port 1(enp7s0) entered forwarding state
Feb 28 18:13:09 vm sshd[2378]: Accepted password for root from 192.168.0.10 por>
Feb 28 18:13:09 vm sshd[2378]: pam_unix(sshd:session): session opened for user >
Feb 28 18:13:09 vm systemd-logind[994]: New session 3 of user root.
Feb 28 18:13:09 vm systemd[1]: Started Session 3 of user root.
Feb 28 18:17:01 vm CRON[2903]: pam_unix(cron:session): session opened for user >
Feb 28 18:17:01 vm CRON[2904]: (root) CMD (   cd / && run-parts --report /etc/c>
Feb 28 18:17:01 vm CRON[2903]: pam_unix(cron:session): session closed for user >
Feb 28 18:21:19 vm systemd[1]: Starting Cleanup of Temporary Directories...
Feb 28 18:21:19 vm systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 28 18:21:19 vm systemd[1]: Finished Cleanup of Temporary Directories.
Feb 28 18:36:44 vm smartd[993]: Device: /dev/sda [SAT], SMART Usage Attribute: >
Feb 28 18:36:44 vm smartd[993]: Device: /dev/sda [SAT], SMART Usage Attribute: >


systemctl status pveproxy.service output:
Code:
systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor pres>
     Active: active (running) since Tue 2023-02-28 18:06:54 WIB; 42min ago
    Process: 1488 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited>
    Process: 1490 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCC>
   Main PID: 1492 (pveproxy)
      Tasks: 4 (limit: 38346)
     Memory: 140.5M
        CPU: 2.050s
     CGroup: /system.slice/pveproxy.service
             ├─1492 pveproxy
             ├─1493 pveproxy worker
             ├─1494 pveproxy worker
             └─1495 pveproxy worker

Feb 28 18:06:52 vm systemd[1]: Starting PVE API Proxy Server...
Feb 28 18:06:54 vm pveproxy[1492]: starting server
Feb 28 18:06:54 vm pveproxy[1492]: starting 3 worker(s)
Feb 28 18:06:54 vm pveproxy[1492]: worker 1493 started
Feb 28 18:06:54 vm pveproxy[1492]: worker 1494 started
Feb 28 18:06:54 vm pveproxy[1492]: worker 1495 started
Feb 28 18:06:54 vm systemd[1]: Started PVE API Proxy Server.
 
Last edited:
Hm, nothing there, at least in this little snippet. You can scroll up/down using your arrow keys (or Ctrl+U/Ctrl+D for page-wise scrolling).
Errors/warnings should be indicated in a red/yellow color. (You can also provide the full log, but if you do so, please as an attachment to your post and not inline!)

You forgot about the output systemctl status pveproxy.service - this service runs the actual HTTPS server on port 8006.

Did you activate the firewall on this node?
 
Hm, nothing there, at least in this little snippet. You can scroll up/down using your arrow keys (or Ctrl+U/Ctrl+D for page-wise scrolling).
Errors/warnings should be indicated in a red/yellow color. (You can also provide the full log, but if you do so, please as an attachment to your post and not inline!)

You forgot about the output systemctl status pveproxy.service - this service runs the actual HTTPS server on port 8006.

Did you activate the firewall on this node?
yes. i checked the firewall checkbox on first installation



Code:
systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor pres>
Active: active (running) since Tue 2023-02-28 18:06:54 WIB; 42min ago
Process: 1488 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited>
Process: 1490 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCC>
Main PID: 1492 (pveproxy)
Tasks: 4 (limit: 38346)
Memory: 140.5M
CPU: 2.050s
CGroup: /system.slice/pveproxy.service
├─1492 pveproxy
├─1493 pveproxy worker
├─1494 pveproxy worker
└─1495 pveproxy worker

Feb 28 18:06:52 vm systemd[1]: Starting PVE API Proxy Server...
Feb 28 18:06:54 vm pveproxy[1492]: starting server
Feb 28 18:06:54 vm pveproxy[1492]: starting 3 worker(s)
Feb 28 18:06:54 vm pveproxy[1492]: worker 1493 started
Feb 28 18:06:54 vm pveproxy[1492]: worker 1494 started
Feb 28 18:06:54 vm pveproxy[1492]: worker 1495 started
Feb 28 18:06:54 vm systemd[1]: Started PVE API Proxy Server.
 
The service is running, that's good.

yes. i checked the firewall checkbox on first installation
What's your current configuration? Can you provide the output of cat /etc/pve/firewall/cluster.fw and cat /etc/pve/local/host.fw?

Also, does curl -v -k https://192.168.0.13:8006 work? Does it put out the expected HTML?
 
The service is running, that's good.


What's your current configuration? Can you provide the output of cat /etc/pve/firewall/cluster.fw and cat /etc/pve/local/host.fw?

Also, does curl -v -k https://192.168.0.13:8006 work? Does it put out the expected HTML?
unfortunately it does not exist. does that mean the firewall is not active?
Code:
root@vm:~# cat /etc/pve/firewall/cluster.fw
cat: /etc/pve/firewall/cluster.fw: No such file or directory
root@vm:~# cat /etc/pve/local/host.fw
cat: /etc/pve/local/host.fw: No such file or directory
root@vm:~#

Code:
curl -v -k https://192.168.0.13:8006
*   Trying 192.168.0.13:8006...
* TCP_NODELAY set
* Connected to 192.168.0.13 (192.168.0.13) port 8006 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: OU=PVE Cluster Node; O=Proxmox Virtual Environment; CN=vm.dr.com
*  start date: Feb 24 05:56:27 2023 GMT
*  expire date: Feb 23 05:56:27 2025 GMT
*  issuer: CN=Proxmox Virtual Environment; OU=c3c5846a-0ef0-4187-b3fe-bf0730f49c0e; O=PVE Cluster Manager CA
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
> GET / HTTP/1.1
> Host: 192.168.0.13:8006
> User-Agent: curl/7.68.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Cache-Control: max-age=0
< Connection: Keep-Alive
< Date: Tue, 28 Feb 2023 12:37:51 GMT
< Pragma: no-cache
< Server: pve-api-daemon/3.0
< Content-Length: 2215
< Content-Type: text/html; charset=utf-8
< Expires: Tue, 28 Feb 2023 12:37:51 GMT
<
<!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>vm - 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/css/ext6-pve.css?ver=7.3-3" />
    <link rel="stylesheet" type="text/css" href="/pwt/css/ext6-pmx.css?ver=3.5.3" />
    
    <script type='text/javascript'>function gettext(buf) { return buf; }</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: 'vm',
    UserName: '',
    CSRFPreventionToken: 'null'
    };
    </script>
    <script type="text/javascript" src="/proxmoxlib.js?ver=3.5.3"></script>
    <script type="text/javascript" src="/pve2/js/pvemanagerlib.js?ver=7.3-3"></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>
* Connection #0 to host 192.168.0.13 left intact
 
unfortunately it does not exist. does that mean the firewall is not active?
Yes, exactly. For reference, if you want to configure the firewall after solving this, have a look here.
It needs be enabled both on the datacenter level as well as for each node.

Anyway, curl retrieves the (login) page successfully, so everything is working fine on the Proxmox VE side.
Therefore the problem seems to be with you browser - what browser are you using exactly?

EDIT: Does you browser allow unverified TLS-certificates?
 
Last edited:
Yes, exactly. For reference, if you want to configure the firewall after solving this, have a look here.
It needs be enabled both on the datacenter level as well as for each node.

Anyway, curl retrieves the (login) page successfully, so everything is working fine on the Proxmox VE side.
Therefore the problem seems to be with you browser - what browser are you using exactly?

EDIT: Does you browser allow unverified TLS-certificates?
actually, i have no idea. i'm using firefox on linux mint version 95.01
 
Could you provide a screenshot of the error page Firefox displays when you try to open https://192.168.0.13:8006?

And maybe try some other browser like Chromium? To see if it is indeed some problem with Firefox itself or not.
 
Could you provide a screenshot of the error page Firefox displays when you try to open https://192.168.0.13:8006?

And maybe try some other browser like Chromium? To see if it is indeed some problem with Firefox itself or not.here
here's the browser output:
 

Attachments

  • proxmox.png
    proxmox.png
    41.4 KB · Views: 69
did you run that curl command on your client or directly on PVE? If you didnt run it on client - repeat it on the client and confirm you get the same output.
If the output you provided is from your Linux client, then make sure you have "https://" in the URL preceding the IP address.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
did you run that curl command on your client or directly on PVE? If you didnt run it on client - repeat it on the client and confirm you get the same output.
If the output you provided is from your Linux client, then make sure you have "https://" in the URL preceding the IP address.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
of course i ran it from the client
 
of course i ran it from the client
Since everything seems to be working on the server side, and partially on the client side (curl), the issue is likely in your browser. Is it perhaps setup to use proxy? You can try to install a TUI browser such as "links", it wont give you a login page, but should provide another data point of client connectivity.

i.e. apt install links
links https://localhost:8006
once you accepted self-signed cert there should be a title in the top right corner. You can also press \ for source


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Since everything seems to be working on the server side, and partially on the client side (curl), the issue is likely in your browser. Is it perhaps setup to use proxy? You can try to install a TUI browser such as "links", it wont give you a login page, but should provide another data point of client connectivity.

i.e. apt install links
links https://localhost:8006
once you accepted self-signed cert there should be a title in the top right corner. You can also press \ for source


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
btw. i'm replying this from the client. i don't think my problem is the browser.
attached below is the output from links https://localhost:8006
the title appeared correctly i guess?

opening links from the client using command links https://192.168.0.13:8006 is also resulting in 100% exactly the same output.
 

Attachments

  • ss1.png
    ss1.png
    21 KB · Views: 54
  • ss2.png
    ss2.png
    12.5 KB · Views: 52
Last edited:
Both curl and links browser when run from your client machine have no issues connecting to the PVE interface. Only your Firefox browser appears to be affected.
Perhaps trying steps from here can help https://www.wikihow.com/Start-Firefox-in-Safe-Mode, or as suggested earlier a different browser altogether. If your phone is connected to the network - try from there.

To sum up: nothing so far points at a Server/PVE issue.

Good luck


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Both curl and links browser when run from your client machine have no issues connecting to the PVE interface. Only your Firefox browser appears to be affected.
Perhaps trying steps from here can help https://www.wikihow.com/Start-Firefox-in-Safe-Mode, or as suggested earlier a different browser altogether. If your phone is connected to the network - try from there.

To sum up: nothing so far points at a Server/PVE issue.

Good luck


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
i was curious. so i tried to install a new server. this problem does not exist when i tried to install a new server since the IP of the server was assigned from DHCP. BUTTTTTT..
even if i set my server's IP to get from DHCP server, it still won't display web interface.
it has now run on 192.168.0.11 assigned by DHCP from my router.
and the problem persists.
it has no problem if I i.e install a new server and get 192.168.0.12 as the assigned IP from DHCP.
but my old server still won't get to work.
I don't wanna start over from zero. since my server has already run 8 vms perfectly before.
 

Attachments

  • dhcp.png
    dhcp.png
    28.6 KB · Views: 24
since everyone is pointing on the browser, i then tried to find solution online and stumbled upon this trick. disabling the SSL certification in firefox. and voila! the web UI shows!!!
 

Attachments

  • disable cert.png
    disable cert.png
    14.1 KB · Views: 49
I am not following what you just did, but perhaps you also have a duplicate IP issue like the fellow here:
https://forum.proxmox.com/threads/e...b-ui-and-ssh-after-update.123474/#post-537175

Please see the troubleshooting steps used and follow them. Since I am not sure what you have installed and where at this point, it may be best for you to re-document everything:
- PVE: ip a
- PVE: /etc/network/interfaces
- PVE: grep -HE "ipconfig|net.:" /etc/pve/qemu-server/*.conf
- Client: ping [pveip]
- Client: ssh [pveip] ls
- Client: arp -an
- Client: arp -a [pveip]


Keep in mind that not a single "I cant access PVE web interface" thread in the last 12+ months has been caused by a bug in PVE, it has always been a user network misconfiguration.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
I am not following what you just did, but perhaps you also have a duplicate IP issue like the fellow here:
https://forum.proxmox.com/threads/e...b-ui-and-ssh-after-update.123474/#post-537175

Please see the troubleshooting steps used and follow them. Since I am not sure what you have installed and where at this point, it may be best for you to re-document everything:
- PVE: ip a
- PVE: /etc/network/interfaces
- PVE: grep -HE "ipconfig|net.:" /etc/pve/qemu-server/*.conf
- Client: ping [pveip]
- Client: ssh [pveip] ls
- Client: arp -an
- Client: arp -a [pveip]


Keep in mind that not a single "I cant access PVE web interface" thread in the last 12+ months has been caused by a bug in PVE, it has always been a user network misconfiguration.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
understood. thank you for your explanation.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!