502 Bad Gateway in Chrome
Check a 502 Bad Gateway in Chrome by separating local browser or network symptoms from a real website-side gateway outage.
Start here
Quick Answer
Chrome is usually displaying a 502 generated by the website, proxy, CDN, or origin server. Reload once, test Incognito, another browser, and another network, then stop local troubleshooting if the same URL fails everywhere. Use the parent 502 diagnostic path for public outages; switch to DNS_PROBE_FINISHED_NXDOMAIN or Aw, Snap! if Chrome shows a browser-generated error instead.
When to use this Chrome page
Use this page when Chrome displays a visible 502 Bad Gateway. Chrome is usually not the cause; it is showing a response from a gateway, CDN, load balancer, reverse proxy, or origin. The useful Chrome task is scope-checking: prove whether the problem is local to one browser/profile/network or public for everyone.
Local vs website outage checks
| Result | Likely meaning | Next path |
|---|---|---|
| Only normal Chrome fails | Profile data, extension, cache, service worker, or cookie state | Stabilize Chrome |
| Chrome and other browsers fail on one network | Network, VPN, proxy, resolver, or edge routing issue | Compare resolvers |
| Every browser and network returns 502 | Website-side gateway, CDN, origin, or upstream outage | 502 Bad Gateway diagnosis |
| Chrome shows DNS_PROBE_FINISHED_NXDOMAIN instead | DNS resolution failure, not a real HTTP 502 | DNS_PROBE_FINISHED_NXDOMAIN |
Safe visitor steps
- Reload once. Do not repeatedly resubmit checkouts, forms, or admin actions.
- Open the URL in Incognito and then in another browser.
- Try another network, such as mobile data, if the page matters and you can test safely.
- Clear site data or DNS cache only when the issue is isolated to Chrome or one network.
- If the same 502 appears everywhere, stop local fixes and report evidence.
What to report
URL:
Time and timezone:
Exact error text:
Chrome version or device:
Network tested:
Did Incognito work:
Did another browser work:
CDN or request ID shown:If you own the site, move from this visitor page to the parent 502 diagnostic path or the platform-specific nginx or WordPress page. If you are only visiting the site, these details are usually the most useful action you can take.
Diagnosis
Symptoms
- Chrome shows 502 Bad Gateway, Bad Gateway, or a CDN-branded 502 page.
- The same URL may work in another browser, profile, device, or network if local Chrome state is involved.
- If every browser and network sees 502, the failure is almost certainly website-side.
Common causes
- The website gateway, CDN, load balancer, reverse proxy, or upstream app returned the 502.
- Chrome has stale site data, cached redirects, a service worker, or extension behavior that makes one site appear broken.
- A VPN, workplace proxy, DNS resolver, or local network path reaches a different edge or origin state.
- The site is down for everyone and only the website owner, host, or CDN provider can fix it.
Diagnostic Checklist
- Reload once and avoid resubmitting forms or checkouts repeatedly.
- Open the URL in Incognito and another browser.
- Try another network, such as mobile data, if available.
- Clear site data or DNS cache only if the failure is isolated to Chrome or one network.
- If every test returns 502, report the URL, timestamp, browser, network, and any CDN request ID to the site owner.
Fixes
Confirm whether Chrome is the only failing path
- 5 minutes
- Risk: low
- Anyone
- Chrome, Browser
Avoid unnecessary browser cleanup when the website is returning a public 502.
- Reload the page once.
- Open the same URL in Incognito.
- Open the same URL in another browser or device.
- Compare the exact error text and whether the page is CDN-branded.
You know whether the 502 is limited to Chrome, one profile, one device, or all visitors.
If all browsers fail, stop Chrome fixes and treat it as a website-side 502.
Keep the failing URL and timestamp for reporting.
No rollback is needed for this read-only check.
Clear only local state when evidence points local
- 10 minutes
- Risk: low
- Anyone
- Chrome, DNS
Use targeted cleanup only after Chrome-specific or network-specific symptoms appear.
- Clear site data for the affected domain rather than all browser data.
- Disable extensions that modify requests, block scripts, or inspect traffic.
- Flush DNS cache or switch networks if only one resolver path fails.
- Restart Chrome and test the exact URL again.
The page loads or the failure changes to a more specific DNS, connection, or server response.
If the same 502 remains in every clean test, the website owner must fix the server side.
Retest Incognito, normal Chrome, and another browser.
Re-enable extensions that were not involved.
Platform notes
Chrome can help you prove scope, but it usually cannot fix a server-generated 502. If the same URL returns 502 in another browser and network, use the parent 502 Bad Gateway diagnostic path or send the evidence to the site owner.
FAQ
Can I fix a 502 Bad Gateway from Chrome?
Only when the failure is caused by local Chrome state, DNS cache, extensions, VPN, or proxy behavior. Most 502 responses require the website owner or host to fix the gateway or upstream.
Should I clear all browsing data?
No. Start with Incognito and another browser. Clear site data only for the affected site when the problem is isolated to Chrome.
What should I report to the site owner?
Send the full URL, timestamp and timezone, the exact error text, your browser, network, whether another browser worked, and any request ID shown by the CDN or error page.
Review notes
- Last reviewed
- 2026-05-05
- Reviewed by
- FaultForge Editorial Team, Web operations reviewer
- Tested on
Chrome Incognito checks, alternate browser and network comparison, targeted site-data cleanup, DNS cache checks, and public 502 outage scope verification.