No Webgui after updating 8.4x to 9.1x

E

Expalmi

New Member
Proxmox Subscriber
Aug 13, 2024
10
2
3
After updating my Proxmox server every vm and lxc work fine, I can access the server via ssh, the web ui does not work.

I tried safari and chrome both say the server is not reachable, same ip than ssh with https.

Loged in vai ssh,

curl -k https://127.0.0.1:8006 puts out

Code: 
curl -k https://127.0.0.1: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>miraculix - 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.1.6" />
    <link rel="stylesheet" type="text/css" href="/pwt/css/ext6-pmx.css?ver=v5.1.8-t1772102916" />
    <link rel="stylesheet" type="text/css" media="(prefers-color-scheme: dark)" href="/pwt/themes/theme-proxmox-dark.css?ver=v5.1.8-t1772102916" />
    
    <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: 'miraculix',
        UserName: '',
        CSRFPreventionToken: 'null',
        ConsentText: ''
    };
    </script>
    <script type="text/javascript" src="/proxmoxlib.js?ver=v5.1.8-t1772102916"></script>
    <script type="text/javascript" src="/pve2/js/pvemanagerlib.js?ver=9.1.6"></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>

Where can I look for the error
 
Expalmi said:
Where can I look for the error
Click to expand...
Check you router/firewall. Did you update the anything in your network? Try "curl" on your LAN IP as a confirmation. Try to direct connect a PC to your PVE to bypass your router.

Users often report a case where they use an IP for PVE that is located within a DHCP range of their smart router. The router then blocks any non-standard IP access to that IP. The solution is to move the PVE outside the DHCP range (or change the DHCP range).

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
Check you router/firewall. Did you update the anything in your network? Try "curl" on your LAN IP as a confirmation. Try to direct connect a PC to your PVE to bypass your router.

Users often report a case where they use an IP for PVE that is located within a DHCP range of their smart router. The router then blocks any non-standard IP access to that IP. The solution is to move the PVE outside the DHCP range (or change the DHCP range).

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
the Ip is static outside dhcp range.

SSH works fine, I can connect to server.

curl -k https://192.168.199.30:8006 says no connection
 
Expalmi said:
curl -k https://192.168.199.30:8006 says no connection
Click to expand...
From the console of the PVE after you logged in via SSH? Perhaps you can share your configuration, i.e. "ip a", etc.

standard list of questions:

What is the IP of the PVE server?
What is the IP of your workstation?
What is the IP of your gateway?
Can you ping the PVE server?
Can you ssh into PVE server?
What is the output of "ip a" on PVE?
What is the corresponding output from your workstation? (ipconfig /all ; ip a)
What is the output of "curl -k https://127.0.0.1:8006" when run directly from PVE (over SSH or physical console)?
What is the output of "curl -k https://<CHANGE_THIS_TO_YOUR_PVE_IP>:8006" when run directly from PVE (over SSH or physical console)?

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
bbgeek17 said:
From the console of the PVE after you logged in via SSH? Perhaps you can share your configuration, i.e. "ip a", etc.

standard list of questions:

What is the IP of the PVE server?
What is the IP of your workstation?
What is the IP of your gateway?
Can you ping the PVE server?
Can you ssh into PVE server?
What is the output of "ip a" on PVE?
What is the corresponding output from your workstation? (ipconfig /all ; ip a)
What is the output of "curl -k https://127.0.0.1:8006" when run directly from PVE (over SSH or physical console)?
What is the output of "curl -k https://<CHANGE_THIS_TO_YOUR_PVE_IP>:8006" when run directly from PVE (over SSH or physical console)?

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Thanks, I am sorry wasting your time, it was my fault.
Fail2ban stopped the connection, I tried my root password to often. It seems to be problem with my password.
Is there any known issue with special characters?
 
Expalmi said:
Thanks, I am sorry wasting your time, it was my fault.
Fail2ban stopped the connection, I tried my root password to often. It seems to be problem with my password.
Click to expand...
Thank you for letting the forum know. This is very helpful for the others as they run into similar issues.

Expalmi said:
Is there any known issue with special characters?
Click to expand...
I am not aware of any.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: Expalmi
bbgeek17 said:
Thank you for letting the forum know. This is very helpful for the others as they run into similar issues.


I am not aware of any.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
I found the problem
/etc/pve/datacenter.cfg contained webauthn: id=xxxxx
I commented that out, login works again.
With 8.4x this line did not cause any problems
 
  • Like
Reactions: bbgeek17 and bl1mp
You must log in or register to reply here.
Top Bottom
Back