HTTP troubleshooting
502 Bad Gateway
A gateway received an invalid response from the upstream application.
What 502 means for a monitor
Statixoup records an incident when 502 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Check whether the upstream process is reachable.
- 2.
Check 2
Review proxy and container logs.
- 3.
Check 3
Verify host, port, TLS, and DNS.
- 4.
Check 4
Check deploy restarts or crashes.
After the service is fixed
- Confirm the URL returns the expected status without a browser session.
- Review response-time and incident history for the recovery.
- Change Expected status code only when the different response is intentional.
Avoid hiding a real outage
Changing the expected code can make an unhealthy response appear operational. Fix the service first whenever the response is unexpected.