Match the symptom, then work through the safe checks.
1. What best matches what you observe?
2. Complete only the checks that are safe for you.
Show stop conditions
- The page handles payment or identity and you cannot confirm whether an action completed
- The site redirects to an unexpected domain or asks for sensitive information
Likely causes
- The origin server is down or returning an invalid response
- A CDN, reverse proxy, or load balancer cannot reach the origin
- A deployment or configuration change broke the upstream service
- Temporary overload or network failure interrupted the backend
Quick checks, in order
Refresh once after a short wait
Transient gateway failures can clear quickly.
Check whether the service reports an outage
Use the official status page rather than repeated refreshes.
Try another network only to compare
A true 502 usually remains server-side across networks.
If you own the site, inspect gateway and origin logs
Check health probes, timeouts, DNS, TLS, and upstream process state.
Where does the HTTP error appear?
The service owner or host must restore the upstream path.
A specific backend service or deployment may be unhealthy.
The new release, health check, or startup timing is a likely cause.
Stop and get qualified help when
- The page handles payment or identity and you cannot confirm whether an action completed
- The site redirects to an unexpected domain or asks for sensitive information
Official support and model manuals
Use the full model number from the rating label. The manufacturer manual is the deciding reference when codes differ by region or product family.
Frequently asked questions
What does HTTP 502 mean?
A gateway or proxy received an invalid response from an upstream server.
Is this usually a browser problem?
Usually not. Browser state can contribute in some cases, but gateway, server, permission, rate-limit, or upstream conditions are common.