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. I can ´t connect to FOP2

I can ´t connect to FOP2

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 98 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.
  • L
    L
    laika
    wrote on last edited by
    #1

    I restarted my asterisk server for maintenance (but i have not made any changes) and when i try to login to fop2 ,it say "Connecting to server, attempt number:". In IE and Firefox. I restarted the fop2 service, but the problem persist. What can i check? Thanks in advance
    Regards

    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #2

      My guess is that you have the old FOP(1) started before FOP2, binding to tcp port 4445. That effectively disables FOP2 as it can bind to an already used port. Check if FOP1 is running:

      pgrep op_server

      If the above command returns a number, it means its running. You must stop it:

      /usr/sbin/amportal stop_fop

      and disable it, by editing /etc/amportal.conf, set FOPRUN=false, and be sure you do not have a line with "start_fop" in /etc/rc.d/rc.local

      Best regards,

      1 Reply Last reply
      0
      • L
        L
        laika
        wrote on last edited by
        #3

        That 's right. I had FOP1 running.

        Thanks Nicolás for your quick response

        Regards

        My guess is that you have the old FOP(1) started before FOP2, binding to tcp port 4445. That effectively disables FOP2 as it can bind to an already used port. Check if FOP1 is running:

        pgrep op_server

        If the above command returns a number, it means its running. You must stop it:

        /usr/sbin/amportal stop_fop

        and disable it, by editing /etc/amportal.conf, set FOPRUN=false, and be sure you do not have a line with "start_fop" in /etc/rc.d/rc.local

        Best regards,

        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