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

    HAproxy management not working

    Scheduled Pinned Locked Moved Cache/Proxy
    3 Posts 2 Posters 841 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.
    • keyserK
      keyser Rebel Alliance
      last edited by

      Hi

      I finally bit the bullit today and upgraded my PFsense 2.2.6 to 2.3.1_5.
      I reinstalled 2.3.1 from scratch and restored the config file, and everything seems to work beautifully…. BUT:

      HAproxy (not devel) is acting up.
      It installed fine, all my frontend/backends are working just fine and everything is accessible from my WAN link. The dashboard widget is reporting clients correctly.

      But I cannot configure it. When accessing Services -> HAproxy i just get a 404 not found on the https://hostname/HAproxy_listeners.php page.
      Likewise i cannot access the Stats page in diagnostics.

      My skill's does unfortunately not include how to diagnose why that's happening, so... HELP :-)

      Love the no fuss of using the official appliances :-)

      1 Reply Last reply Reply Quote 0
      • keyserK
        keyser Rebel Alliance
        last edited by

        Hmm.

        It seems it was the update from 2.3.1 to  2.3.1_5 that was to blame.

        I reinstalled the package, and now everything is working.

        Love the no fuss of using the official appliances :-)

        1 Reply Last reply Reply Quote 0
        • P
          PiBa
          last edited by

          The https://hostname/HAproxy_listeners.php never existed on 2.3.x versions.. (or at least it wasnt supposed to..) All the php package files for haproxy package where moved to a subfolder https://hostname/haproxy/HAproxy_listeners.php ..

          It might have been that some old 2.2.x files remained or that old menu references where still present in the config file..

          Anyway good that a reinstall of package fixed it..  :D

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