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. Cannot connect to FOP2 from my webbrowser

Cannot connect to FOP2 from my webbrowser

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 52 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

    After a smooth installation of FOP2 on OS debian I cannot make a connection from my webbrowser to FOP2.
    The browser returns with the following message:

    **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 xxx.xxx.xxx.xxx Port 80**

    I have checked that FOP2 and Apache2 are running.
    The server and the workstation of which I try to connect to FOP3 panel are on the same internal network segment (no firewall issue).
    I also tried the webbrowser on the server itself (via http//127.0.0.1/fop2) but this is also not working.
    Finally I check for availability of fop2 directory in /var/www/ and this directory exists.

    Is it maybe a permission issue?

    Can anyone help?

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

      Add mod_headers to your apache installation or remove the fop2 .htmlaccess file.

      1 Reply Last reply
      0
      • I
        I
        ipsystems
        wrote on last edited by
        #3

        Thanks Nicolás,

        Adding mod_headers to apache2 solved the problem.
        FOP2 is working great now

        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