PVE 7.4 installation can't open GUI

Samsly

New Member
Apr 26, 2025
3
0
1
Hi, I reinstalled the PVE to 7.4, after many trys installation successful, however cannot open GUI either via Edge or Chrome. Before the machine had been running PVE 5.4 well in same network system with no such problem.
These days I tried many way to check following previous post mentioned cause. No way can resolve the problem. Even the SSH connection getting worse, now oftens the SSH response hang. P.S. I applied update to PVE 8.4 but problem still.
Here below the copy of status, any advices is appreciated.

root@PVE:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.6.191 PVE.localnet PVE

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

root@PVE:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet dhcp
# address 192.168.6.193/24
# gateway 192.168.6.1
bridge-ports enp1s0
bridge-stp off
bridge-fd 0

iface enp4s0 inet manual

root@PVE:~# systemctl |grep pve
etc-pve.mount loaded active mounted /etc/pve
pve-cluster.service loaded active running The Proxmox VE cluster filesystem
pve-firewall.service loaded active running Proxmox VE firewall
pve-guests.service loaded active exited PVE guests
pve-ha-crm.service loaded active running PVE Cluster HA Resource Manager Daemon
pve-ha-lrm.service loaded active running PVE Local HA Resource Manager Daemon
pve-lxc-syscalld.service loaded active running Proxmox VE LXC Syscall Daemon
pve-query-machine-capabilities.service loaded active exited PVE Query Machine Capabilities
pvebanner.service loaded active exited Proxmox VE Login Banner
pvedaemon.service loaded active running PVE API Daemon
pvefw-logger.service loaded active running Proxmox VE firewall logger
pvenetcommit.service loaded active exited Commit Proxmox VE network changes
pveproxy.service loaded active running PVE API Proxy Server
pvescheduler.service loaded active running Proxmox VE scheduler
pvestatd.service loaded active running PVE Status Daemon
dev-pve-swap.swap loaded active active /dev/pve/swap
pve-storage.target loaded active active PVE Storage Target
pve-daily-update.timer loaded active waiting Daily PVE download activities

root@PVE:~# ss -antlp|grep 8006
LISTEN 0 4096 0.0.0.0:8006 0.0.0.0:* users:(("pveproxy worker",pid=916618,fd=6),("pveproxy worker",pid=916617,fd=6),("pveproxy worker",pid=916616,fd=6),("pveproxy",pid=1006,fd=6))

root@PVE:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: ena>
Active: active (running) since Mon 2025-04-21 23:23:19 CST; 4 days ago
Main PID: 1006 (pveproxy)
Tasks: 4 (limit: 9325)
Memory: 178.9M
CPU: 1min 58.119s
CGroup: /system.slice/pveproxy.service
├─ 1006 pveproxy
├─916616 "pveproxy worker"
├─916617 "pveproxy worker"
└─916618 "pveproxy worker"

Apr 26 00:00:25 PVE pveproxy[1006]: starting 3 worker(s)
Apr 26 00:00:25 PVE pveproxy[1006]: worker 916616 started
Apr 26 00:00:25 PVE pveproxy[1006]: worker 916617 started
Apr 26 00:00:25 PVE pveproxy[1006]: worker 916618 started
Apr 26 00:00:30 PVE pveproxy[234404]: worker exit
Apr 26 00:00:30 PVE pveproxy[234402]: worker exit
Apr 26 00:00:30 PVE pveproxy[234403]: worker exit
Apr 26 00:00:30 PVE pveproxy[1006]: worker 234402 finished
Apr 26 00:00:30 PVE pveproxy[1006]: worker 234403 finished
Apr 26 00:00:30 PVE pveproxy[1006]: worker 234404 finished

root@PVE:~# systemctl status pvedaemon
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; preset: en>
Active: active (running) since Mon 2025-04-21 23:23:14 CST; 4 days ago
Main PID: 993 (pvedaemon)
Tasks: 4 (limit: 9325)
Memory: 184.3M
CPU: 1min 21.817s
CGroup: /system.slice/pvedaemon.service
├─993 pvedaemon
├─994 "pvedaemon worker"
├─995 "pvedaemon worker"
└─996 "pvedaemon worker"

Apr 21 23:23:09 PVE systemd[1]: Starting pvedaemon.service - PVE API Daemon...
Apr 21 23:23:14 PVE pvedaemon[993]: starting server
Apr 21 23:23:14 PVE pvedaemon[993]: starting 3 worker(s)
Apr 21 23:23:14 PVE pvedaemon[993]: worker 994 started
Apr 21 23:23:14 PVE pvedaemon[993]: worker 995 started
Apr 21 23:23:14 PVE pvedaemon[993]: worker 996 started
Apr 21 23:23:14 PVE systemd[1]: Started pvedaemon.service - PVE API Daemon.
Apr 21 23:30:15 PVE pvedaemon[995]: <root@pam> successful auth for user 'root@p>
Apr 22 22:39:42 PVE pvedaemon[995]: <root@pam> successful auth for user 'root@p>
lines 1-22/22 (END)


root@PVE:~# 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>PVE - 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=8.4.1" />
<link rel="stylesheet" type="text/css" href="/pwt/css/ext6-pmx.css?ver=v4.3.10-t1744126616" />
<link rel="stylesheet" type="text/css" media="(prefers-color-scheme: dark)" href="/pwt/themes/theme-proxmox-dark.css?ver=v4.3.10-t1744126616" />

<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: 'PVE',
UserName: '',
CSRFPreventionToken: 'null',
ConsentText: ''
};
</script>
<script type="text/javascript" src="/proxmoxlib.js?ver=v4.3.10-t1744126616"></script>
<script type="text/javascript" src="/pve2/js/pvemanagerlib.js?ver=8.4.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>

root@PVE:~# journalctl -f
Apr 26 15:13:48 PVE systemd[1061019]: Reached target sockets.target - Sockets.
Apr 26 15:13:48 PVE systemd[1061019]: Reached target basic.target - Basic System.
Apr 26 15:13:48 PVE systemd[1061019]: Reached target default.target - Main User Target.
Apr 26 15:13:48 PVE systemd[1061019]: Startup finished in 305ms.
Apr 26 15:13:48 PVE systemd[1]: Started user@0.service - User Manager for UID 0.
Apr 26 15:13:48 PVE systemd[1]: Started session-146.scope - Session 146 of User root.
Apr 26 15:13:48 PVE sshd[1060985]: pam_env(sshd:session): deprecated reading of user environment enabled
Apr 26 15:17:01 PVE CRON[1061562]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Apr 26 15:17:01 PVE CRON[1061563]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Apr 26 15:17:01 PVE CRON[1061562]: pam_unix(cron:session): session closed for user root
 
Please upgrade or reinstall with the latest (and supported) PVE 8.4. I don't know what you tried or changes but can only tell you what appears to be wrong with what I see in your post.
root@PVE:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.6.191 PVE.localnet PVE

root@PVE:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet dhcp
# address 192.168.6.193/24
# gateway 192.168.6.1
bridge-ports enp1s0
bridge-stp off
bridge-fd 0

iface enp4s0 inet manual
192.168.6.191 is not the same as 192.168.6.193. Maybe change the first to match the latter? Also make sure the address is static and not in the DHCP range of your router.
You should also not comment out the address and gateway line, as that determines the IP address of Proxmox on that interface.
Make sure to reboot after changing all this. Afterwards, please show the output of ip a and cat /etc/hosts /etc/network/interfaces (in CODE-tags for readability).
 
Hi Leesteken, thanks for the reply. Following your advice, I modified the address firstly. No yet fixed. Here below the code:
Code:
:~# ip a
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: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 10:90:27:e9:e4:8f brd ff:ff:ff:ff:ff:ff
3: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 10:90:27:e9:e4:90 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 10:90:27:e9:e4:8f brd ff:ff:ff:ff:ff:ff
    inet 192.168.6.92/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::1290:27ff:fee9:e48f/64 scope link
       valid_lft forever preferred_lft forever

:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.6.92 PVE.localnet PVE

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.6.92/24
        gateway 192.168.6.1
        bridge-ports enp1s0
        bridge-stp off
        bridge-fd 0

iface enp4s0 inet manual
 
Following your advice, I modified the address firstly. No yet fixed.
Can you successfully ping -c1 192.168.6.1? Did you reserve/statically allocate 192.168.6.92 in router? Does your router have IP address 192.168.6.1? Is 192.168.6.92 outside of the DHCP-range of your router (or at least reserved)? Are you running Proxmox inside another hypervisor (Hyper-V, VirtualBox, VMware ESX(i)/Workstation)?
 
Can you successfully ping -c1 192.168.6.1? Did you reserve/statically allocate 192.168.6.92 in router? Does your router have IP address 192.168.6.1? Is 192.168.6.92 outside of the DHCP-range of your router (or at least reserved)? Are you running Proxmox inside another hypervisor (Hyper-V, VirtualBox, VMware ESX(i)/Workstation)?
Yes ping successfully. IP 192.168.92 is now statically reserved from router (IP: 192.168.6.1) outside DHCP range. PVE runs from bootable disk.

Code:
~# ping -c1 192.168.6.1
PING 192.168.6.1 (192.168.6.1) 56(84) bytes of data.
64 bytes from 192.168.6.1: icmp_seq=1 ttl=64 time=0.250 ms

--- 192.168.6.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.250/0.250/0.250/0.000 ms
 
Last edited: