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. No connection from webbrowser

No connection from webbrowser

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 147 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.
  • I
    I
    ipsystems
    wrote on last edited by
    #1

    Hello,

    I have installed FOP2 panel on my Debian server on which Asterisk is running.
    The installation went smoothly.
    I can make a connection from FOP2 to the Asterisk manager successfully.
    Now I try to make the connection from my webbrowser to FOP2 panel by entering http://xxx.xxx.xxx.xxx/fop2 into the address field of my webbrowser.
    As a result my webbrowser returns with:

    ***Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log.

    Apache/2.2.16 (Debian) Server at 192.168.1.250 Port 80***

    I have checked fop2 and apache2 are running.
    I also checked that fop2 exists in /var/www

    Even when I try to make a connection from the webbrowser on de Asterisk machine itself is not working,

    So is there something wrong with the webclient in fop2?
    Anyone suggestions to solve this?

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

      The fop2 html directory include an .htaccess file that is read by the apache web server. It tries to set some headers to avoid caching of files. If your apache configuration prevents these from being set (for example if mod_headers is not enabled), you could get a 500 error. So, be sure you have mod_headers enabled. If that is not an option, you could remove the .htaccess file, as it is not vital for fop2 , but handy to have.

      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