ProxMox URL is not accessible on the local network.

[bhavyaashok8]

Noob here ..!! I have recently installed ProxMox proxmox-ve_6.4-1. Looks like the installation is successful and it shows the screen with the URL to configure the server. But the URL is not accessible from any system.
Any help is appreciated. I have attached the ip a and cat /etc/hosts output.
Thank you,

 

[bbgeek17]

what are the IP addresses of some of other systems in your network?
Can you ping from other system to PVE and vice-versa?
Can you ping between other systems?
What is the output of "cat /etc/network/interfaces"
What is the "ip r" output from PVE?
Can you ping the gateway?

---

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

 

[bhavyaashok8]

what are the IP addresses of some of other systems in your network?
Can you ping from other system to PVE and vice-versa?
Can you ping between other systems?
What is the output of "cat /etc/network/interfaces"
What is the "ip r" output from PVE?
Can you ping the gateway?

---

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

what are the IP addresses of some of other systems in your network? -> 10.0.0.XX
Can you ping from other system to PVE and vice-versa? -> No I can not.
Can you ping between other systems? -> Yes I can form my Mac to another Linux machine
What is the output of "cat /etc/network/interfaces"

What is the "ip r" output from PVE?

Can you ping the gateway? -> Yes I can

 

[sb-jw]

Did you ping a DNS name or an IP address? Is the /24 network also configured on the other clients?

 

[leesteken]

Did you make sure that the IP 10.0.0.30 is outside of the DHCP range of the gateway? I often read about traffic being blocked (or not router) when it overlaps.

 

[bbgeek17]

Based on the fact that you can ping the gateway/router from PVE, but you cant ping between PVE and your other hosts, I agree with @leesteken - the culprit is likely your "smart" router.
As a test - run the cable directly between PVE and Mac/Linux, confirm proper communication. Put a simple non-managed switch where you can connect your hosts, or, as @leesteken said, try to play with moving IP outside of "protected" range of your router, or research your router config.

---

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

 

[bhavyaashok8]

Did you ping a DNS name or an IP address? Is the /24 network also configured on the other clients?

I Pinged the IP address. And /24 is not configured for other clients. I left that as-is when I was installing ProxMox. Do I have to change it? Thank you

 

[bhavyaashok8]

Did you make sure that the IP 10.0.0.30 is outside of the DHCP range of the gateway? I often read about traffic being blocked (or not router) when it overlaps.

I don't think it is out of the DHCP range of the gateway. Yes, I saw some articles too.
Thank you

 

[bhavyaashok8]

Based on the fact that you can ping the gateway/router from PVE, but you cant ping between PVE and your other hosts, I agree with @leesteken - the culprit is likely your "smart" router.
As a test - run the cable directly between PVE and Mac/Linux, confirm proper communication. Put a simple non-managed switch where you can connect your hosts, or, as @leesteken said, try to play with moving IP outside of "protected" range of your router, or research your router config.

---

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

Apologies, I can ping the router from other systems, not from PVE. Yes, let me try to run the cable directly or let me check the IP if it is in the protected range.
Thanks you.

 

[bbgeek17]

And /24 is not configured for other clients.

What is configured on other clients? There has to be some subnet, configured or implied.
Execute "ip a" on your working Linux host.

---

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

 

[BobhWasatch]

I Pinged the IP address. And /24 is not configured for other clients. I left that as-is when I was installing ProxMox. Do I have to change it? Thank you

What do you mean by this? Are the other clients configured as /24 or with a 255.255.255.0 netmask? Because if they are not the default for a 10 network would be /8 or 255.0.0.0. Having different netmasks on PVE vs the other machines could definitely cause the symptoms you are seeing.

ETA: I see @bbgeek17 was posting the same thing at the same time

 

[bhavyaashok8]

What do you mean by this? Are the other clients configured as /24 or with a 255.255.255.0 netmask? Because if they are not the default for a 10 network would be /8 or 255.0.0.0. Having different netmasks on PVE vs the other machines could definitely cause the symptoms you are seeing.

ETA: I see @bbgeek17 was posting the same thing at the same time

Looks like other systems are configured with a 255.255.255.0 netmask. I do not have any other system that is hardwired through the ethernet cable so all the devices are over the wifi.

 

[bbgeek17]

with a 255.255.255.0 netmask

is another way to write down /24

I do not have any other system that is hardwired through the ethernet cable so all the devices are over the wifi.

again, more than likely the configuration of your router expects something different on LAN interface vs Wifi.
Keep working on it, you should be able to ping the router first and foremost. Go over router settings, perhaps its a different subnet than you think.

---

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

 

[bhavyaashok8]

What is configured on other clients? There has to be some subnet, configured or implied.
Execute "ip a" on your working Linux host.

---

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

root@nivya:~# 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
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 4c:72:b9:9d:c0:53 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.187/24 brd 10.0.0.255 scope global dynamic noprefixroute enp3s0
       valid_lft 172715sec preferred_lft 172715sec
    inet6 2601:205:c300:48e0::e46a/128 scope global dynamic noprefixroute
       valid_lft 213534sec preferred_lft 213534sec
    inet6 2601:205:c300:48e0:2b2d:a3:83c9:a9ce/64 scope global temporary dynamic
       valid_lft 213629sec preferred_lft 85865sec
    inet6 2601:205:c300:48e0:60f0:d78f:1251:184f/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 213629sec preferred_lft 213629sec
    inet6 fe80::531e:b73:638a:805d/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

Here it is from a working Linux host.
Thank you.

 

[bhavyaashok8]

is another way to write down /24

again, more than likely the configuration of your router expects something different on LAN interface vs Wifi.
Keep working on it, you should be able to ping the router first and foremost. Go over router settings, perhaps its a different subnet than you think.

---

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

Sure, sounds good. Let me work on that. Looks like in the router settings netmask is 255.255.255.0 is set.
Thank you So much.