Unable to Access ChirpStack Web Interface - Connection Reset by Peer

ChirpStack (v4)
1

I’m having trouble accessing the ChirpStack v4 web interface and could use some help troubleshooting the issue. The interface becomes inaccessible approximately every 2 weeks (though the timing isn’t exact), and the only way to restore access is by restarting the Docker container.

When I try to access the web UI, I get a “connection reset” error. Here’s an example of what happens when I use curl:

curl -I http://localhost:8080
curl: (56) Recv failure: Connection reset by peer

ChirpStack is running in a Docker container, and the logs don’t show anything obviously wrong. I see messages like:

  • INFO and DEBUG logs
  • ERROR logs (e.g., “device is disabled”) so normal
  • Messages about received data, join requests, and integration events

However, there’s nothing in the logs referencing HTTP access issues. The web UI is the only part that’s inaccessible—everything else seems to be functioning normally.

I’ve already enabled debug logging, but I’m not sure what else to check. Any suggestions on how to further troubleshoot this issue?

Thanks in advance for your help!

2

This appears to be a common docker issue, unrelated to the specific application.
A link that made most sense to me (from first 10) was this one: Docker “connection reset by peer” error

3

Thanks! I appreciate the response and apologize for not thinking outside the box more. :slightly_frowning_face: Kept overthinking it.

I should add, I have nginx pointing to CS:8080 and am still able to get to nginx, so that is why I thought it might of been something with the container.