Icecast streaming behind HAProxy 2.8

We have been streaming audio with Icecast behind HAProxy 1.8 on Ubuntu 18.04 for a long time. It’s in need of an upgrade no doubt. After upgrading to Ubuntu 24.04 running HAProxy 2.8 and now I am experiencing an issue with HTTPS dropping after 15-20 minutes. When it drops, HTTPS connections time out for a minute or two. We use pfSense NAT routing. This is easily duplicated using a custom port forward to the newly upgraded server, with only me as the client in HAProxy stats.

After going round and round with AI and trying many options from changes to the HAProxy configuration or Ubuntu kernel options, the issue remains. AI has finally boiled it down to the need to run in mode tcp instead of mode http, however, I need Layer 7 to get the X-Forward-For header for the Icecast logs. AI has suggested moving my Icecast to WebSockets as the ultimate solution. I thought I’d check here first of this is reasonable?

BTW - AI suggests the fundamental reason our existing Ubuntu 18.04 / HAProxy 1.8 server runs without issue while the new Ubuntu 24.04 / HAProxy 2.8 server drops connections is a radical rewrite of how HAProxy processes HTTP data internally.

Thanks for any guidance on upgrading. HAProxy has always been rock solid, and we’d like to get it working.

That’s a blind guess. Configuration, outpuf of haproxy -vv and the logs indicating the reason for the disconnect are necessary to troubleshoot this.

Are you saying that when this happens, not even new parallel connections establish (basically the entire service is dead of all clients, new and old), or are you saying the application stops working for a minute or two before it reconnects for this specific session?

Thanks for the help. Yes, when the connection drops, I cannot connect again for a minute or two, I even tried in a different browser while experiencing the issue. No output in the logs when the disconnect happens, I only see the connections.

root@haproxy2:~# haproxy -vv
HAProxy version 2.8.30-0ubuntu0.24.04.1 2026/10/06 - https://haproxy.org/
Status: long-term supported branch - will stop receiving fixes around Q2 2028.
Known bugs: http://www.haproxy.org/bugs/bugs-2.8.30.html
Running on: Linux 6.8.0-147-generic #147-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 24 11:33:16 UTC 2026 x86_64
Build options :
  TARGET  = linux-glibc
  CPU     = generic
  CC      = cc
  CFLAGS  = -O2 -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/build/haproxy-X7IdTm/haproxy-2.8.30=/usr/src/haproxy-2.8.30-0ubuntu0.24.04.1 -Wdate-time -D_FORTIFY_SOURCE=3 -Wall -Wextra -Wundef -Wdeclaration-after-statement -Wfatal-errors -Wtype-limits -Wshift-negative-value -Wshift-overflow=2 -Wduplicated-cond -Wnull-dereference -fwrapv -Wno-address-of-packed-member -Wno-unused-label -Wno-sign-compare -Wno-unused-parameter -Wno-clobbered -Wno-missing-field-initializers -Wno-cast-function-type -Wno-string-plus-int -Wno-atomic-alignment
  OPTIONS = USE_OPENSSL=1 USE_LUA=1 USE_SLZ=1 USE_SYSTEMD=1 USE_QUIC=1 USE_PROMEX=1 USE_PCRE2=1 USE_PCRE2_JIT=1 USE_QUIC_OPENSSL_COMPAT=1
  DEBUG   = -DDEBUG_STRICT -DDEBUG_MEMORY_POOLS

Feature list : -51DEGREES +ACCEPT4 +BACKTRACE -CLOSEFROM +CPU_AFFINITY +CRYPT_H -DEVICEATLAS +DL -ENGINE +EPOLL -EVPORTS +GETADDRINFO -KQUEUE -LIBATOMIC +LIBCRYPT +LINUX_CAP +LINUX_SPLICE +LINUX_TPROXY +LUA +MATH -MEMORY_PROFILING +NETFILTER +NS -OBSOLETE_LINKER +OPENSSL -OPENSSL_WOLFSSL -OT -PCRE +PCRE2 +PCRE2_JIT -PCRE_JIT +POLL +PRCTL -PROCCTL +PROMEX -PTHREAD_EMULATION +QUIC +QUIC_OPENSSL_COMPAT +RT +SHM_OPEN +SLZ +SSL -STATIC_PCRE -STATIC_PCRE2 +SYSTEMD +TFO +THREAD +THREAD_DUMP +TPROXY -WURFL -ZLIB

Default settings :
  bufsize = 16384, maxrewrite = 1024, maxpollevents = 200

Built with multi-threading support (MAX_TGROUPS=16, MAX_THREADS=256, default=4).
Built with OpenSSL version : OpenSSL 3.0.13 30 Jan 2024
Running on OpenSSL version : OpenSSL 3.0.13 30 Jan 2024
OpenSSL library supports TLS extensions : yes
OpenSSL library supports SNI : yes
OpenSSL library supports : TLSv1.0 TLSv1.1 TLSv1.2 TLSv1.3
OpenSSL providers loaded : default
Built with Lua version : Lua 5.4.6
Built with the Prometheus exporter as a service
Built with network namespace support.
Running with a replaced memory allocator (e.g. via LD_PRELOAD).
Built with libslz for stateless compression.
Compression algorithms supported : identity("identity"), deflate("deflate"), raw-deflate("deflate"), gzip("gzip")
Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT IP_FREEBIND
Built with PCRE2 version : 10.42 2022-12-11
PCRE2 library supports JIT : yes
Encrypted password support via crypt(3): yes
Built with gcc compiler version 13.3.0

Available polling systems :
      epoll : pref=300,  test result OK
       poll : pref=200,  test result OK
     select : pref=150,  test result OK
Total: 3 (3 usable), will use epoll.

Available multiplexer protocols :
(protocols marked as <default> cannot be specified using 'proto' keyword)
       quic : mode=HTTP  side=FE     mux=QUIC  flags=HTX|NO_UPG|FRAMED
         h2 : mode=HTTP  side=FE|BE  mux=H2    flags=HTX|HOL_RISK|NO_UPG
       fcgi : mode=HTTP  side=BE     mux=FCGI  flags=HTX|HOL_RISK|NO_UPG
         h1 : mode=HTTP  side=FE|BE  mux=H1    flags=HTX|NO_UPG
  <default> : mode=HTTP  side=FE|BE  mux=H1    flags=HTX
       none : mode=TCP   side=FE|BE  mux=PASS  flags=NO_UPG
  <default> : mode=TCP   side=FE|BE  mux=PASS  flags=

Available services : prometheus-exporter
Available filters :
        [BWLIM] bwlim-in
        [BWLIM] bwlim-out
        [CACHE] cache
        [COMP] compression
        [FCGI] fcgi-app
        [SPOE] spoe
        [TRACE] trace

https://station2.wmnf.org:4444/wmnf_high_quality

Still need to take a look at the configuration, and if the logs don’t help as-is we need to configure logging so that they are actually useful.

Also provide the outputs of systemctl status haproxy and journalctl -u haproxy after such an event.

You are missing the latest security update, please run a apt update && apt upgrade to fix that; if haproxy is crashing periodically due to some CVEs getting exploided that could explain the behaviour (although I think that is rather unlikely) - but we do need to know if haproxy is completely crashing here (and beeing restarted by systemd after a little bit) or if this is something else (timeout handling in whichever part of the stack).

Okay, this is hacked up after trying what AI suggests. I needed the X-Forwarded-For header for the Icecast logs and it wanted me to use mode tcp, this was the answer. I can go back to my configuration before troubleshooting with what I was using in HAProxy 1.8 if you think its best.

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
    tune.ssl.maxrecord 16384
    nbthread 1
    nosplice

defaults
    log     global
    mode    http
    option  httplog
    option  dontlognull
    option forwardfor
    option http-server-close
    stats enable
    stats auth admin:wmnfadmin121
    stats uri /hastats
    retries 3
    option redispatch
    timeout connect  20s
    timeout client  10m
    timeout server  10m
    errorfile 400 /etc/haproxy/errors/400.http
    errorfile 403 /etc/haproxy/errors/403.http
    errorfile 408 /etc/haproxy/errors/408.http
    errorfile 500 /etc/haproxy/errors/500.http
    errorfile 502 /etc/haproxy/errors/502.http
    errorfile 503 /etc/haproxy/errors/503.http
    errorfile 504 /etc/haproxy/errors/504.http

frontend stream_https_in_7
        mode http
        bind 192.168.7.69:443 interface eno2 ssl crt /etc/haproxy/certs/wmnf.pem alpn http/1.1 no-tls-tickets

        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
        timeout client 24h

        http-request set-header X-Forwarded-Proto https
        http-request set-header X-Forwarded-For %[src]

        acl ssl_ha hdr(host) -i ha.wmnf.org
        acl ssl_station hdr(host) -i station.wmnf.org www.wmnf.org wmnf.org
        acl ssl_stream hdr(host) -i stream.wmnf.org
        acl ssl_tickets hdr(host) -i station.wmnf.org trouble.wmnf.org

        use_backend ha_cluster_7 if ssl_ha
        use_backend www_cluster_7 if ssl_station
        use_backend tickets_cluster_7 if ssl_tickets

        use_backend stream_pass_through_l7 if ssl_stream
        default_backend stream_pass_through_l7

frontend isolated_stream_l4
        # Receives the handed-off connection as raw TCP
        mode tcp
        bind 127.0.0.1:8080 accept-proxy
        timeout client 24h
        default_backend ssl_cluster_7

backend stream_pass_through_l7
        mode http
        timeout server 24h
        ignore-persist if TRUE
        server local_l4_bridge 127.0.0.1:8080 send-proxy

Here is the output after applying the update. Log when connecting; no further output when dropped…

2026-11-04T09:31:20.804094-05:00 haproxy2 haproxy[218033]: 47.206.68.190:4118 [04/Nov/2026:09:31:20.758] stream_https_in_7~ stream_pass_through_l7/local_l4_bridge 0/0/1/1/45 200 208020 - - CD-- 4/2/1/1/0 0/0 {||Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KH} "GET /wmnf_high_quality HTTP/1.1"
2026-11-04T09:31:20.804399-05:00 haproxy2 haproxy[218033]: 47.206.68.190:4118 [04/Nov/2026:09:31:20.758] stream_https_in_7~ stream_pass_through_l7/local_l4_bridge 0/0/1/1/45 200 208020 - - CD-- 4/2/1/1/0 0/0 {||Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KH} "GET /wmnf_high_quality HTTP/1.1"
2026-11-04T09:31:20.804500-05:00 haproxy2 haproxy[218033]: 47.206.68.190:4118 [04/Nov/2026:09:31:20.759] isolated_stream_l4 ssl_cluster_7/stream1 1/0/43 232624 CD 3/2/1/1/0 0/0
root@haproxy2:~# systemctl status haproxy
● haproxy.service - HAProxy Load Balancer
     Loaded: loaded (/usr/lib/systemd/system/haproxy.service; enabled; preset: enabled)
     Active: active (running) since Wed 2026-11-04 09:30:50 EST; 7min ago
       Docs: man:haproxy(1)
             file:/usr/share/doc/haproxy/configuration.txt.gz
   Main PID: 217969 (haproxy)
     Status: "Ready."
      Tasks: 2 (limit: 19080)
     Memory: 13.0M (peak: 13.7M)
        CPU: 1.724s
     CGroup: /system.slice/haproxy.service
             ├─217969 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock
             └─218033 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock

Nov 04 09:30:50 haproxy2 haproxy[217969]: [WARNING]  (217969) : config : parsing [/etc/haproxy/haproxy.cfg:28] : 'option htt>
Nov 04 09:30:50 haproxy2 haproxy[217969]: [WARNING]  (217969) : config : 'stats' statement ignored for frontend 'isolated_st>
Nov 04 09:30:50 haproxy2 haproxy[217969]: [WARNING]  (217969) : config : 'stats' statement ignored for backend 'ssl_cluster_>
Nov 04 09:30:50 haproxy2 haproxy[217969]: [WARNING]  (217969) : config : 'option forwardfor' ignored for frontend 'isolated_>
Nov 04 09:30:50 haproxy2 haproxy[217969]: [WARNING]  (217969) : config : 'option forwardfor' ignored for backend 'ssl_cluste>
Nov 04 09:30:50 haproxy2 haproxy[217969]: [NOTICE]   (217969) : New worker (218033) forked
Nov 04 09:30:50 haproxy2 haproxy[217969]: [NOTICE]   (217969) : Loading success.
Nov 04 09:31:20 haproxy2 haproxy[218033]: 47.206.68.190:4118 [04/Nov/2026:09:31:20.758] stream_https_in_7~ stream_pass_throu>
Nov 04 09:31:20 haproxy2 haproxy[218033]: 47.206.68.190:4118 [04/Nov/2026:09:31:20.758] stream_https_in_7~ stream_pass_throu>
Nov 04 09:31:20 haproxy2 haproxy[218033]: 47.206.68.190:4118 [04/Nov/2026:09:31:20.759] isolated_stream_l4 ssl_cluster_7/str

The journal command returns a great deal of logs; I am posting only what I believe are the last pertinent lines…

Nov 04 09:30:49 haproxy2 systemd[1]: Stopping haproxy.service - HAProxy Load Balancer...
Nov 04 09:30:49 haproxy2 haproxy[198165]: [NOTICE]   (198165) : haproxy version is 2.8.30-0ubuntu0.24.04.2
Nov 04 09:30:49 haproxy2 haproxy[198165]: [NOTICE]   (198165) : path to executable is /usr/sbin/haproxy
Nov 04 09:30:49 haproxy2 haproxy[198165]: [WARNING]  (198165) : Exiting Master process...
Nov 04 09:30:49 haproxy2 haproxy[198165]: [ALERT]    (198165) : Current worker (217706) exited with code 143 (Terminated)
Nov 04 09:30:49 haproxy2 haproxy[198165]: [WARNING]  (198165) : Former worker (198167) exited with code 143 (Terminated)
Nov 04 09:30:49 haproxy2 haproxy[198165]: [WARNING]  (198165) : All workers exited. Exiting... (0)
Nov 04 09:30:50 haproxy2 haproxy[217969]: [NOTICE]   (217969) : haproxy version is 2.8.30-0ubuntu0.24.04.2
Nov 04 09:30:50 haproxy2 haproxy[217969]: [NOTICE]   (217969) : path to executable is /usr/sbin/haproxy
Nov 04 09:30:50 haproxy2 haproxy[217969]: [WARNING]  (217969) : config : parsing [/etc/haproxy/haproxy.cfg:28] : 'option htt>
Nov 04 09:30:50 haproxy2 haproxy[217969]: [WARNING]  (217969) : config : 'stats' statement ignored for frontend 'isolated_st>
Nov 04 09:30:50 haproxy2 haproxy[217969]: [WARNING]  (217969) : config : 'stats' statement ignored for backend 'ssl_cluster_>
Nov 04 09:30:50 haproxy2 haproxy[217969]: [WARNING]  (217969) : config : 'option forwardfor' ignored for frontend 'isolated_>
Nov 04 09:30:50 haproxy2 haproxy[217969]: [WARNING]  (217969) : config : 'option forwardfor' ignored for backend 'ssl_cluste>
Nov 04 09:30:50 haproxy2 haproxy[217969]: [NOTICE]   (217969) : New worker (218033) forked
Nov 04 09:30:50 haproxy2 haproxy[217969]: [NOTICE]   (217969) : Loading success.
Nov 04 09:31:20 haproxy2 haproxy[218033]: 47.206.68.190:4118 [04/Nov/2026:09:31:20.758] stream_https_in_7~ stream_pass_throu>
Nov 04 09:31:20 haproxy2 haproxy[218033]: 47.206.68.190:4118 [04/Nov/2026:09:31:20.758] stream_https_in_7~ stream_pass_throu>
Nov 04 09:31:20 haproxy2 haproxy[218033]: 47.206.68.190:4118 [04/Nov/2026:09:31:20.759] isolated_stream_l4 ssl_cluster_7/str>
lines 12225-12258/12258 (END)

Yes, go back to your 1.8 configuration.

This configuration is incomplete (missing ssl_cluster_7 backend) but it is also a mess that makes no sense (we can argue about the differences between layer 4 and layer 7, but if you suspect an issue with layer 7 you need to not use layer 7 as oppossed to routing the traffic once through layer 4 but using layer 7 anyway).

From the log, the issue looks like it is external (pfsense), the CF flag indicates:

 CD   The client unexpectedly aborted during data transfer. This can be
      caused by a browser crash, by an intermediate equipment between the
      client and HAProxy which decided to actively break the connection,
      by network routing issues between the client and HAProxy, or by a
      keep-alive session between the server and the client terminated first
      by the client.

Well, not sure what is happening. I did try it many times over several days since I brought in the HAProxy 1.8 configuration the first time. Even several times when trying more subtle changes to the config. I put it back now and well above the timeout I was seeing at 15-20 minutes at more than 30 minutes. I believe the only change has been the package updates. The 1.8 was behind the same pfSense router. Surely my odd port was not being exploited. Seems to be fine; sorry for the trouble, wish I had all that troubleshooting time back :-/

For the records, the package update was: Start-Date: 2026-11-04 09:30:23
Commandline: apt upgrade
Upgrade: bind9-host:amd64 (1:9.18.39-0ubuntu0.24.04.8, 1:9.18.39-0ubuntu0.24.04.9), libmspack0t64:amd64 (0.11-1.1build1, 0.11-1.1ubuntu0.24.04.1), gvfs-fuse:amd64 (1.54.4-0ubuntu1~24.04.4, 1.54.4-0ubuntu1~24.04.5), gvfs-common:amd64 (1.54.4-0ubuntu1~24.04.4, 1.54.4-0ubuntu1~24.04.5), gvfs-libs:amd64 (1.54.4-0ubuntu1~24.04.4, 1.54.4-0ubuntu1~24.04.5), gnome-shell:amd64 (46.0-0ubuntu6~24.04.16, 46.0-0ubuntu6~24.04.17), libsoup2.4-common:amd64 (2.74.3-6ubuntu1.9, 2.74.3-6ubuntu1.10), libsoup-2.4-1:amd64 (2.74.3-6ubuntu1.9, 2.74.3-6ubuntu1.10), libsoup-3.0-0:amd64 (3.4.4-5ubuntu0.9, 3.4.4-5ubuntu0.10), gvfs-backends:amd64 (1.54.4-0ubuntu1~24.04.4, 1.54.4-0ubuntu1~24.04.5), gvfs:amd64 (1.54.4-0ubuntu1~24.04.4, 1.54.4-0ubuntu1~24.04.5), gvfs-daemons:amd64 (1.54.4-0ubuntu1~24.04.4, 1.54.4-0ubuntu1~24.04.5), bind9-dnsutils:amd64 (1:9.18.39-0ubuntu0.24.04.8, 1:9.18.39-0ubuntu0.24.04.9), gnome-shell-common:amd64 (46.0-0ubuntu6~24.04.16, 46.0-0ubuntu6~24.04.17), libpcre2-8-0:amd64 (10.42-4ubuntu2.1, 10.42-4ubuntu2.2), bind9-libs:amd64 (1:9.18.39-0ubuntu0.24.04.8, 1:9.18.39-0ubuntu0.24.04.9), libsoup-3.0-common:amd64 (3.4.4-5ubuntu0.9, 3.4.4-5ubuntu0.10), gir1.2-soup-3.0:amd64 (3.4.4-5ubuntu0.9, 3.4.4-5ubuntu0.10), haproxy:amd64 (2.8.30-0ubuntu0.24.04.1, 2.8.30-0ubuntu0.24.04.2), libpcre2-32-0:amd64 (10.42-4ubuntu2.1, 10.42-4ubuntu2.2)
End-Date: 2026-11-04 09:30:47

I don’t know what you are saying.

Are you saying you went back to the 1.8 configuration before introducing the AI configuration, and now it works even with haproxy 2.8 under Ubuntu 24.04?

Are you saying that after the apt upgrade it stopped happening?

Are you saying you did both and don’t know which of the two changes did the trick?

Yes, yes, and yes. But as mentioned before, I am the only client on this new setup. I did compare it to HTTP and HTTPS on the 1.8 install; both worked, while HTTPS was dropping. If it happens again, I’ll do more thorough testing from multiple locations.

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.

Are you sure that in the icecast configuration you listed the internal IP address 192.168.7.69 of the haproxy 2.8 box as a trusted proxy?

If not, icetrust may not trust the X-Forwarded-For header sent from haproxy at all and ignore it for security reasons.

A couple of config things that I suggest you fix (even for 1.8), unrelated to the X-Forwarded-For issue:

acl ssl_station hdr(host) req_ssl_sni -i station.wmnf.org
acl ssl_stream hdr(host) req_ssl_sni -i stream.wmnf.org

This compares the HTTP Host header against a list of 3 strings, which are:

req_ssl_sni
-i
station.wmnf.org

in the first ACL, and:

req_ssl_sni
-i
stream.wmnf.org

in the second ACL.

It will work anyway, because it will find string number 3 in both ACLs, but this is confusing for no reason and it would match a Host header that is -i for example, which is not what you want.

This ACL needs to be without req_ssl_sni:

acl ssl_station hdr(host) -i station.wmnf.org
acl ssl_stream hdr(host) -i stream.wmnf.org

What is req_ssl_sni ? It is a fetch that is irrelevant in this configuration, you’d use it when you are in TCP mode and passing through encrypted TLS.

tcp-request inspect-delay 5s
tcp-request content accept if { req_ssl_hello_type 1 }

Not necessary because you are not using req_ssl_sni and it would not work anyway because you are not in TCP mode here, just as the warning you already saw says.

server stream1 192.168.7.16:8000 cookie A check
server stream2 192.168.7.17:8000 cookie A check

For the record, a cookie must be unique per server otherwise there is no point in cookie stickiness; not an issue if the actual production cookie values are different and this is just and example of course.

Those irrelevant/wrong configurations - even though haproxy will work anyway and just produce some warnings - will confuse anyone reading the config including an AI.

Well, I do have the x-forwarded-for settings in there. But with your pointers, I checked everything and found the configuration was failing on restart and falling back to the icecast2 service, and not icecast-kh I am running for support of the proxy headers.

And thanks for the pointers; yes, a lot left over from previous tcp mode being used a long time ago. I’ve cleaned up.

Thanks again!!