"connection reset by peer" in an openshift/k8s environment

### What happened? **Environment:** OpenShift version: 4.12.0-0.okd-2023-02-04-212953 Kubernetes version: v1.25.0-2653+a34b9e9499e6c3-dirty Grafana is running with default config (only the port is changed to 3001) and empty database. **Issue:** Starting from version 10.4.18 grafana resets connection to its main port while being started in a k8s/OKD environment: ``` /usr/share/grafana $ curl http://127.0.0.1:3001/ curl: (56) Recv failure: Connection reset by peer ``` Note that this happens inside a pod, so no networkPolicy or other k8s entities can possible influence this. I'm also able to run test netcat server-client chain inside very same pod and communicate via socket on a non-WKS port. 10.4.17 and lower versions runs just fine on the very same cluster. Log level is set to trace, no sign of connection or connection dropping reason in grafana logs. (however, in 10.4.17 the following lines appear in the log: ```` logger=context userId=0 orgId=0 uname= t=2025-06-25T13:10:46.867930777Z level=info msg="Request Completed" method=GET path=/ status=302 remote_addr=127.0.0.1 time_ms=0 duration=70.84µs size=29 referer= handler=/ status_source=server logger=context userId=0 orgId=0 uname= t=2025-06-25T13:11:42.801848884Z level=info msg="Request Completed" method=GET path=/ status=302 remote_addr=127.0.0.1 time_ms=0 duration=64.27µs size=29 referer= handler=/ status_source=server ```` ) I'm attaching the log file from the pod. [grafana-test-9854d5f4c-g2g96-grafana.log](https://github.com/user-attachments/files/20898727/grafana-test-9854d5f4c-g2g96-grafana.log) ### What did you expect to happen? I'm expecting grafana answering lie it did on 10.4.17: ``` /usr/share/grafana $ curl http://127.0.0.1:3001/ <a href="/login">Found</a>. ``` ### Did this work before? Working on 10.4.17 an lower versions.