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

    HAProxy: After upgrading 2.5.0 -> 2.5.1 no server entries in backend

    Scheduled Pinned Locked Moved Cache/Proxy
    4 Posts 1 Posters 618 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.
    • D
      dkrizic
      last edited by

      I just upgraded from pfSense 2.5.0 to 2.5.1 and HAProxy stopped working. After taking a deeper look I saw that the generated file /var/etc/haproxy/haproxy.conf has backends without server entries like here:

      backend kubernetes_ipvANY
      	mode			tcp
      	id			123
      	log			global
      	timeout connect		10000
      	timeout server		10000
      	retries			2
      
      

      but is is configured like shown here:

      Screenshot 2021-04-18 at 23.35.04.png

      What could be the reason for that?

      I am using HAProxy (not HAProxy-devel). Any ideas?

      D 1 Reply Last reply Reply Quote 0
      • D
        dkrizic @dkrizic
        last edited by

        BTW: Same with HAProxy-devel

        D 1 Reply Last reply Reply Quote 0
        • D
          dkrizic @dkrizic
          last edited by

          I backed up the configuration, removed the whole <haproxy>....</haproxy> block from the XML and restore that new configuration and created some tests hosts... Same result, the server entries are missing - I am totally clueless:

          backend kubernetes_ipvANY
          	mode			tcp
          	id			100
          	log			global
          	timeout connect		30000
          	timeout server		30000
          	retries			3
          	option			httpchk OPTIONS / 
          
          backend ingress_ipvANY
          	mode			http
          	id			104
          	log			global
          	timeout connect		30000
          	timeout server		30000
          	retries			3
          	option			httpchk OPTIONS /
          

          Is it possible that I am the only one with this problem? I happened after 2.5.0 -> 2.5.1 update without any other configuration change. On 2.5.0 this was working flawlessly.

          D 1 Reply Last reply Reply Quote 0
          • D
            dkrizic @dkrizic
            last edited by

            Ok, this was a side effect of this problem: https://forum.netgate.com/topic/162978/unbound-stop-working-on-127-0-0-1-after-2-5-1-upgrade

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