Error AtlasError Documentation and Resolution
Back to search

HTTP Status Codes

HTTP 502 Bad Gateway

502 Bad Gateway

A server acting as a gateway or proxy received an invalid response from the upstream server it depends on.

502 Bad Gatewaynetworking

Observed message

502 Bad Gateway

Why it happens

  • The upstream service returned an invalid or malformed response to the proxy.
  • The upstream application is down or unstable.
  • Proxy, load balancer, or network configuration broke communication with the upstream.

How to fix it

  1. Check the upstream service health and logs.
  2. Review reverse proxy or load balancer configuration for protocol and routing mismatches.
  3. Inspect network timeouts and response formatting between the proxy and upstream.

Official reference

MDN: 502 Bad Gateway

Related errors

408 Request TimeoutHTTP 408 Request Timeout413 Content Too LargeHTTP 413 Content Too Large414 URI Too LongHTTP 414 URI Too Long429 Too Many RequestsHTTP 429 Too Many Requests

Explore more

networkingBrowse more networking errors
502 Bad Gateway: what it means and how to fix it | Error Atlas