New installation of Proxmox VE - no access to GUI

Q

Quantsch

New Member
Feb 9, 2023
6
1
3
Hi everyone,
I'm pretty new to whole topic of Proxmox. I installed it rather succesful on a Fujitsu Futro S740.
After the installation I fail to connect to the Proxmox Server via GUI.
From Proxmox I'm able to ping my gateway as well as my client (running win11). The other way around I always get time out or ERR_CONNECTION_TIMED_OUT via my browser. Same result if I want to access https://***ipofmyProxmox***:8006
Proxmox VE has a static IP.
ip a prompts:
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
inet127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether ***MAC address*** brd ff:ff:ff:ff:ff:ff
altname enp2s0
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ***MAC address*** brd ff:ff:ff:ff:ff:ff
inet ***ipofmyProxmox***/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 ***inet6adress***/64 scope link
valid_lft forever preferred_lft forever
Click to expand...

cat /etc/network/interfaces prompts:
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
address ***ipofmyProxmox***/24
gateway ***gatewayIP***
bridge-ports eno1
bridge-stp off
bridge-fd 0
Click to expand...
The results are obtained independently if my (Windows-) Firewall is switched on or of.
Do I make any obvious rookie mistake? or does anyone know what issue I may have here?
Looking forward to your feedback and thanks in advance for help.
 
Do you mean my ip addresses? I just wanted to be careful with publishing them. Do you need them or is other information missing?
 
@bbgeek17 thanks for your quick response and here are my "unfiltered" information:

pve 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
inet127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 4c:52:62:ba:04:89 brd ff:ff:ff:ff:ff:ff
altname enp2s0
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 4c:52:62:ba:04:89 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.87/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::4e52:62ff:feba:489/64 scope link
valid_lft forever preferred_lft forever
Click to expand...
pve ip route:
default via 192.168.0.1 dev vmbr0 proto kernel onlink
192.168.0.0/24 dev vmbr0 proto kernel scope link src 192.168.0.87
Click to expand...
pve arp -n:
-bash: arp: command not found
Click to expand...
Win: ipconfig /all
Windows-IP-Konfiguration

Hostname . . . . . . . . . . . . : Kianze4
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Hybrid
IP-Routing aktiviert . . . . . . : Nein
WINS-Proxy aktiviert . . . . . . : Nein

Unbekannter Adapter Wintun:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : PolarBear Tunnel
Physische Adresse . . . . . . . . :
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja

Unbekannter Adapter LAN-Verbindung:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Phantom TAP-Windows Adapter V9
Physische Adresse . . . . . . . . : 00-FF-FD-64-B9-08
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 3:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
Physische Adresse . . . . . . . . : 14-18-C3-87-A6-1E
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 12:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #4
Physische Adresse . . . . . . . . : 16-18-C3-87-A6-1D
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter Ethernet 5:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Lenovo USB Ethernet
Physische Adresse . . . . . . . . : 08-3A-88-63-16-CD
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IPv6-Adresse. . . . . . . . . . . : 2a02:8070:c687:cde0::1a74(Bevorzugt)
Lease erhalten. . . . . . . . . . : Donnerstag, 9. Februar 2023 08:08:08
Lease läuft ab. . . . . . . . . . : Freitag, 10. Februar 2023 08:00:39
IPv6-Adresse. . . . . . . . . . . : 2a02:8070:c687:cde0:f907:fe30:85ec:3ba2(Bevorzugt)
Temporäre IPv6-Adresse. . . . . . : 2a02:8070:c687:cde0:b5c7:da85:9b06:9c2b(Bevorzugt)
Verbindungslokale IPv6-Adresse . : fe80::2c98:eb76:9771:980d%20(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.0.98(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Lease erhalten. . . . . . . . . . : Donnerstag, 9. Februar 2023 08:08:06
Lease läuft ab. . . . . . . . . . : Donnerstag, 16. Februar 2023 08:08:06
Standardgateway . . . . . . . . . : fe80::eea9:40ff:fe75:6906%20
192.168.0.1
DHCP-Server . . . . . . . . . . . : 192.168.0.1
DHCPv6-IAID . . . . . . . . . . . : 721959560
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-29-4C-02-4A-14-18-C3-87-A6-1D
DNS-Server . . . . . . . . . . . : 2a02:8070:c687:cde0:eea9:40ff:fe75:6906
192.168.0.1
NetBIOS über TCP/IP . . . . . . . : Aktiviert

Drahtlos-LAN-Adapter WLAN:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW)
Physische Adresse . . . . . . . . : 14-18-C3-87-A6-1D
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter Ethernet 6:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : TunnelBear Adapter V9
Physische Adresse . . . . . . . . : 00-FF-6B-9C-3E-AA
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter Bluetooth-Netzwerkverbindung:

Medienstatus. . . . . . . . . . . : Medium getrennt
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physische Adresse . . . . . . . . : 14-18-C3-87-A6-21
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
Click to expand...
Win: arp -n:
gives just an overview of options for command "arp" - which one is relevant?
 
on windows :
arp -a|findstr 04:89
arp -a|findstr 192.168.0.87

So you can ping from PVE to Windows/router.
I assume you can ping from Windows to router?
But you cant ping from Windows to PVE?
Does the router show PVE IP and corresponding MAC in active connections? Is possible you have a duplicate?
Does this provide html? PVE: curl -sk https://192.168.0.87:8006
From windows: powershell -command "Test-NetConnection -ComputerName 192.168.0.87 -Port 22"
From windows: powershell -command "Test-NetConnection -ComputerName 192.168.0.87 -Port 8006"

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
bbgeek17 said:
on windows :
arp -a|findstr 04:89
Click to expand...
gives me no output
bbgeek17 said:
arp -a|findstr 192.168.0.87
Click to expand...
192.168.0.87 a0-72-2c-cc-77-32 dynamisch
bbgeek17 said:
So you can ping from PVE to Windows/router.
Click to expand...
yes to my windows laptop as well as to my router
bbgeek17 said:
I assume you can ping from Windows to router?
Click to expand...
yes
bbgeek17 said:
But you cant ping from Windows to PVE?
Click to expand...
exactly - always timed out
bbgeek17 said:
Does the router show PVE IP and corresponding MAC in active connections? Is possible you have a duplicate?
Click to expand...
1675974885845.png
I can't see a duplicate yet - have to check it.


bbgeek17 said:
Does this provide html? PVE: curl -sk https://192.168.0.87:8006
Click to expand...
Yes
bbgeek17 said:
From windows: powershell> Test-NetConnection -ComputerName 192.168.0.87 -Port 22
Click to expand...
PS C:\WINDOWS\system32> Test-NetConnection -ComputerName 192.168.0.87 -Port 22
WARNUNG: TCP connect to (192.168.0.87 : 22) failed
WARNUNG: Ping to 192.168.0.87 failed with status: TimedOut


ComputerName : 192.168.0.87
RemoteAddress : 192.168.0.87
RemotePort : 22
InterfaceAlias : Ethernet 5
SourceAddress : 192.168.0.98
PingSucceeded : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : False
Click to expand...

bbgeek17 said:
From windows: powershell> Test-NetConnection -ComputerName 192.168.0.87 -Port 8006
Click to expand...
S C:\WINDOWS\system32> Test-NetConnection -ComputerName 192.168.0.87 -Port 8006
WARNUNG: TCP connect to (192.168.0.87 : 8006) failed
WARNUNG: Ping to 192.168.0.87 failed with status: TimedOut


ComputerName : 192.168.0.87
RemoteAddress : 192.168.0.87
RemotePort : 8006
InterfaceAlias : Ethernet 5
SourceAddress : 192.168.0.98
PingSucceeded : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : False
Click to expand...
 
The output form PVE shows that you have this combination of IP/MAC:
link/ether 4c:52:62:ba:04:89 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.87/24 scope global vmbr0

The output from windows says that no such MAC exists in windows ARP cache, and 192.168.0.87 matches to a0-72-2c-cc-77-32.

Obviously there is a disconnect here, you will have to figure out what it is. I'd start with using a different IP for PVE.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
You're completely right - it is strange and I have somehow to fix it. I'll update here as soon as I've found out the reason why...
Your feedback is much appreciated! Thank you
 
bbgeek17 said:
The output form PVE shows that you have this combination of IP/MAC:
link/ether 4c:52:62:ba:04:89 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.87/24 scope global vmbr0

The output from windows says that no such MAC exists in windows ARP cache, and 192.168.0.87 matches to a0-72-2c-cc-77-32.

Obviously there is a disconnect here, you will have to figure out what it is. I'd start with using a different IP for PVE.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Dear @bbgeek17

thanks again for your prompt support - after reinstallation of Proxmox and new IP addresses it works without issue.
As always the weakest link in the chain is in front of the computer ;-)
 
  • Like
Reactions: bbgeek17
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom