Large Conntrack/Active connections count. FD Limit Reached

Hey all, I’m currently trying to migrate my servers from NGINX to HAProxy but on restarting the proxies with the new configuration, the conntrack and active connection count skyrockets to around 600k/20k respectively. I’ve been looking at this issue for a week and I have no idea how to proceed. I’ve looked at tcpdumps and other tools like ss but I honestly don’t know what to look for. The logs don’t really show anything. I haven’t tried yet to set them to a verbose mode as they generate so much garbage. Usually, Conntrack is hanging around 15k per server. also what is odd is that if one haproxy reloads the other proxies also spike around 600k in conntrack. what TH could be happening? Thanks for the help
config: global daemon maxconn 50000 user haproxy group haproxy - Pastebin.com (edited)

http-response del-header Connection

You are interfering with haproxy’s connection handling. Don’t do that. I know those crazy hacks (overwriting connection handling headers) are considered normal in the nginx world, but that is definitely not the case with haproxy.

http-response set-header Connection close if exceeded_connection reset

Here too, don’t do this. If you believe you need get crazy with connection headers later on, I will probably not be able to stop you, but please get your baseline numbers first without it. Your mileage will certainly vary, if you choose to do so.

Please provide the output of haproxy -vv and from the ss output, try to understand if there is a pattern, like, are most of the sockets in CLOSE_WAIT state? Are most of the sockets between the haproxy and the backend server, or between haproxy and the clients? Things like that could help narrow down the root cause.