Truenas not listening/respecting X-Forward-For in haproxy setup... Feature Request?

So I tried to open what I believe is a “bug”, or at least a Feature request. However, this was quickly shot down. So I would like to ask either for input, opinions, or suggestions on how to solve this.

Issue:
So I access my truenas primarily through a pfsense+haproxy setup. Going through the Truenas audit logs. Basically all of the access IP-addresses being listed, are referenced as the pfsense routers LAN address. The option forwardfor is activated on the frontend.

If someone asks “why” I use it this way: It’s because I can easily use SSL-certs by only needing this setup in one place. Which makes password management easier, since browsers like https websites more. This is obviously not exposed out towards internet.

I’ve seen a few references that one could modify the nginx source code, to enable the X-Forward-For. So that Truenas would recognize and list the actual origin source IP. However, this would not persist between upgrades. And I really don’t want to be fiddling with core functionality, since this is an appliance… Hence me hoping to lift this issue, and hopefully getting this added somehow. :slight_smile:

Running TN ElectricEel-24.10.0.2.
Thanks!