Proxmox Web GUI stuck at loading and unable to apt update

F

f1shboll

New Member
Sep 12, 2024
9
1
3
Hello folks,I have read and followed the earlier thread https://forum.proxmox.com/threads/gui-webpage-stuck-on-loading.91900/ but it did not solve the issue for me.

I have re-installed a proxmox node and I'm trying to access the web UI. Below is the screenshot the loading screenScreenshot 2025-11-26 at 9.56.31 PM.png

I have SSH access to the node and i am able to
Code: 
curl -k https://localhost:8006
and got a response.
Code: 
<!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>pio - 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.1" />
    <link rel="stylesheet" type="text/css" href="/pwt/css/ext6-pmx.css?ver=v5.1.2-t1763394412" />
    <link rel="stylesheet" type="text/css" media="(prefers-color-scheme: dark)" href="/pwt/themes/theme-proxmox-dark.css?ver=v5.1.2-t1763394412" />
  
    <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: 'pio',
        UserName: '',
        CSRFPreventionToken: 'null',
        ConsentText: ''
    };
    </script>
    <script type="text/javascript" src="/proxmoxlib.js?ver=v5.1.2-t1763394412"></script>
    <script type="text/javascript" src="/pve2/js/pvemanagerlib.js?ver=9.1.1"></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>

The below is the output of my
Code: 
ip a
Code: 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: nic0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vmbr0 state UP group default qlen 1000
    link/ether 98:fa:9b:05:9f:57 brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
    altname enx98fa9b059f57
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 98:fa:9b:05:9f:57 brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.102/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::9afa:9bff:fe05:9f57/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever

Port scan shows that all the ports are open too.
Code: 
Starting Nmap 7.98 ( https://nmap.org ) at 2025-11-26 22:06 +0800
Nmap scan report for 192.168.10.102
Host is up (0.0036s latency).
Not shown: 996 closed tcp ports (conn-refused)
PORT     STATE SERVICE VERSION
22/tcp   open  ssh     OpenSSH 10.0p2 Debian 7 (protocol 2.0)
53/tcp   open  domain  NLnet Labs NSD
111/tcp  open  rpcbind 2-4 (RPC #100000)
| rpcinfo:
|   program version    port/proto  service
|   100000  2,3,4        111/tcp   rpcbind
|   100000  2,3,4        111/udp   rpcbind
|   100000  3,4          111/tcp6  rpcbind
|_  100000  3,4          111/udp6  rpcbind
3128/tcp open  http    Proxmox Virtual Environment REST API 3.0
|_http-server-header: pve-api-daemon/3.0
|_http-title: Site doesn't have a title.
Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel

1 perculier thing that i noticed though is I am not able to do apt update on the node. It will just be taking a long time to and stuck there. I've put my /etc/resolv.conf to 8.8.8.8 too to ensure the connection is flowing through and able to ping to google.com.

Code: 
Get:5 http://deb.debian.org/debian trixie/main amd64 Packages [13.3 MB]
Ign:5 http://deb.debian.org/debian trixie/main amd64 Packages                                         
Err:6 http://deb.debian.org/debian trixie/main Translation-en
  Connection timed out [IP: 146.75.46.132 80]
  404  Not Found [IP: 146.75.46.132 80]
Ign:5 http://deb.debian.org/debian trixie/main amd64 Packages
Fetched 83.7 kB in 7min 50s (178 B/s)
Error: Failed to fetch http://deb.debian.org/debian/dists/trixie/main/i18n/Translation-en  404  Not Found [IP: 146.75.46.132 80]
Error: Some index files failed to download. They have been ignored, or old ones used instead.

Any help would be appreciated
 
Last edited:
It could be you have some basic network issues with the NIC/cable/switch
do pings to your local gateway and to the machine you are trying to get to the admin pages from.
if you can change the speed of it's switch port to 100 duplex or half-duplex (from gigabit) just to get basic connectivity, that's a start.
or
ethtool -s enp0s31f6 speed 100 duplex half
or ethtool -s nic0 speed 100 duplex half
 
Last edited:
arghdubya said:
It could be you have some basic network issues with the NIC/cable/switch
do pings to your local gateway and to the machine you are trying to get to the admin pages from.
if you can change the speed of it's switch port to 100 duplex or half-duplex (from gigabit) just to get basic connectivity, that's a start.
or
ethtool -s enp0s31f6 speed 100 duplex half
or ethtool -s nic0 speed 100 duplex half
Click to expand...
Hello thank you for instructions. I am able to ping the gateway. I can ping the node itself too regardless of having a duplex.
Code: 
~# ping 192.168.10.1
PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
64 bytes from 192.168.10.1: icmp_seq=1 ttl=64 time=0.604 ms
64 bytes from 192.168.10.1: icmp_seq=2 ttl=64 time=0.973 ms
64 bytes from 192.168.10.1: icmp_seq=3 ttl=64 time=0.757 ms
64 bytes from 192.168.10.1: icmp_seq=4 ttl=64 time=0.371 ms
64 bytes from 192.168.10.1: icmp_seq=5 ttl=64 time=0.469 ms
64 bytes from 192.168.10.1: icmp_seq=6 ttl=64 time=0.659 ms
64 bytes from 192.168.10.1: icmp_seq=7 ttl=64 time=0.553 ms
^C
--- 192.168.10.1 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6136ms
rtt min/avg/max/mdev = 0.371/0.626/0.973/0.182 ms

~# ethtool nic0
Settings for nic0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  100baseT/Half
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 100Mb/s
        Duplex: Half
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        MDI-X: off (auto)
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes
Not sure if it'll help but I have 2 VLANs. The proxmox nodes I have the VLANs is 10.x subnet and default is on another one. I am able to ping and SSH to all the other nodes in the 10.x subnet but I can't SSH or access the web page of this particular node only.
 
Last edited:
I ran an SSH connection to the node with debug and it does not seem to respond after prompting for password if I try to connect from a different VLAN.
Code: 
---snip---
debug3: authmethod_lookup password
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
root@192.168.10.102's password:
debug3: send packet: type 50
debug2: we sent a password packet, wait for reply
ssh_dispatch_run_fatal: Connection to 192.168.10.102 port 22: Operation timed out

Whereas, from the same vlan, I can access.
Code: 
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
root@192.168.10.102's password:
debug3: send packet: type 50
debug2: we sent a password packet, wait for reply
debug3: receive packet: type 52
Authenticated to 192.168.10.102 ([192.168.10.102]:22) using "password".
debug1: channel 0: new session [client-session] (inactive timeout: 0)
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Requesting no-more-sessions@openssh.com
debug3: send packet: type 80
debug1: Entering interactive session.

So i tested this theory out and tried to access the web page from same VLAN and I am able to access. Is this an expected behaviour that's happening on proxmox??
Screenshot 2025-11-27 at 2.25.01 PM.png
 
Last edited:
You must log in or register to reply here.
Top Bottom