Error 502 is a classic server-to-server error: a gateway, reverse proxy, or CDN tried to fetch content from an upstream server and got an invalid or no response. Because it involves multiple hops, the cause can live anywhere between your browser and the site’s origin.
When you see 502 in a browser, the fastest path to resolution is understanding what’s failing (gateway vs. upstream) and then narrowing down with targeted checks: timestamps, logs, network paths, and configuration.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
HTTP Pocket Reference: Hypertext Transfer Protocol | $6.94 | Buy on Amazon |
| 2 |
|
Pocket Ref Third Edition | $35.99 | Buy on Amazon |
| 3 |
|
Jane's Pocket Guide: A.T. F. | $40.00 | Buy on Amazon |
| 4 |
|
Pocket Guide to Pretty Stitches: Carry-Along Guide to Visible Mending & Embroidery Stitches... | $8.50 | Buy on Amazon |
| 5 |
|
POCKET REFERENCE BOOK 768pgs | $27.11 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
This guide covers the most common causes, what you can do as a visitor, and what site owners should check when 502 starts happening.
Recommended Free Tools
What Error 502 actually means
502 Bad Gateway means: the system acting as a gateway or proxy received an erroneous response from its upstream server (often called the origin).
#1 Best Overall
Typical request flow looks like this:
- Your browser sends a request.
- A CDN, load balancer, or reverse proxy receives it.
- The gateway forwards the request to the origin (and possibly other services like an API or cache).
- If the origin (or an intermediate hop) fails or returns something the gateway can’t use, the gateway sends back 502.
Common causes of Error 502
Most 502 errors fall into a handful of categories. Pinpointing which one you’re dealing with depends on whether you’re a visitor or responsible for the site.
Origin server issues
If the origin server is down, overloaded, misconfigured, or returning broken responses, the gateway can’t complete the request.
- Application crashes (e.g., container restarted, process exited)
- Database failures causing upstream to hang or error
- Bad deployments (new build breaks a route)
- Resource exhaustion (CPU pegged, memory pressure, thread pool starvation)
Reverse proxy / gateway problems
Even if the origin is healthy, the gateway can still produce 502 if its configuration or behavior is wrong.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Incorrect upstream address or port in
nginx,HAProxy, or a cloud load balancer - Upstream returns headers/status codes the gateway doesn’t accept
- Bad health check configuration marks upstream “down”
- Header size limits or malformed headers
CDN or edge network interruptions
CDNs add speed, but they also introduce another layer that can fail.
- Edge can’t reach origin (routing, firewall, or peering issues)
- Origin timeouts increase when traffic spikes
- Misconfigured cache rules forward requests incorrectly
- Certificate or SNI issues at the edge
DNS and routing problems
If DNS records or routing change unexpectedly, gateways may attempt connections that fail or go to the wrong place.
- Outdated DNS cache pointing to decommissioned IPs
- Wrong CNAME/A records for the origin
- Load balancer target group misrouting
- Asymmetric routing causing connection resets
TLS/SSL handshake failures
Gateways talk to upstream using HTTPS more often than you might think. Any TLS failure can surface as 502.
Rank #2
- Certificate expired or doesn’t match hostname (SNI mismatch)
- Unsupported cipher suites between components
- Intermediate CA missing
- Upstream requires client certificates, but gateway doesn’t present them
Network timeouts and overload
Timeouts are a top cause because 502 happens when the gateway gives up.
- Origin takes too long to respond (slow app, slow DB, network latency)
- Gateway upstream timeout too low for real workload
- Too many concurrent connections exhaust connection pools
- Limits hit (max request body size, max connections, rate limiting)
Authentication and session mismatches
This is less common, but can trigger 502 if an upstream service fails during auth flows.
- Bad token forwarding causing upstream to reject requests repeatedly
- Misconfigured OAuth callbacks leading to loops and eventual gateway failure
- Session store outages (Redis/Memcached) causing upstream to fail
How to troubleshoot Error 502 (user/client side)
If you’re just trying to access a site, you usually can’t fix the server. Your job is to determine whether the problem is local or server-side—and gather evidence that helps support teams.
Basic browser checks
Start with the fastest, reversible steps.
- Hard refresh the page (Ctrl+F5 on Windows/Linux, Cmd+Shift+R on macOS).
- Try an Incognito/Private window to rule out extensions.
- Clear site data for the domain (cookies and cache).
- Check if the error appears on every page of the site or only specific URLs.
Test from another network/device
If it works elsewhere, it’s likely a local network, DNS, or security product issue.
- Use a different Wi‑Fi network or switch to mobile data.
- Try another device on the same network.
- Compare results across browsers (Chrome, Firefox, Safari, Edge).
Check local DNS and connectivity
DNS issues can make you hit an unreachable or wrong upstream path.
- Restart your modem/router once, then re-test.
- Flush DNS cache (examples below) and reload.
- On macOS: open Terminal and run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. - On Windows: open Command Prompt as admin and run
ipconfig /flushdns.
Disable interfering software
Security tools and ad blockers can interfere with requests, especially when they modify HTTPS traffic.
Rank #3
- Temporarily disable VPN/proxy.
- Disable ad blockers and “HTTPS inspection” in security suites.
- If you run custom DNS, try default DNS from your network and re-test.
When it’s clearly server-side
Common signs the origin is failing: multiple people report it, it affects many URLs, and retries don’t help for minutes.
- Check a second connection or device to confirm it’s not local.
- Try again after 5–15 minutes—deployments and autoscaling can take time.
- If you manage the site, capture the exact URL, time, and error text for logs correlation.
How to troubleshoot Error 502 (site owner/server side)
If you run the service, treat Error 502 as a symptom. The real work is tracing which hop returned failure and why.
Inspect logs and correlate timestamps
Start with evidence. Compare gateway logs with origin and upstream service logs around the failure window.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Identify the exact timestamp of the 502 (including timezone).
- Search gateway/reverse proxy logs for the upstream host and request ID.
- Check origin logs for matching requests, errors, and timeouts.
- Look for spikes in 5xx/4xx, connection resets, and upstream response time.
Verify upstream health (origin and services)
Most gateway 502s occur because the upstream dependency isn’t healthy.
- Confirm the origin process is running (containers/VMs not restarting).
- Check application health endpoints (e.g.,
/healthzor/status). - Verify database connectivity and response time.
- Validate cache availability (Redis/Memcached) and eviction behavior.
Check reverse proxy configuration
Configuration mistakes can be surprisingly subtle. Validate these common areas:
- Upstream target: hostnames, ports, and weights
- Timeouts: connect, read, and send timeouts
- Body limits: max request size
- Header handling: large headers, missing required headers
If you use nginx, typical settings include proxy_connect_timeout, proxy_read_timeout, and proxy_pass. If you use HAProxy, check backend server checks and timeout connect/timeout server.
Validate CDN and load balancer settings
When a CDN is present, confirm the chain of trust and routing from edge to origin.
- Confirm origin hostname/SNI matches the origin certificate.
- Check firewall rules and allowlists for edge IP ranges.
- Review load balancer target group health checks and thresholds.
- Verify cache/origin request policies (especially for authenticated paths).
Monitor timeouts, keep-alives, and limits
Timeouts and connection management are frequent triggers during traffic spikes or dependency slowdowns.
- Connection pool exhaustion can cause new requests to fail quickly.
- Keep-alive misconfiguration can create stale connections.
- Rate limits may throttle upstream calls, leading to gateway timeouts.
Practical move: temporarily increase upstream/read timeouts only if your SLOs and capacity plan allow it; otherwise, you may just mask a deeper performance issue.
Test the upstream path directly
Skip the gateway for a moment to isolate the upstream.
- From a server in the same network, request the origin endpoint directly.
- Measure response time and confirm status codes.
- If upstream requires headers (Host, Authorization), include them to match real traffic.
- Repeat during the 502 window to catch transient failures.
When using curl, you’ll often want to test with the expected -H "Host: example.com" header if the origin routing depends on it.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Common variants you might see
Different platforms display slightly different messages, but the underlying meaning usually stays the same. The table below helps you connect the message to a likely failing hop.
Best Value
| Message variant | What it often indicates |
|---|---|
| 502 Bad Gateway | Gateway/proxy received invalid response from upstream |
| Web server is returning an unknown response | Upstream sent malformed headers/body or protocol mismatch |
| Bad Gateway (cloud/load balancer name) | Load balancer can’t reach target or target returned failure |
| 502 Proxy Error | Forward proxy or reverse proxy upstream connection failed |
| 502 Service Temporarily Unavailable | Often overload/timeouts (less precise wording) |
Preventing Error 502 going forward
Prevention is mostly about resilience: capacity, health checks, safe deployments, and fast detection.
Operational safeguards
- Use circuit breakers or graceful degradation when upstream dependencies fail.
- Set realistic timeouts and ensure they align with your p95/p99 latency.
- Use connection pooling correctly and avoid per-request TLS overhead where possible.
- Keep health checks meaningful (not just “process is up”).
Observability and alerting
- Alert on error rate (5xx), upstream latency, and gateway-specific 502 counts.
- Track saturation signals: CPU, memory, DB connections, queue depth.
- Use request IDs/tracing so you can jump from a 502 to a failing upstream call.
Deployment and rollback discipline
- Roll out gradually (canary/blue-green) so 502 doesn’t hit everyone at once.
- Have an automated rollback when 502 spikes beyond a threshold.
- Validate environment variables, secrets, and certificate chains before switching traffic.
FAQs
Is Error 502 the same as Error 503?
No. 502 means a gateway/proxy got a bad response from upstream. 503 typically means the service is temporarily unavailable—often due to maintenance or overload—without necessarily blaming an upstream gateway response.
Can Error 502 be caused by my internet connection?
It can, but it’s less common. If DNS is wrong, a VPN/proxy interferes, or a security product breaks HTTPS, you can end up triggering failures that look like 502. Testing another network usually clarifies this.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →How long should I wait before assuming it’s server-side?
If the issue persists across multiple devices/networks for more than 5–15 minutes, it’s likely server-side. If it clears quickly, it may have been a transient upstream timeout, deployment, or autoscaling event.
What should I report to website support when I see 502?
Send the full URL, the time you saw it (with timezone), your browser/device, whether it affects all pages or only one, and whether it happens on a different network or mobile data.
For site owners, where do I start if 502 starts suddenly after a deploy?
Compare gateway and origin logs around the deploy timestamp, verify upstream health checks, and check if any dependency changed (DB credentials, environment variables, TLS config, routing rules, or upstream timeouts).
Bottom Line
Error 502 isn’t a “you” problem in most cases—it’s a sign that a gateway couldn’t get a valid response from upstream. The quickest fix depends on narrowing whether the failure is local (DNS/VPN/extensions) or server-side (origin health, timeouts, TLS, proxy/CDN config).
If you manage the site, treat 502 as a tracing problem: correlate timestamps, verify upstream health, validate gateway/CDN configuration, and tighten monitoring so you catch the first moment the chain breaks.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
