I’m back. I have triple-checked to be sure this time, copying over the configuration from 1.8 and only changing the IP address, and I’m still struggling to get the version 2.8 X-Forwarded-For header to work like 1.8 does.
Would there be anything in version 2.8 that would cause the ‘option forwardfor’ not to work the same? With the following configuration, I am hitting the default_backend with my testing since I am using the IP address to request, not an FQDN.
global
log /dev/log local0 debug
maxconn 2000
user haproxy
group haproxy
ssl-default-bind-options no-tlsv11 no-tlsv10 no-sslv3
tune.ssl.default-dh-param 2048
defaults
log global
mode http
option httplog
option dontlognull
option forwardfor
option http-server-close
option redispatch
retries 3
timeout connect 20s
timeout client 10m
timeout server 10m
frontend stream_https_in_7
bind 192.168.7.69:443 interface ens9 ssl crt /etc/haproxy/certs/wmnf.pem
log /dev/log local0 debug
capture request header Referrer len 64
capture request header Content-Length len 10
capture request header User-Agent len 64
tcp-request inspect-delay 5s
tcp-request content accept if { req_ssl_hello_type 1 }
http-request set-header X-Forwarded-Proto https
acl ssl_station hdr(host) req_ssl_sni -i station.wmnf.org
acl ssl_stream hdr(host) req_ssl_sni -i stream.wmnf.org
use_backend www_cluster_7 if ssl_station
use_backend ssl_cluster_7 if ssl_stream
default_backend ssl_cluster_7
backend ssl_cluster_7
redirect scheme https if !{ ssl_fc }
balance source
hash-type consistent
option httpclose
option forwardfor
option httpchk GET /wmnf_high_quality
cookie SERVERID insert indirect nocache httponly secure
server stream1 192.168.7.16:8000 cookie A check
server stream2 192.168.7.17:8000 cookie A check
Here is the log entry from HAProxy; it is behind pfSense with NAT port 4444 forwarding to the HAProxy server on port 443. All the same as the HAProxy server running version 1.8:
2026-11-06T20:04:49.948497-05:00 haproxy2 haproxy[278175]: 47.206.68.190:4590 [06/Nov/2026:20:04:35.849] stream_https_in_7~ ssl_cluster_7/stream2 0/0/1/0/14098 200 475850 - - CDNI 2/2/0/0/0 0/0 {||Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:159.0) Gecko/201001} "GET https://the.ip.addr:4444/wmnf_high_quality HTTP/2.0"
And the log entry from Icecast:
192.168.7.69 - - [06/Nov/2026:20:04:49 -0500] "GET /wmnf_high_quality HTTP/1.1" 200 476474 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:159.0) Gecko/20100101 Firefox/159.0" 14
However, version 1.8 shows the real IP with the same configuration. I can actually see the real IP requests coming in from the 1.8 server on the same Icecast server where I see the log entry above. Perhaps something different about Ubuntu 24.04 versus 18.04 running 1.8. I am seeing the following warning when checking the configuration, but I figure it is harmless if ignored and want to stay with the same configuration as 1.8…
root@haproxy2:~# haproxy -c -f /etc/haproxy/haproxy.cfg
[NOTICE] (278638) : haproxy version is 2.8.30-0ubuntu0.24.04.2
[NOTICE] (278638) : path to executable is /usr/sbin/haproxy
[WARNING] (278638) : config : Proxy 'stream_https_in_7': L6 sample fetches ignored on HTTP proxies (declared at /etc/haproxy/haproxy.cfg:206).
Warnings were found.
Configuration file is valid
I’m trying to find an answer here first this time, rather than listening to AI.