Public IP issue

[hussein abdi]

Dear sir,

I have an issue i manually configured the public IP on Proxmox while installing, and now I am not able to login using the public IP.

my NIC cards are as below.

management interface: eno1np0
hostname: hussein.local
ip add: public ip
gateway: publi
dns: google ip

after successful install it shows the login IP as my public ip: 8006 but i can not reach it or ping the IP

when i login to the Proxmox via commandline and run commanf --- ip a

it shows no IP for the interfaces
- eno1np0
- eno99
- eno2np1
-eno59s0f1

But it shows my Public IP that i manually added at Install as

- vmbr0


Please assist with this Thank you let me know if you need more clarification

 

[bbgeek17]

Where are you trying to access this IP from? Is your client on internal LAN or are you trying to access it over the internet?
Is this installation at home or in a data center?
Can you ping to your gateway from PVE? Can you actually access the DNS? Are there firewalls in front of PVE?

---

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

 

[hussein abdi]

Hi BBgeek17,

Am trying to access it from my internal network which is a different ISP from the NEtwork of the Proxmox that i gave public IP.

i can not ping google nor the public IP gateway from the Proxmox CLI
no firewalls connected directly to ISP.

 

[bbgeek17]

Am trying to access it from my internal network which is a different ISP from the NEtwork of the Proxmox that i gave public IP.

So, to clarify, your workstation is on a non-routable subnet, ie 192.168.x.y, which then uses a router with Public IP of w.x.y.z , and then uses Internet infrastructure to potentially reach the PVE with a public IP of a.b.c.d ?

i can not ping google nor the public IP gateway from the Proxmox CLI

If you cant access out from PVE, then you need to review all the network information again. At the very least you must be able to ping your gateway. Until this is resolved, there is no point in troubleshooting client connectivity.
If the IP and subnet are properly set, there is nothing else that you need to change in PVE to ping the GW.

---

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

 

[hussein abdi]

So, to clarify, your workstation is on a non-routable subnet, ie 192.168.x.y, which then uses a router with Public IP of w.x.y.z , and then uses Internet infrastructure to potentially reach the PVE with a public IP of a.b.c.d ?

yes

 

[hussein abdi]

f you cant access out from PVE, then you need to review all the network information again. At the very least you must be able to ping your gateway. Until this is resolved, there is no point in troubleshooting client connectivity.
If the IP and subnet are properly set, there is nothing else that you need to change in PVE to ping the GW.

With the PVE server i connected it to a hub which inturn connects to the ISP Router which will only work with Public IP after assigning Manualy not DHCP.

 

[bbgeek17]

With the PVE server i connected it to a hub which inturn connects to the ISP Router which will only work with Public IP after assigning Manualy not DHCP.

Well, it doesnt work. There could be many reasons - none are Proxmox specific. Solutions can range from MAC address spoofing or registration, to bad cable. You need to do basic network troubleshooting. Try to reduce the number of variables, ie "hub". Beyond that, the next step is to contact your ISP so they can sanity check your configuration (which only you and them know) and assist you in troubleshooting.

Good luck

---

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