I have a physical server where I installed Proxmox. The machine has two NICs:
One connected to the public IP (WAN)
One connected to the private IP (LAN)
Inside Proxmox, I created a FreePBX 16 VM and assigned it two network interfaces:
eth0 for the private IP (LAN)
eth1 for the public IP (WAN)
Configuration so far:
Inside the VM I can successfully ping both the private and public IPs.
The FreePBX GUI works fine when accessed via the private IP.
However, the public IP cannot be accessed from outside.
From the Proxmox host itself, I can also ping both IPs, but from an external device (laptop, browser, or phone), only the private IP responds — the public IP does not.
Has anyone encountered this before? Any advice or troubleshooting steps would be much appreciated.
Yes, that’s correct. Our goal is to have the FreePBX VM reachable on both networks:
Private IP (LAN): for internal access within our office network.
Public IP (via eth1): so the FreePBX GUI and SIP services can also be accessed externally.
The idea is to assign both interfaces (private and public) to the FreePBX VM so that we can manage it locally and also allow external connectivity. Right now, only the private IP is reachable from outside, while the public IP isn’t.
In our setup, the FreePBX VM actually has both a private IP (LAN) and a public IP directly assigned (no NAT). The private IP works fine and I can reach the GUI internally, but the public IP isn’t accessible externally even though it’s bound to the VM and responds to ping/curl inside Proxmox. That’s why I was wondering if this is a Proxmox bridge/firewall issue or if I should be handling this differently.