Cannot access web GUI

R

roostertail

New Member
Jan 30, 2025
8
1
1
Hello,

I recently installed PVE and am having no luck connecting to the web GUI

When I ping 1.1.1.1 from the PVE cli, it returns
Code: 
Destination Host Unreachable

My /etc/network/interfaces file reads

Code: 
auto lo
iface lo inet looback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.100.2/24
    gateway 192.168.100.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0
    
    
source /etc/network/interfaces.d/*

I am running PVE 8.3.0 on a HP Elitedesk 800 g3 35w. I have it connected through ethernet to a stock AT&T BGW320-505 router

Thank you for help
 
@bbgeek17

I'm on a Windows 10 laptop and working through an Ubuntu 22.04 WSL terminal. I have a wifi connection and also an ethernet connection to my LAN

I got these results:

Code: 
$ hostname -I
192.168.1.226 192.168.149.1 192.168.190.1 100.64.100.6


Code: 
ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.226  netmask 255.255.255.0  broadcast 192.168.1.255
        ether 08:97:98:6e:aa:88  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.149.1  netmask 255.255.255.0  broadcast 192.168.149.255
        ether 00:50:56:c0:00:01  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.190.1  netmask 255.255.255.0  broadcast 192.168.190.255
        ether 00:50:56:c0:00:08  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 65535
        inet 100.64.100.6  netmask 255.255.255.255  broadcast 100.64.100.6
        inet6 fe80::86d6:4f39:c6c5:29e2  prefixlen 64  scopeid 0xfd<compat,link,site,host>
        ether 00:00:00:00:00:00  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 1500
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0xfe<compat,link,site,host>
        loop  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


Code: 
$ ip addr show
17: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 group default qlen 1
    link/ether 08:97:98:6e:aa:88
    inet 192.168.1.226/24 brd 192.168.1.255 scope global dynamic
       valid_lft 84868sec preferred_lft 84868sec
24: eth1: <> mtu 1500 group default qlen 1
    link/ether 84:fd:d1:7e:97:c0
    inet 169.254.1.241/16 brd 169.254.255.255 scope global dynamic
       valid_lft forever preferred_lft forever
18: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 group default qlen 1
    link/ether 00:50:56:c0:00:01
    inet 192.168.149.1/24 brd 192.168.149.255 scope global dynamic
       valid_lft 1169sec preferred_lft 1169sec
15: eth3: <BROADCAST,MULTICAST,UP> mtu 1500 group default qlen 1
    link/ether 00:50:56:c0:00:08
    inet 192.168.190.1/24 brd 192.168.190.255 scope global dynamic
       valid_lft 1167sec preferred_lft 1167sec
1: lo: <LOOPBACK,UP> mtu 1500 group default qlen 1
    link/loopback 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope global dynamic
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host dynamic
       valid_lft forever preferred_lft forever
20: eth4: <> mtu 1500 group default qlen 1
    link/ether 00:ff:c2:23:4c:1d
    inet 169.254.242.161/16 brd 169.254.255.255 scope global dynamic
       valid_lft forever preferred_lft forever
3: eth5: <BROADCAST,MULTICAST,UP> mtu 65535 group default qlen 1
    link/ether 00:00:00:00:00:00
    inet 100.64.100.6/32 brd 100.64.100.6 scope global dynamic
       valid_lft forever preferred_lft forever
    inet6 fe80::86d6:4f39:c6c5:29e2/64 scope link dynamic
       valid_lft forever preferred_lft forever
10: wifi0: <> mtu 1500 group default qlen 1
    link/ieee802.11 84:fd:d1:7e:97:bc
    inet 169.254.244.65/16 brd 169.254.255.255 scope global dynamic
       valid_lft forever preferred_lft forever
14: wifi1: <> mtu 1500 group default qlen 1
    link/ieee802.11 84:fd:d1:7e:97:bd
    inet 169.254.231.88/16 brd 169.254.255.255 scope global dynamic
       valid_lft forever preferred_lft forever
6: wifi2: <> mtu 1500 group default qlen 1
    link/ieee802.11 86:fd:d1:7e:97:bc
    inet 169.254.177.115/16 brd 169.254.255.255 scope global dynamic
       valid_lft forever preferred_lft forever
 
Last edited:
You seem to have a somewhat complex networking. Unfortunately you did not label where each snippet came from or what it refers to.

However, nowhere in your output there are any IPs from 192.168.100 network. The most logical conclusion is that you did not place PVE on the network subnet that is appropriate for your home.

Perhaps, you used default values?

This video may be able to help: https://www.youtube.com/watch?v=TA0gZs0X_7o

Cheers

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
You seem to have a somewhat complex networking. Unfortunately you did not label where each snippet came from or what it refers to.

However, nowhere in your output there are any IPs from 192.168.100 network. The most logical conclusion is that you did not place PVE on the network subnet that is appropriate for your home.

Perhaps, you used default values?

This video may be able to help: https://www.youtube.com/watch?v=TA0gZs0X_7o

Cheers

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
This is from my AT&T management interface:

1305dbb2e3285628d9d011bef7997a18.png
 
roostertail said:
This is from my AT&T management interface:
Click to expand...
This additional information does not help to clarify things. In fact, it makes the situation even more complicated.

The screenshot implies that although you set the PVE to static IP, you also have an active DHCP server where the range starts at the same IP address. Forum members reported that some "smart" routers/DHCP block connectivity from devices that use static IPs which overlap with DHCP range.

PVE is based on Debian Linux. The TCP/IP stack involved is used by billions of PCs/servers. Your PVE network configuration is very simple and straightforward. Figure out the correct IP/Subnet for your environment and ensure your physical connectivity is sound (the link is up).
The fact that you can not ping the gateway is very telling. Perhaps run tcpdump and monitor the ARP requests to understand where your connection fits.

Cheers

I misread...
Your PVE is 192.168.1 , the DHCP screenshot is 192.168.100

The screenshot still does not help.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
bbgeek17 said:
You seem to have a somewhat complex networking. Unfortunately you did not label where each snippet came from or what it refers to.

However, nowhere in your output there are any IPs from 192.168.100 network. The most logical conclusion is that you did not place PVE on the network subnet that is appropriate for your home.

Perhaps, you used default values?

This video may be able to help: https://www.youtube.com/watch?v=TA0gZs0X_7o

Cheers

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Resolved! Changed network to 192.168.1.5
 
You must log in or register to reply here.
Top Bottom