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

HAProxy backend server DOWN

Cache/Proxy
2
4
497
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.
  • J
    jdenny
    last edited by Nov 14, 2024, 4:59 PM

    I have a single frontend server configured to route traffic to multiple backends based on the subdomain. I have added all of these and they were UP and working fine. Until they weren't.... I have deleted a backend server when receiving an error, recreated it IDENTICALLY, and poof it works again. So I am playing whack-a-mole with deleting and recreating things.

    I have 8 different backend servers. Half work, half don't. All configs are seemingly the same.

    I have tried to update the package, but the pfsense package manager says I am on the latest version.

    login-to-view

    login-to-view

    NOTICE] (69864) : haproxy version is 2.7.8-58c657f
    [NOTICE] (69864) : path to executable is /usr/local/sbin/haproxy
    [WARNING] (69864) : config : Server lidarr-backend_ipvANY/lidarr is DOWN, changed from server-state after a reload. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
    [WARNING] (69864) : config : Server sonarr-backend_ipvANY/sonarr is DOWN, changed from server-state after a reload. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
    [WARNING] (69864) : config : Server radarr-backend_ipvANY/radarr is DOWN, changed from server-state after a reload. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
    [WARNING] (69864) : config : Server prowlarr-backend_ipvANY/prowlarr is DOWN, changed from server-state after a reload. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.

    Does anyone have any insight into this?

    V 1 Reply Last reply Nov 14, 2024, 6:36 PM Reply Quote 0
    • V
      viragomann @jdenny
      last edited by Nov 14, 2024, 6:36 PM

      @jdenny
      The backend state is determined by the health check. So ensure that your health check works with your backend server. Use basic if you're unsure.

      J 1 Reply Last reply Nov 14, 2024, 6:49 PM Reply Quote 1
      • J
        jdenny @viragomann
        last edited by Nov 14, 2024, 6:49 PM

        @viragomann So I changed all of the "Checks" from HTTP to Basic. Now everything is working. However, yesterday the HTTP check worked fine with everything. What would the underlying reason be for this?

        Regardless, thanks for the help... Looks like it was an easy fix (if it holds).

        V 1 Reply Last reply Nov 14, 2024, 7:19 PM Reply Quote 0
        • V
          viragomann @jdenny
          last edited by Nov 14, 2024, 7:19 PM

          @jdenny
          If you use the HTTP check, you will need to configure it properly. You can specify the method, URL and also the protocol version.

          Note that HAproxy just request the server by its IP and port as stated in the backend setting. It doesn't send a host header to the backend. If your server requires this, the check will fail.
          Also it just requests the server root / if you didn't state any other URL.

          So ensure, that your server is responding to such requests.

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