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

    HAProxy x-forward-for

    Scheduled Pinned Locked Moved Cache/Proxy
    1 Posts 1 Posters 502 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.
    • L
      ludejim
      last edited by

      I currently have HAProxy installed on my pfsense firewall and it works well.

      I have a shared front end that 3 servers utilize. Everything works as intended.
      Those three servers work perfectly fine with the "Use "forwardfor" option" enabled, which allows me to track unique website visitors with tools like google analytics.

      I have been running HomeAssistant for a very long time and just had the desire to access this server from the outside world. I added Home Assistant to the shared front end. The only way I can get Home Assistant to work is by disabling the "Use "forwardfor" option". This makes Home Assistant work well, but a few of the other servers will start to randomly give 503 errors.

      Another aspect that may need to be taken into consideration is that I use Cloud Flare as my DNS.

      I have tried creating another shared front end and sticking the home assistant server under it, but HAProxy does not like two shared front ends with the same listen address. This breaks all front ends that do not reside under the second shared front end...

      Any insights on how to make separate shared front ends with the same listen address so that I can disable the xforward for option would be great. Other solutions are also welcome.

      Regards,
      James

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