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. Chrome Extension on FreePBX 14 not working

Chrome Extension on FreePBX 14 not working

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 200 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.
  • J
    J
    Joseph.G
    wrote on last edited by
    #1

    Hello, I installed the latest version of FOP2 today on FreePBX 14.0.13.4 with a basic white label license. Admin GUI and user/extension logins work both on Chrome 76.0.3809.87 and Firefox and I can manage calls with any given user/extension.
    Then I installed FOP2 Chrome extension. I used the same URL as when using for fop2 extensions, port 4445 and same extension:password but it doesn't connect (Unable to connect to server).
    Checked admin GUI and disableWebSocket is disabled. I haven't run the scripts to synch DND and CF yet. I'm using CFS firewall and opened both 4445 and 5038 in addition to http and https ports for IP addresses that need to run FOP2 on their browsers. Other than that all and everything else is working fine. Please advise. Thank you, Joseph

    1 Reply Last reply
    0
    • J
      J
      jerryriggin
      wrote on last edited by
      #2

      Is FreePBX firewall or fail2ban running? What OS are you running chrome on?

      Also, if you are running FOP2 the only use I am aware of for the Chrome plugin is click-to-dial. Is that why you are installing it?

      1 Reply Last reply
      0
      • J
        J
        Joseph.G
        wrote on last edited by
        #3

        Just found out that the URL should be plain domain name or IP address without HTTPS:// and leading /fop2. Now it works for me.

        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