Proxmox VE 9: Can not access WebGUI after reboot, until first ssh connect

P

peter_zh

New Member
Oct 2, 2025
2
0
1
Hello,

There are several threads here reporting problems accessing the GUI, but I haven't found anything that matches my situation.

Initial situation:
  • Fresh installation of VE 9
  • Update to latest versions (non-subscription)
  • Reboot
Problem:
  • After rebooting, the WebGUI is no longer accessible, no matter how long I wait...
  • As soon as I try to access the server from my notebook using SSH, I suddenly get a response from the GUI.
  • I don't even have to log in; all I have to do is call
    Code: 
    ssh root@192.168.xxx.xxx
    and as soon as the login prompt appears in the terminal, my GUI responds and everything works fine
System information:
  • Tried two several machines from different vendors: always same result:
    • 12 x Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz (1 Socket) / 24 GB RAM /
    • 8 x Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz (1 Socket) / 32 GB RAM /
  • Kernel Version: Linux 6.14.11-3-pve (2025-09-22T10:13Z)
  • PVE Manager: 9.0.10/deb1ca707ec72a89

Maybe interesting to know:
  • My friend ChatGPT assumes pveproxy service starts bevor the network is available (I'll try the suggest fix in the next days)
  • I started the installation on a IP address that I did receive by DHCP, but switched to a different (fixed) IP during the installation process. Maybe there are some issues with this?
 
Hi @peter_zh , welcome to the forum.

You’re correct that your report doesn’t match anything posted here recently. It seems unique, which strongly suggests it’s specific to your environment.

The troubleshooting steps I’d recommend are:
  • From the physical console, check your IP configuration before applying "ssh fix" : "ip a" and "ip route". Install "arp" if not present and list mac table.
  • From the physical console, verify that the UI is responding: curl -k https://localhost:8006.
  • Replace localhost with your static LAN IP and see if you get a response.
  • From the physical console, confirm you can ping other hosts. Does that restore your ability to access the UI from another host?
  • From an external host, check that your PVE node is pingable. Does that enable access to the UI?
  • Since this is a new install, are you applying any custom scripts that modify firewall rules? Or is this a completely vanilla install?
  • Is the network device in between “smart” (managed switch, firewall, etc.)? If so, can you bypass it and reproduce the issue by connecting a laptop directly to the PVE host?
In short: continue with methodical network-related troubleshooting until you isolate the point of failure.

Cheers

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
From the physical console, check your IP configuration before applying "ssh fix" : "ip a" and "ip route". Install "arp" if not present and list mac table.
Click to expand...
Everything looks fine

bbgeek17 said:
From the physical console, verify that the UI is responding: curl -k https://localhost:8006.
Click to expand...
Yes, I do get a reply

bbgeek17 said:
Replace localhost with your static LAN IP and see if you get a response.
Click to expand...
Works also fine
bbgeek17 said:
From the physical console, confirm you can ping other hosts. Does that restore your ability to access the UI from another host?
Click to expand...
Yes, I can confirm that I can bin my internet router, using its hostname
No, the GUI still does not connect from my client to the Proxmox VE host
bbgeek17 said:
Since this is a new install, are you applying any custom scripts that modify firewall rules? Or is this a completely vanilla install?
Click to expand...
complete vanilla. I just plugged in the usb stick and installed

bbgeek17 said:
Is the network device in between “smart” (managed switch, firewall, etc.)? If so, can you bypass it and reproduce the issue by connecting a laptop directly to the PVE host?
Click to expand...
No, nothing special. It is my private home environment.
Interestingly, when I do connect my client directly to the PVE host, everything works fine.
 
You must log in or register to reply here.
Top Bottom