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

haproxy command socket does not exist

Scheduled Pinned Locked Moved Cache/Proxy
3 Posts 3 Posters 890 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.
  • C
    cjbujold
    last edited by cjbujold Jul 3, 2023, 5:19 PM Jul 3, 2023, 5:14 PM

    Upgraded to Pfsense 2.7 and unable to start HAProxy getting error:

    haproxy command socket does not exist, haproxy not running?haproxy command socket does not exist, haproxy not running?
    [WARNING] (14628) : config : config: Can't open global server state file '/tmp/haproxy_server_state': No such file or directory

    How do I fix?

    Thanks

    A 1 Reply Last reply Jul 9, 2023, 1:42 PM Reply Quote 0
    • A
      angel701129 @cjbujold
      last edited by angel701129 Jul 9, 2023, 1:43 PM Jul 9, 2023, 1:42 PM

      @cjbujold I recommend you review the system logs, in my case I found that by disabling the "Cookie protection" option in all the Backends, the HAProxy started without problems.
      You can workaround the "Cookie protection" in "Services>HAProxy>Backend>Edit> Backend pass thru" setting this option in each Backend where you disable "Cookie protection": http-response replace-header Set-Cookie "^((?:(?!; [Ss]ecure\b).)*)$" "\1; secure" if { ssl_fc }

      R 1 Reply Last reply Jul 10, 2023, 12:32 PM Reply Quote 0
      • R
        RegalMonkey @angel701129
        last edited by Jul 10, 2023, 12:32 PM

        @angel701129 @PiBa

        I ended up with a similar response after the 2.7 upgrade, it seems odd that this would be changed by the OS upgrade rather than a package change though. Did something change withing the 2.7 version that reverted how the HAProxy config gets written?

        In my case specifically it listed '[ALERT] 190/122149 (58497) : parsing [/var/etc/haproxy_test/haproxy.cfg:520] : The 'rspirep' directive is not supported anymore since HAProxy 2.1. Use 'http-response replace-header' instead.'

        1 Reply Last reply Reply Quote 0
        1 out of 3
        • First post
          1/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received