Unable to access Self-Hosted 3CX via public URL (No access to building firewall)

[Samuel.v2]

Hi everyone,


I have deployed a self-hosted 3CX instance in our office, which is located in a building where we do not have administrative access to the modem/firewall.


The PBX is working internally, and the mobile app registers successfully using the QR code because it contains the local IP address of the 3CX server. However, I am unable to access the 3CX web interface using the public URL/FQDN, as traffic does not appear to be reaching the server through the building's firewall.


The Windows desktop client seems to require access through the public address/FQDN and therefore cannot connect, while the mobile app continues to work on the local network.


Is there a recommended way to make the Windows client work in this type of environment?


Any advice would be appreciated.

 

[bitn2]

That won't work—and can't work—that way. A cloud-based system makes more sense for your scenario.

 

[Samuel.v2]

I have a gateway in the office that I need to use. If I move 3CX to the cloud, how would the gateway connect without access to the building's firewall? Wouldn't the required ports still need to be opened for the gateway to communicate with the PBX?

 

[bitn2]

Than you need access to the firewall anyway...

 

[SteveITS]

A working FQDN is required. You will need https://www.3cx.com/docs/creating-fqdn-split-dns/.