hack3rs.ca network-security
/502/ :: http-status::502

root@hack3rs:/srv/www$ curl -i /502/

HTTP/1.1 502 Bad Gateway

A gateway or proxy received an invalid response from an upstream server.

status-summary.log
HTTP 502 Bad Gateway

The edge layer could not get a usable response from the backend service it depends on.

Trace the request path through CDN, reverse proxy, and origin service to find the failing hop.

likely-causes.lst
  • $Upstream service crashed or returned malformed HTTP.
  • $TLS handshake failure between proxy and origin.
  • $DNS resolution or service discovery issue for the upstream target.
  • $Load balancer target health checks are passing intermittently.
recovery-steps.md
  1. Inspect reverse proxy/CDN error logs and upstream status metrics.
  2. Check origin service health and listen ports.
  3. Validate upstream TLS certificates and trust configuration.
  4. Review DNS/service discovery records and target registration.
quick-actions.sh
open / Return to the home terminal open /learning Browse structured learning modules open /errors View the full HTTP error reference open /contact Report a broken link or page issue
ops-note.txt

Use these pages for debugging and user guidance. In production, configure your host or reverse proxy to return the matching HTTP status code for the route (especially for 502 and 404/500 responses) rather than serving a 200 with error-themed content.