FaultForge

Platform

Chrome Troubleshooting

Fix Chrome loading problems such as Aw, Snap!, DNS failures, and server errors shown in Chrome by checking extensions, cache, profiles, networks, and outage scope.

Chrome loading vs site errors

Chrome can show browser-level loading errors even when the website is healthy. It can also display server errors that no Chrome setting can fix. Separate local browser/profile issues from DNS and HTTP problems before clearing data or asking a site owner to change servers.

SymptomLikely issueNext path
Aw, Snap!Browser/profile/extension/cache/device issueAw, Snap! in Chrome
DNS_PROBE_FINISHED_NXDOMAINDNS resolution failureDNS_PROBE_FINISHED_NXDOMAIN
Chrome displays 502 Bad GatewayUsually website-side; Chrome helps prove scopeChrome 502 checks
Only one site shows 500 or 502Server-side issueHTTP errors
Works in another browserChrome profile, cache, extension, or settingStabilize Chrome

Local checks

Test Incognito, disable extensions, create a temporary profile, clear site data for only the affected site when possible, and toggle hardware acceleration if crashes continue. If every browser and network sees the same server status code, stop Chrome-specific changes and move to HTTP or DNS diagnosis.

Related hubs

Use DNS errors for resolver problems and HTTP errors for server responses. That keeps Chrome fixes focused on browser behavior and avoids overclaiming local steps for origin outages.

Quick local checklist

  • Works in Incognito: suspect extension, cookie, cache, or profile data.
  • Works in another Chrome profile: suspect the original profile or synced settings.
  • Works in another browser but not Chrome: keep troubleshooting Chrome before changing the site.
  • Fails in every browser and network: move to DNS or HTTP diagnosis.

When the website owner must act

A visitor cannot fix a server-side 500, 502, expired origin certificate, blocked CDN origin, or broken DNS zone. The best UX is to report the exact error wording, URL, time, network, and whether another browser or device worked. That gives the site owner useful evidence without asking visitors to run server checks.

If the same URL fails for multiple people in different browsers, stop clearing Chrome data and hand the evidence to the site owner or hosting team.

Errors

Aw, Snap! in Chrome

Fix Chrome Aw, Snap! crashes by isolating extensions, profile corruption, cache issues, hardware acceleration, and device-specific problems.

DNS_PROBE_FINISHED_NXDOMAIN

Resolve DNS_PROBE_FINISHED_NXDOMAIN by checking domain records, nameservers, resolver cache, DNS propagation, and browser/network settings.

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.

Guides