The web Interface not loading up after installation of proxmox 8.2.

[Miko888]

I had an issue with upgrading from 7 to 8 so I decided I would just do a fresh install, sacrificing all my vms. I have done 3 proxmox 8.2 installs and I still can't get the web interface to load. I have done "systemctl status pveproxy" like I saw on other support posts as shown below and it seems to be fine. What can I do to troubleshoot this? My knowledge of Linux isn't the greatest and there isn't a visible error but I don't know other necessary commands to check for errors so I am probably wrong.

 

[bbgeek17]

Hi @Miko888 ,

There are many threads that provide suggested next steps. The one you found probably had more than "pveproxy" status. That said, here is a list of standard questions you should answer:

• 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://LAN_IP:8006" when run directly from PVE (over SSH or physical console?)

Good luck

PS you may also want to watch some Proxmox YouTube videos where the authors walk you step by step through every imaginable variation.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Miko888]

IP of the PVE server: 192.168.1.180:8006 I think, I just used the default one because after the third install, I gave up on a custom one just in case it was that which was the problem.
IP of my workstation: 192.168.1.178 probably
IP of my gateway: I don't know I left the default one and didn't change it.
Can I ping the PVE server: no

Can I ssh into PVE server: no

ip a:

ipconfig /all:
C:\Users\michk>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-GTM0JT4
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : tail2eb4f.ts.net
lan

Unknown adapter Tailscale:

Connection-specific DNS Suffix . : tail2eb4f.ts.net
Description . . . . . . . . . . . : Tailscale Tunnel
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fd7a:115c:a1e0:ab12:4843:cd96:624e:cd8e(Preferred)
Link-local IPv6 Address . . . . . : fe80::d8ff:5060:f230:9168%9(Preferred)
IPv4 Address. . . . . . . . . . . : 100.78.205.142(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Connection-specific DNS Suffix Search List :
tail2eb4f.ts.net

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Killer E2400 Gigabit Ethernet Controller
Physical Address. . . . . . . . . : B8-85-84-AF-48-A8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fdf3:e7a1:80c5:cc63:4ddf:4847:51a6:c9ab(Preferred)
Temporary IPv6 Address. . . . . . : fdf3:e7a1:80c5:cc63:e536:4cb8:907f:aa16(Preferred)
Link-local IPv6 Address . . . . . : fe80::a119:da5f:139f:c5df%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.178(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 22 September 2024 20:12:13
Lease Expires . . . . . . . . . . : 24 September 2024 22:50:21
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 163087748
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-EC-49-62-B8-85-84-AF-48-A8
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : UsbNcm Host Device
Physical Address. . . . . . . . . : 24-74-F7-84-FD-C4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ef70:1d3f:d9b:8a47%14(Preferred)
IPv4 Address. . . . . . . . . . . : 172.27.134.52(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 23 September 2024 17:58:48
Lease Expires . . . . . . . . . . : 03 October 2024 17:58:48
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 172.27.134.51
DHCPv6 IAID . . . . . . . . . . . : 186938615
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-EC-49-62-B8-85-84-AF-48-A8
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wi-Fi:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Qualcomm QCA9377 802.11ac Wireless Adapter
Physical Address. . . . . . . . . : 48-5F-99-68-6D-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 5:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #9
Physical Address. . . . . . . . . : 4A-5F-99-68-6D-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #10
Physical Address. . . . . . . . . : 5A-5F-99-68-6D-B9
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) #3
Physical Address. . . . . . . . . : 48-5F-99-68-6D-BA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:14be:4c8:28a1:2fb0:a3e7:68d3(Preferred)
Link-local IPv6 Address . . . . . : fe80::28a1:2fb0:a3e7:68d3%19(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 268435456
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-EC-49-62-B8-85-84-AF-48-A8
NetBIOS over Tcpip. . . . . . . . : Disabled
curl -k https://127.0.0.1:8006 through physical console:

curl -k https://LAN_IP:8006 through physical console:

 

[bbgeek17]

Proxmox appears to be fine: the interface is up, services are responding.

Based on what you provided, it appears that your network is "broken". Whether its misconfigured or "broken" on purpose only you can figure out.
The usual suspects are:
- your router that may be blocking "rogue" IPs in the DHCP range.
- your tailscale tunnel that may blocking traffic
- some cabling issue, i.e. cable is plugged into wrong jack

Start with the basics. Disable all VPN services. Connect two PCs via direct cable. Test outbound connectivity from PVE. I.e. ping from PVE console 192.168.1.1, check ARP table on each side. Etc.

So far nothing points to an issue in PVE Installation or Configuration.

Good luck

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Miko888]

I found an old laptop with a broken screen in my attic that I haven't touched in years and installed proxmox on it and I'm having the same issue with not being able to access the web GUI. On the pc that I tried to fix before, I tried downgrading to proxmox 7.4 which was working before I wiped it and installed 8.2 but it still had the same issue that's why I switched devices and the web GUI issue is still on this laptop. I connected the laptop to the PC and tried pinging 192.168.1.1 but as shown above, it's unsuccessful.