You open Chrome. You type the URL. You hit enter. And then... nothing. Or a spinning wheel. Or a wall of red text telling you the connection failed. Whatever the exact message, the frustration is the same. Your browser is broken and you need it working five minutes ago.
Here's the good news: in my years running a help desk, I've seen hundreds of browser error tickets. Almost every one of them traces back to one of three causes. Sometimes it's two of them stacked together, which is why people give up and reinstall Windows. Don't do that. Work through these in order and you'll solve it.
Cause #1: Stale or corrupted browser cache
This is the big one. If I had to guess, I'd say 60% of browser errors I've handled came down to a cache that went bad. Browsers store local copies of pages, scripts, images, and cookies so they load faster next time. Problem is, when a site updates its code but your browser still serves the old cached version, things break in weird ways. You get blank pages, half-loaded layouts, login loops, or an error that only happens on one specific site.
A real-world example: a client called me because their company's HR portal showed a white screen in Chrome but worked fine in Edge. Classic cache issue. Chrome had cached a broken JavaScript file from the previous week, and the new version never got fetched. Clearing cache fixed it in 30 seconds.
How to clear cache in Chrome, Edge, and Firefox
- Open the browser and press
on Windows orCtrl + Shift + Delete
on Mac.Cmd + Shift + Delete - A dialog box appears. In Chrome and Edge, set "Time range" to All time. In Firefox, set it to Everything.
- Check these boxes: Cookies and other site data, Cached images and files.
- Leave "Passwords" and "Autofill" unchecked unless you want to lose saved logins.
- Click Clear data. The button is usually blue.
After clicking Clear data, you should see the dialog close and the browser may log you out of sites like Gmail. That's expected. Reload the page that was erroring out. If it works, you're done. If it doesn't, move on.
Tip: If only one site is broken, you don't need to nuke everything. Click the padlock icon next to the URL, then "Cookies and site data," and delete just that site's data. Faster and less disruptive.
Cause #2: A rogue browser extension
Extensions are mini-apps that plug into your browser. Ad blockers, password managers, coupon finders, PDF viewers, that one thing your coworker told you to install three years ago. Most are fine. Some are actively hostile to your browsing experience. And you probably have more installed than you realize.
Here's the tell: if you get a browser error and it only happens in one browser (Chrome but not Firefox), and clearing cache didn't fix it, extensions are suspect number one. I've seen ad blockers nuke legitimate sites, VPN extensions break banking portals, and security extensions intercept every request and time out.
Test with extensions disabled
- In Chrome or Edge, click the three-dot menu, then Extensions, then Manage extensions.
- Toggle every extension off using the switches. Don't uninstall yet — just disable.
- Reload the failing page. If it works now, an extension is your culprit.
- Turn extensions back on one at a time, reloading the page after each. The one that breaks it is the problem.
In Firefox, the fastest test is Safe Mode. Click the hamburger menu, then Help, then Troubleshoot Mode. Firefox restarts with all extensions off. If your error vanishes, same drill — re-enable one at a time.
Once you find the bad extension, remove it entirely. Don't just disable it. Extensions that misbehave once will misbehave again after the next update.
Cause #3: DNS or network resolution problems
If cache and extensions are clean but you're still getting errors like
ERR_NAME_NOT_RESOLVEDERR_CONNECTION_TIMED_OUTDNS_PROBE_FINISHED_NXDOMAINReal-world trigger: this one hits hard after switching networks. You close your laptop at the office, drive home, open it on your home Wi-Fi, and suddenly half your tabs throw DNS errors. The old DNS cache is still pointing at the office network's resolver, which you can't reach anymore.
Flush your DNS cache
On Windows, open Command Prompt as administrator and run:
ipconfig /flushdns
ipconfig /release
ipconfig /renewYou should see "Successfully flushed the DNS Resolver Cache." After the renew command, your IP and gateway info reappears. Close the terminal and reload the page.
On macOS, the command changed in Big Sur and later:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderYou'll be prompted for your password. Type it (nothing shows on screen, that's normal), hit enter. No output means success.
On Linux with systemd-resolved:
sudo systemd-resolve --flush-cachesIf DNS flush doesn't fix it, switch DNS providers
Sometimes your ISP's DNS servers are just slow or down. Point your machine at Cloudflare or Google instead.
- Open Settings, then Network & Internet, then Wi-Fi (or Ethernet).
- Click your active network, then scroll to DNS server assignment and click Edit.
- Change from Automatic to Manual, turn on IPv4.
- Enter
as preferred and1.1.1.1
as alternate.1.0.0.1 - Click Save. You should see the DNS field update immediately.
Cloudflare's resolver is fast and doesn't log your queries. Google's
8.8.8.8One more thing on this layer: reboot your router. Yes, I know, it's a cliché. But routers cache DNS too, and a 30-second power cycle clears it. Unplug the power, wait 30 seconds, plug it back in, wait two minutes for it to fully boot. Do this after flushing your computer's cache or you'll just re-cache the bad result.
Quick reference: match the error to the fix
| Error message | Most likely cause | First fix to try |
|---|---|---|
| Blank page, half-loaded layout | Stale cache | Clear cache (Ctrl+Shift+Del) |
| Works in Firefox, breaks in Chrome | Extension conflict | Disable all extensions, re-enable one by one |
| ERR_NAME_NOT_RESOLVED | DNS failure | ipconfig /flushdns |
| DNS_PROBE_FINISHED_NXDOMAIN | DNS failure | Switch DNS to 1.1.1.1 |
| ERR_CONNECTION_TIMED_OUT | DNS or network | Flush DNS, reboot router |
| ERR_CONNECTION_RESET | Extension or firewall | Disable extensions, check firewall |
| Login loops on one site | Bad cookies | Delete cookies for that site only |
| Every site broken | Network or DNS | Flush DNS, reboot router |
Start at the top of the list, work down, and don't skip steps. The number of tickets I've closed by just clearing cache would embarrass the people who opened them. And if all three of these fail, try a different browser entirely. If the page loads in Edge but not Chrome, you've narrowed it to a Chrome-specific problem — probably a profile issue, which is a reinstall of Chrome itself, not your whole OS.