502 Bad Gateway (NGINX)

On-Premise
1

Hi,
I installed Sentry successfully and images are successfully running but if i tried in browser, throws “502 bad Gateway”(NGINX). I didnt change any configuration,Kindly help me to resolve this issue.

2

I’ve started noticing same issue with our installation. Sentry UI is not working but POST /api/2/store/ is working fine.

021/02/25 21:07:06 [error] 6#6: *18530 connect() failed (111: Connection refused) while connecting to upstream, client: 172.31.34.90, server: , request: "GET / HTTP/1.1", upstream: "http://172.18.0.27:9000/", host: "172.31.21.155:9000"
172.31.34.90 - - [25/Feb/2021:21:07:06 +0000] "GET / HTTP/1.1" 502 150 "-" "ELB-HealthChecker/2.0" "-"
2021/02/25 21:07:06 [error] 6#6: *18532 connect() failed (111: Connection refused) while connecting to upstream, client: 172.31.19.171, server: , request: "GET / HTTP/1.1", upstream: "http://172.18.0.27:9000/", host: "172.31.21.155:9000"
3

Even api also not working showing bad gateway only

4

@sathak for us it was due to heave load on the server. Check nginx logs, it may provide you more info about your issue

You can list all containers
sudo docker container ls

then follow nginx logs
sudo docker container logs --follow sentry_onpremise_nginx_1

5

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