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. FOP not working: Couldn't load variables.txt?aldope=64572

FOP not working: Couldn't load variables.txt?aldope=64572

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

    I noticed this was an old problem on FOP1 concerning adobe flash - http://www.asternic.org/archives/msg03086.html

    I seem to have the same issue on my FOP2 install, it has been running fine for quite some time (purchased version), all of a sudden the fop webpage loads with:
    Couldn't load variables.txt?aldope=64572

    The number being different everytime.

    I have tried ./fop2_server -test and manager connection is fine, and it starts/stops just fine, so I think it may once again be an incompatibility with flash.

    any ideas?

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

      That error is not from FOP2. there is no variables.txt in fop2. The problem with fop1 usually happens when the daemon (op_server.pl) is not running.

      In FOP2, if the daemon is not running, you will be asked to enter the extension and password and then it will try to connect but it will never succeed.

      Verify your fop2_server is actually running:

      pgrep fop2_server

      if it is not running, run it by hand in the console to see if it errors out:

      /usr/local/fop2/fop2_server -X 3

      (with no --test).

      If you get an error about not being able to bind to port 4445, then stop fop1 or change fop1 port to something else so fop2 can run.

      1 Reply Last reply
      0
      • T
        T
        totalimpact
        wrote on last edited by
        #3

        I think what has happened is a freepbx update has overwritten some of my fop web dir - I renamed fop2 to be panel when I first installed it, so I just recompiled my fop install and it works again.

        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