Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. FOP2 One Moment Please

FOP2 One Moment Please

Scheduled Pinned Locked Moved Support
2 Posts 1 Posters 356 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D
    D
    dashrender
    wrote on last edited by
    #1

    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).

    1 Reply Last reply
    0
    • D
      D
      dashrender
      wrote on last edited by
      #2

      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.

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      Powered by NodeBB Contributors
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups