<![CDATA[FOP2 One Moment Please]]>I have a relatively new FreePBX setup with FOP2 on it.
The PBX is hosted by Vultr in Chicago, no Vultr firewall enabled
I'm able to connect to FOP2 from my Cox ISP connection, but others on Verizon and Centurylink can't.

I've changed the default port to 14445 to no avail.

I've whitelisted the Testing parties IPs so they aren't getting blocked (they are get the One Moment Please page, and a count up, but it never connects, and eventually reads System is not available right now).

]]>https://forum.fop2.com/topic/2813/fop2-one-moment-pleaseRSS for NodeTue, 27 Oct 2026 17:42:14 GMTMon, 06 Apr 2020 21:27:34 GMT60<![CDATA[Reply to FOP2 One Moment Please on Tue, 07 Apr 2020 12:50:40 GMT]]>The issue was discovered by @JaredBusch (thanks!)
FreePBX has several types of allowed IPs under Connectivity > firewall >Networks
When you more or less want to white list an IP address, you mark them as either Trusted or Local.
Trusted = allow access to anything on the server, any port, no restrictions
Local = allow access to the ports known by FreePBX (connectivity > Firewall > Networks > side hamburger menu > Services - once here you will see the following tabs Services, Extra Services, Custom Services, Blacklist) and marked as Local.

At some point, for an unknown reason when entering IPs into the Networks tab I changed from using Trusted to using Local. My personal IP, along with a support persons were both under Trusted, but everyone else -all those who were failing to connect to FOP2 - were listed as Local.
Because Local seems to be a bit more locked down, I decided to add a custom service to the Custom Services tab for FOP2 4445 TCP and UDP. I then marked it as Local, click the green checkbox to save.

Upon saving that, all users listed as Local in the Networks tab could now access FOP2.

I hope this helps someone else someday.

]]>https://forum.fop2.com/post/11851https://forum.fop2.com/post/11851Tue, 07 Apr 2020 12:50:40 GMT