When Chrome can’t open sites, start with connection checks, disable add-ons, clear cache, test DNS, then reset settings as needed.
If tabs spin forever or pages error out while other apps work, don’t panic. The problem usually lives in one of four places: your connection, your browser data or add-ons, system networking (DNS, proxy, firewall), or a corrupted profile. This guide gets you from “nothing loads” to “back online,” with clear steps for Windows, macOS, and ChromeOS.
When Chrome Fails To Open Sites: Quick Wins
Start with low-effort checks that solve a surprising number of stuck pages. Work top to bottom; stop when the web starts working again.
| Symptom | Quick Fix | Where |
|---|---|---|
| Only one site won’t load | Hard refresh, then clear cookies for that site | Shift+Reload; Settings → Privacy & security → Cookies and other site data → See all site data |
| All sites timeout or show “This site can’t be reached” | Toggle Wi-Fi off/on, reboot router, test another network (hotspot) | OS network menu; router |
| Pages load in another browser, not in Chrome | Disable all extensions; try Incognito | Menu → Extensions; Ctrl/Cmd+Shift+N |
| Endless loading after an update or crash | Restart the browser; update to the latest build | Menu → Help → About Google Chrome |
| Some sites error; others work | Switch DNS to a reliable provider, then retry | OS network settings |
| Nothing loads on Wi-Fi but works on Ethernet (or vice versa) | Forget and rejoin the Wi-Fi; renew DHCP; test another profile | OS network settings; Chrome profile menu |
| “ERR_CONNECTION_RESET” or random resets | Reset Winsock/TCP stack (Windows) | Command Prompt (admin) |
| Corporate/VPN networks | Turn off VPN/proxy to test; check firewall rules | VPN app; OS proxy settings; security suite |
Rule Out A Bad Connection First
Open a different browser and try the same site. If it fails everywhere, the issue likely sits with your internet path. Power-cycle the router, try a phone hotspot, and check whether other devices in the home can reach the web. If only Chrome misbehaves, keep going.
Kill The Hidden Gremlins: Cache, Cookies, And Add-Ons
Do A Focused Clean
Stale cookies or cached files often block logins and scripts. Clear data for the broken site first so you don’t lose session data across everything. If that fails, clear cached images and files for a broad reset while keeping passwords intact. This often fixes layout loops and half-loaded pages.
Test Without Extensions
Open an Incognito window and try the page. If it loads there, an extension is the likely culprit. Disable all add-ons, then re-enable one at a time to find the breaker. Ad blockers, privacy tools, and shopping helpers are frequent causes when scripts conflict.
Restart And Update
Quit Chrome fully, reopen, and check Menu → Help → About Google Chrome for updates. A quick restart clears stuck processes, and the latest build often contains networking fixes.
Fix Name Lookups: DNS Settings That Actually Help
When the address bar can’t turn a site name into an IP, pages won’t load. Switching DNS can resolve that in seconds. On Windows or macOS, set DNS servers at the adapter level. Use providers known for uptime and speed. If nothing changes, switch back; you’re only changing resolvers, not your plan.
On Mac, the path is System Settings → Network → (your network) → Details → DNS. Add new servers, move them to the top, and apply. Apple documents this flow on its help pages, which is useful if the menu labels moved after an update. On Windows 11, you can adjust DNS in adapter properties or via the new Settings panels.
Check Proxies, VPNs, And Firewalls
Chrome follows system proxy settings on desktop. If a proxy or VPN is set but unreachable, tabs will spin and then fail. Turn off the VPN temporarily. In system settings, open the proxy panel and make sure no stale auto-config URL or SOCKS entry is left behind. Security suites can also block connections; toggle their web shields off for a minute to test, then re-enable and add an allow-list entry if needed.
Reset The Network Stack On Windows
Network stacks on Windows can get jammed after driver changes, VPN installs, or malware removal. A Winsock reset refreshes the catalog of network providers, which clears many ERR_CONNECTION_RESET and “site can’t be reached” errors. Run Command Prompt as admin and execute:
netsh winsock reset
netsh int ip reset
Reboot and test Chrome again. This small reset is safe and reversible and comes straight from Microsoft’s command reference.
Repair The Browser Without Losing Your Stuff
Restore Defaults
If settings drift caused the problem, use Chrome’s built-in reset to restore startup pages, search, content permissions, and temporary data. Bookmarks, history, and saved passwords stay untouched. After the reset, sign-ins may prompt again, which is expected.
Create A Fresh Profile
Corrupted user data can block page loads in odd ways. Add a new person from the profile menu and try the same sites. If the new profile works, move bookmarks and passwords over and retire the old one.
OS-Specific Steps That Solve Stubborn Cases
Windows Tips
- Network reset: Settings → Network & Internet → Advanced network settings → Network reset. This reinstalls adapters and clears old configs.
- Driver refresh: Update the Wi-Fi/Ethernet driver from Device Manager if recent changes caused drops.
- Hosts file: Confirm no stray entries for common sites in
C:\Windows\System32\drivers\etc\hosts.
macOS Tips
- Remove and re-add the network service in System Settings → Network, then reconnect.
- DNS order: Place your preferred resolvers first; delete old ones left by VPN clients.
- Keychain items: If only certain domains fail with certificate prompts, delete stale website certificates and reconnect.
ChromeOS Tips
- Wi-Fi hops: Forget and rejoin the network, then toggle Allow proxies for shared networks off unless required.
- Guest session: Test in Guest to isolate profile issues. If Guest works, reset the main profile’s settings.
Map The Error To The Right Fix
Match what you see on the error page to a targeted action. Use this table when you need a quick nudge in the right direction.
| Error Or Message | Best Next Step | Why It Helps |
|---|---|---|
| “This site can’t be reached” / DNS_PROBE_FINISHED_NXDOMAIN | Switch DNS on the OS; flush cache; retry | Fixes broken name lookups that stop pages at the first hop |
| ERR_CONNECTION_RESET | Run Winsock/TCP resets; test without VPN | Clears corrupt providers and unstable tunnels |
| ERR_SSL_PROTOCOL_ERROR | Set system time, clear site cookies, disable intercepting proxies | Bad clocks and MITM proxies break TLS handshakes |
| ERR_TIMED_OUT | Restart router, test Ethernet vs Wi-Fi, change DNS | Helps when upstream routing or Wi-Fi quality is poor |
| Aw, Snap! | Update Chrome, disable hardware acceleration, check RAM | Stability fixes prevent renderer crashes |
| Only one domain fails after login | Clear cookies for that domain; try Incognito | Removes looped sessions and broken auth tokens |
A Short, Proven Sequence (10 Minutes)
- Open the page in another browser. If that also fails, test another network. If the web works elsewhere, keep going.
- Incognito test. If the page loads, disable all extensions and re-enable one by one.
- Clear cached images/files and cookies for the site that fails.
- Restart Chrome; check for updates.
- Switch DNS on the OS to a known reliable resolver; retry.
- Turn off VPN/proxy; confirm no leftover proxy entries at the OS level.
- On Windows, run the two reset commands shown earlier; reboot.
- Reset Chrome settings. If that works, export and rebuild from a clean profile.
When It’s Not Chrome At All
Some outages live outside your machine. If multiple devices on the same network can’t reach a site, check the vendor’s status page or a public outage map. If only large media or cloud services fail, the issue may be upstream. Keep your notes: time of day, ISP, whether the issue appears on mobile data. That information speeds up support calls.
Prevention: Keep Browsing Smooth
- Audit extensions every few months; prune anything you don’t rely on.
- Update the browser and OS regularly. Patches include networking fixes.
- Use a quality DNS provider on the router so every device benefits.
- Avoid stacking multiple VPNs, firewalls, and proxies at once.
- Back up your profile items (bookmarks, passwords) with a password manager. If a profile breaks, you can rebuild fast.
Helpful References
You can find Chrome’s official guidance on fixing connection and loading problems in the Google Help Center. For Windows networking rebuilds, Microsoft’s command reference documents the Winsock reset in detail. Both links open in a new tab:
Still Stuck? Use A Clean Profile As A Last Step
If none of the steps worked, create a fresh browser person and sign in. Move only essentials: bookmarks and passwords. If the new profile loads pages instantly, the old one carried the problem. Keep the fresh one and reinstall only trusted add-ons.