Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    PFSense 2.2.6 web interface becomes unresponsive

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 1.2k Views
    Loading More Posts
    • 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.
    • S Offline
      Sander88
      last edited by

      Hi,

      We experiencing an issue in PFSense 2.2.6. It's a high available setup (2 nodes) and the webinterface of the slave becomes unresponsive a few times a month.

      The solution is to login the SSH of the slave node and use options 11 (Restart webConfigurator) and 16 (Restart PHP-FPM). The webinterfaces (and the XMLRPC) becomes reachable again.

      I can't find anything useful in the logs (on both nodes). I guess it's caused by the XMLRPC as that's the only 'user' that's active on the webinterface of the slave during the time it gets unresponsive.

      Is this a known issue? Any suggestion in how to fix it?

      Thanks,
      Sander

      1 Reply Last reply Reply Quote 0
      • V Offline
        viragomann
        last edited by

        I had also such an issue, the lighttpd on backup box crashed when Suricata ran an XMLRPC Sync.
        CMB suggested me to update the lighttpd package. After the update the issue was gone.

        Here is the thread:
        https://forum.pfsense.org/index.php?topic=108832.msg606053#msg606053

        1 Reply Last reply Reply Quote 0
        • S Offline
          Sander88
          last edited by

          @viragomann:

          I had also such an issue, the lighttpd on backup box crashed when Suricata ran an XMLRPC Sync.
          CMB suggested me to update the lighttpd package. After the update the issue was gone.

          Here is the thread:
          https://forum.pfsense.org/index.php?topic=108832.msg606053#msg606053

          Thanks for your reply. I will give it a try, it makes sense to me that this may solve the issue.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.