502 Bad Gateway After Period of Time

after installing Sentry on-premise I faced 502 Bad Gateway Issues it tries again and again and if I need to fix it I must run docker-compose down then docker-compose up -d
and after that show me an error in Nginx container

[error] 6#6: *21 connect() failed (111: Connection refused) while connecting to upstream, client:, server: , request: “GET /favicon.ico HTTP/1.1”, upstream: “”, host: “sfdamonitor.thiqah.sa”, referrer:

Looks like your Sentry web instance is going down for some reason. It’s not possible to tell why without more information like logs etc.

We have the same issue. This fixes it temporarily, but I have to debug what causes the issue:

docker restart sentry_onpremise_nginx_1

1 Like

My best guess here is lack of RAM. Might be too many workers and threads but that boils down to lack of RAM.
But due to the limited amount of info we have here it is hard to say.

Posting here to follow this topic, as we’ve ran into a similar issue.

In case I catch it again I’ll try grab the logs and post and update here.

I was stucked from last 5 days on the same issue. Though it is a temporarily fix but get me going for now.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.