You’re online but pages won’t load? DNS, cache, bad time, or blocked traffic are common—try a reboot, flush DNS, and test in another browser.
Nothing’s more annoying than seeing Wi-Fi bars or a live Ethernet icon while every tab spins. The good news: this problem follows repeatable patterns. Work through the quick checks below, then move into fixes that clear bad data, refresh name lookups, and repair the connection stack. The steps are safe and take only a few minutes. Today.
Pages won’t load while connected to internet: quick fixes
Start with fast, low-risk checks. These tell you whether the snag lives in the browser, on your device, in the router, or upstream with the provider.
| Symptom | What it points to | Quick test |
|---|---|---|
| Only one site fails | DNS or site outage | Try a different device or mobile data |
| All sites fail on one device | Local settings or cache | Open a private window, then reboot the device |
| All devices fail | Router or provider issue | Power-cycle the router for 60 seconds |
| Login page pops on public Wi-Fi | Captive portal | Open a new tab and visit http://neverssl.com |
| Lock or clock errors | Time mismatch or TLS | Check date, time, and region settings |
| Pages load in one browser only | Extension or profile issue | Try private mode with extensions disabled |
| Works on hotspot but not home | DNS or router rules | Switch DNS servers and test again |
Rule out the basics
Toggle airplane mode or unplug and reattach Ethernet. Reboot the device. Restart the router and modem: unplug for a full minute, plug back in, and wait for lights to stabilize. If you’re on café or hotel Wi-Fi, open a new tab and visit a plain http site to trigger the login page. Set your system clock to auto and verify time zone. Try a second browser; if that works, the issue is browser-specific.
Clear bad data: cache, cookies, and DNS
Old cache and cookies can stale a session or loop a redirect. Clear site data for the troubled domain, or run a full browser clean. Next, refresh DNS—the address book that turns names into IPs. A quick flush forces new lookups and often fixes mysterious timeouts.
Flush DNS quickly
Windows: open Command Prompt as admin and run ipconfig /flushdns. macOS: run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal. On Chrome, visit chrome://net-internals/#dns and click “Clear host cache.” Reopen the tabs and test again.
Clear the browser’s temp data
In Chrome, press Ctrl+Shift+Del (Cmd+Shift+Del on Mac) and clear cached images, files, and cookies for the time range that includes your last visit. In Firefox, use Settings → Privacy & Security → Cookies and Site Data → Clear Data. Sign back into the site after the refresh.
Switch DNS to a reliable resolver
If name lookups fail, try public resolvers. Set DNS to 1.1.1.1 and 1.0.0.1, or 8.8.8.8 and 8.8.4.4. On Windows 11: Settings → Network & Internet → Wi-Fi or Ethernet → Hardware properties → Edit DNS. On macOS: System Settings → Network → Wi-Fi → Details → DNS. Test the same site after saving the change. If pages now load, your previous DNS was the culprit.
For step-by-step browser fixes, see Mozilla’s guide to fixing website errors. For Windows socket and TCP/IP rebuild steps, see the Microsoft Learn page on resetting TCP/IP.
Reset the network stack on Windows
Corrupt network components can block traffic even when the link stays up. On Windows, open an elevated Command Prompt and run netsh winsock reset, then netsh int ip reset. Reboot. These commands rebuild sockets and TCP/IP defaults; you may need to reapply any custom adapter tweaks afterward.
Watch for browser error clues
Browser messages point straight at root causes. “ERR_NAME_NOT_RESOLVED” points to DNS. “Your connection is not private” paired with a date warning points to clock or certificate issues. “SEC_ERROR_EXPIRED_CERTIFICATE” means the site’s certificate is out of date or blocked by a filter. Note the exact text; it speeds up fixes.
Rule out proxy or odd LAN settings
A stuck proxy breaks every page. On Windows, open Internet Options → Connections → LAN settings and uncheck proxy unless your office requires one. On macOS, open System Settings → Network → Wi-Fi → Details → Proxies and turn off any entries you did not set. In Chrome, type chrome://settings/system and make sure the proxy switch isn’t forcing a path you don’t need.
Test with ping, traceroute, and name lookups
Open a terminal and try ping 1.1.1.1. If you get replies, the link passes raw traffic. Run ping google.com. If numbers fail but names fail too, DNS is likely. Use nslookup example.com or dig example.com to see the DNS answer. Run tracert on Windows or traceroute on Mac and Linux to see where packets stop.
Tame extensions and browser profiles
Ad blockers, privacy tools, and old plugins can block entire domains. Disable all extensions, test, then re-enable one by one. If the issue sticks to a single profile, create a new browser profile and test there. If the new profile works, export bookmarks and move over only what you need.
Time, certificates, and HTTPS warnings
TLS depends on correct time. If the system clock drifts by hours or years, certificate checks will fail. Turn on automatic time and region. Sync time once, then reload the tab. If only one site shows a certificate warning, the site may truly be expired; test on another device before proceeding.
Hosts file, DNS filters, and parental tools
Entries in the hosts file can force domains to wrong addresses. Check C:\Windows\System32\drivers\etc\hosts on Windows or /etc/hosts on Mac and Linux for lines that point domains to 0.0.0.0 or 127.0.0.1. DNS filter apps and routers with parental controls can block categories or entire TLDs. If that fits your setup, allow the domain temporarily and test again.
IPv6 and IPv4 toggles
Some networks advertise IPv6 but route it poorly. On Windows, open adapter properties and briefly untick IPv6, then test. On macOS, in Wi-Fi Details → TCP/IP, set Configure IPv6 to Link-local only and try again. If pages start loading, leave the tweak or ask your provider about IPv6 quality.
Android and iPhone quick wins
Toggle airplane mode for ten seconds. Forget and rejoin the Wi-Fi network. Change DNS to 1.1.1.1 and 1.0.0.1 under the network’s DNS settings. On Android, reset network settings under System → Reset options. On iPhone, go to Settings → General → Transfer or Reset → Reset → Reset Network Settings. As always, test on mobile data to separate device issues from Wi-Fi issues.
Edge cases that waste time
VPN split tunneling: traffic for certain sites may route through a slow tunnel. Toggle split tunneling off and retry. Enterprise filters: some workplaces block cloud storage, code hosts, or social sites; try a personal connection. Large system updates: background downloads can saturate the link; pause them while testing. Weird MTU on PPPoE links: if only large pages stall, ask the provider about MTU and try 1492 on the router.
Renew the IP lease
Your device may hold a stale address. On Windows, run ipconfig /release then ipconfig /renew. Follow with ipconfig /flushdns. On macOS, open Wi-Fi Details → TCP/IP and click Renew DHCP Lease. If the page loads right after the lease refresh, the old address or gateway was the blocker.
Reinstall or update the network adapter
Open Device Manager, expand Network adapters, right-click your Wi-Fi or Ethernet device, and choose Uninstall device. Reboot and Windows will load a driver. If you have a vendor tool, install the newest driver. On Mac, apply the latest system update; that refreshes networking components as well.
Handy paths and commands
| Platform | Menu path | Command or tool |
|---|---|---|
| Windows 11 | Settings → Network & Internet → Advanced network settings → Network reset | netsh winsock reset |
| Windows 10 | Settings → Network & Internet → Status → Network reset | ipconfig /flushdns |
| macOS | System Settings → Network → Wi-Fi → Details → DNS | sudo killall -HUP mDNSResponder |
Check firewalls, VPNs, and filters
Security suites, firewall rules, and VPN clients can block domains or deny new DNS. Pause the VPN and test. If you use a firewall app, create a rule that allows your browser and DNS. Re-enable protections once you finish the check.
Router and provider checks
If every device stalls, shift to the router and the line. Confirm the WAN light is steady, then review router logs for DNS failures. Temporarily set the router’s DNS to 1.1.1.1 and 8.8.8.8. If you can browse on a phone’s hotspot but not through the router, the issue lives on your LAN or router. If nothing loads on any line, contact the provider from a phone.
When only one site won’t load
Test the site on mobile data and a second device. If it loads elsewhere, the site isn’t down; your device stored something stale. Clear DNS and cookies for that domain. Run nslookup example.com and confirm the answer is an IP, not NXDOMAIN. If only your network fails to reach the site, a blocklist or parental filter may be at play.
Keep it running smooth
Update the browser and the operating system, keep extensions lean, and avoid stacking multiple security tools. Use automatic time and region. Leave DNS on dependable resolvers or on the router. Every so often, reboot the router to refresh the link and renew leases.