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 stopped working after registration!

Fop2 stopped working after registration!

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 108 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
    dansford
    wrote on last edited by
    #1

    Hi,

    We are running an elastix 2.2 distribution on NIC interface eth1 (not eth0, as it is not recognized, there s no cable in eth0) and installed fop2 through the add ons. Demo worked fine, with no issues. We purchased the white label license and installed it through the fop2 panel footer, where it mentions to enter the code. After doing so we are unable to login to fop2!
    "--test" shows no license installed, only demo.

    Browsed the forum and saw there are some issues when using a different Ethernet interface other than eth0, thus we registered through the cli command again putting in "--register -i -eth1" switch, registered successfully, --test shows the white label license (1). But still unable to login to fop2!!

    "service fop2 status" shows fop2 not running. So we restart by "service fop2 restart", fop2 starts "ok", but still unable to login to fop2!. "service fop2 status" again show fop2 crash and some syslock error!

    Please help to resolve this issue. Was working fine using the demo, the problem arose we we tried to register the license.

    Thanks,
    D

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

      I think we already fixed this over chat/ssh.

      If you use another interface for binding the license, you have to modify the options for the init script to pass the -i eth1 parameter.

      In /etc/sysconfig/fop2

      set

      OPTIONS="-d -i eth1 -c /etc/asterisk/fop2"
      

      For non elastix rpm users, the -c option should not be used, only -d -i eth1.

      After that restart fop2

      service fop2 restart

      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