This Site Can't Be Reached: Complete Troubleshooting Guide (2025)

You're trying to access a website. Chrome throws up that frustrating gray page with the dinosaur and the message: "This site can't be reached."

Firefox says: "Hmm. We're having trouble finding that site."

Edge gives you: "Can't reach this page."

Different browsers, same problem. And honestly? It's one of the most annoying errors you'll encounter because it doesn't tell you WHAT went wrong or HOW to fix it.

I've been dealing with this error professionally for six years. I run uptime monitoring for thousands of websites, and "This site can't be reached" is the number one support ticket I get. Not because it's complicated—but because the actual cause varies wildly from case to case.

Here's what nobody tells you upfront: this error has nothing to do with the website being "down" in the traditional sense. The website could be perfectly operational. The problem is that YOUR computer can't establish a connection to that server.

Think of it like calling someone's phone. If they don't answer, is their phone broken? Did they block you? Is their number disconnected? Is YOUR phone having network issues? Is the cell tower down?

Same concept here.

This guide will walk you through every possible cause and solution, in order of likelihood. We'll start with the quick fixes that solve 70% of cases, then move into the technical stuff if needed.

Let's fix this.

What Does "This Site Can't Be Reached" Actually Mean?

In technical terms, your browser is saying: "I tried to connect to this server, but the connection failed before we could even start talking."

It's a connection failure, not a server failure.

The error usually includes one of these technical codes:

• ERR_CONNECTION_REFUSED - Server actively rejected the connection
• ERR_CONNECTION_TIMED_OUT - Server didn't respond in time
• ERR_CONNECTION_RESET - Connection was established but then dropped
• ERR_NAME_NOT_RESOLVED - Your computer can't find the website's IP address
• ERR_CONNECTION_CLOSED - Connection ended unexpectedly

Each code points to a slightly different problem, but the fixes are mostly the same. We'll cover all of them.

Quick Diagnosis: Is It You or the Website?

Before we waste time troubleshooting your setup, let's confirm the website itself isn't down.

30-second test:

1. Open your phone (disconnect from WiFi, use mobile data)
2. Try loading the website
3. If it loads on mobile data → Problem is with your home network
4. If it DOESN'T load → Check if site is down globally

Check global status:

• Go to IsYourWebsiteDownRightNow.com
• Enter the website URL
• Get instant results from multiple global servers

If the site is confirmed UP globally but you can't reach it, the problem is definitely on your end. Keep reading.

If the site is DOWN globally, there's nothing you can do except wait. The server is offline.

The 5-Minute Fix Checklist (Solves 70% of Cases)

Try these in order. Don't skip steps.

Step 1: Restart Your Router (Properly)

I know you've probably tried this, but most people do it wrong.

Correct method:

1. Unplug the power cable from your router
2. Count to 30 slowly (seriously, don't plug it back in after 5 seconds)
3. Plug it back in
4. Wait 2 full minutes for it to boot completely
5. Try the website again

Why this works: Your router maintains connection states, DNS cache, and IP assignments. After days of uptime, these can get corrupted. A power cycle clears everything.

Last week, a user insisted their router restart "didn't work." I walked them through it again, made them wait the full 30 seconds, and boom—instant fix. Patience matters here.

Step 2: Flush DNS Cache

Your computer stores IP addresses of websites you visit (DNS cache). If that data becomes outdated or corrupted, you can't reach those sites.

Windows:

1. Press Windows key
2. Type "cmd" and press Enter
3. Type: ipconfig /flushdns
4. Press Enter
5. You should see "Successfully flushed"

Mac:

1. Open Terminal (Applications → Utilities)
2. Type: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
3. Enter your password
4. Done

Linux:

sudo systemd-resolve --flush-caches

What this does: Deletes all stored DNS records, forcing your computer to look them up fresh.

Step 3: Change Your DNS Servers

This is the big one. I'd estimate 40% of "This site can't be reached" errors come from DNS problems with your ISP's servers.

Your ISP's DNS servers can be:

• Slow
• Unreliable
• Blocking certain websites
• Temporarily down

Switch to Cloudflare DNS (fastest and most private):

Windows:

1. Control Panel → Network and Sharing Center
2. Click your connection → Properties
3. Select "Internet Protocol Version 4 (TCP/IPv4)" → Properties
4. Choose "Use the following DNS server addresses"
5. Preferred DNS: 1.1.1.1
6. Alternate DNS: 1.0.0.1
7. Click OK

Mac:

1. System Preferences → Network
2. Select your connection → Advanced
3. DNS tab
4. Click the + button
5. Add 1.1.1.1 and 1.0.0.1
6. Click OK → Apply

Alternative DNS options:

• Google DNS: 8.8.8.8 and 8.8.4.4
• OpenDNS: 208.67.222.222 and 208.67.220.220

I switched to Cloudflare DNS three years ago and never looked back. Faster page loads, fewer connection errors, better privacy.

Step 4: Disable VPN/Proxy

VPNs and proxies add an extra layer between you and websites. Sometimes that layer breaks.

Test:

1. Completely turn off your VPN (don't just pause it)
2. Disable any proxy settings
3. Try loading the site

Where to check proxy settings:

Windows:

• Settings → Network & Internet → Proxy
• Make sure everything is OFF

Mac:

• System Preferences → Network → Advanced → Proxies
• Uncheck all proxy protocols

Common VPN issues:

• VPN server is down
• Website blocks VPN traffic (Netflix, banks, etc.)
• VPN DNS is misconfigured
• Split tunneling conflicts

If the site loads with VPN off, your VPN is the problem. Contact their support or try a different VPN server location.

Step 5: Check Firewall/Antivirus

Security software can block connections they consider "suspicious."

Windows Defender:

1. Settings → Update & Security → Windows Security
2. Firewall & network protection
3. Click "Allow an app through firewall"
4. Make sure your browser is checked

Third-party antivirus (Norton, McAfee, Kaspersky, etc.):

• Temporarily disable it
• Try loading the site
• If it works, add the site to your antivirus whitelist

I once spent 2 hours troubleshooting a client's issue before discovering their corporate antivirus was silently blocking all .io domains. Security software can be overly aggressive.

Intermediate Fixes (When Basic Steps Don't Work)

Fix #6: Reset TCP/IP Stack

Your computer's network configuration can get corrupted. Resetting it often fixes mysterious connection issues.

Windows (requires admin):

1. Open Command Prompt as Administrator
2. Run these commands one by one:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

3. Restart your computer

Mac:

1. Open Terminal
2. Type: sudo ifconfig en0 down
3. Type: sudo ifconfig en0 up
4. Enter password when prompted

What this does: Resets all network adapters and clears corrupted network settings.

Fix #7: Update Network Drivers

Outdated or corrupted network drivers cause connection failures.

Windows:

1. Right-click Start → Device Manager
2. Expand "Network adapters"
3. Right-click your adapter → Update driver
4. Choose "Search automatically for drivers"
5. Restart if updates installed

Mac:

• Network drivers update automatically with macOS updates
• Go to System Preferences → Software Update
• Install any available updates

Fix #8: Disable IPv6

Some websites have IPv6 compatibility issues. Disabling it forces IPv4, which is more universally supported.

Windows:

1. Control Panel → Network and Sharing Center
2. Click your connection → Properties
3. Uncheck "Internet Protocol Version 6 (TCP/IPv6)"
4. Click OK

Mac:

1. System Preferences → Network
2. Advanced → TCP/IP
3. Configure IPv6: Link-local only or Off
4. Apply

Note: You can always re-enable this later. It's just for testing.

Fix #9: Check Hosts File

Your hosts file can override DNS lookups. Malware sometimes modifies it to block websites.

Windows:

1. Open Notepad as Administrator
2. File → Open
3. Navigate to: C:\Windows\System32\drivers\etc
4. Change file type to "All Files"
5. Open "hosts"
6. Look for the website you're trying to reach
7. Delete any lines referencing it
8. Save

Mac:

1. Open Terminal
2. Type: sudo nano /etc/hosts
3. Enter password
4. Look for the website domain
5. Delete any lines with it
6. Press Ctrl+X, then Y to save

Normal hosts file has:

• Lines starting with # (comments)
• "127.0.0.1 localhost"
• That's it

If you see random websites listed, delete those lines.

Fix #10: Try a Different Browser

Browser-specific corruption happens more often than you'd think.

Test with:

• Chrome (if using Firefox)
• Firefox (if using Chrome)
• Edge (built into Windows)
• Safari (Mac default)

If it works in Browser B:

• Your original browser has corrupted settings
• Try resetting it to defaults
• Or create a new user profile

Chrome profile reset:

1. chrome://settings/reset
2. "Restore settings to their original defaults"
3. Reset settings

Advanced Troubleshooting (Technical Users)

Fix #11: Check MTU Settings

MTU (Maximum Transmission Unit) mismatches can cause connection failures.

Windows - Find optimal MTU:

ping google.com -f -l 1472

If this fails, reduce the number:

ping google.com -f -l 1464
ping google.com -f -l 1450

Keep going until it succeeds. That's your optimal MTU.

Set MTU:

netsh interface ipv4 set subinterface "Wi-Fi" mtu=1450 store=persistent

(Replace "Wi-Fi" with your adapter name)

Mac - Set MTU:

1. System Preferences → Network → Advanced
2. Hardware tab
3. Configure: Manually
4. MTU: Custom (try 1450)
5. Apply

Fix #12: Traceroute Diagnosis

See exactly where the connection is failing.

Windows:

tracert example.com

Mac/Linux:

traceroute example.com

What to look for:

• Request timed out at hop 1-3 → Your router/ISP issue
• Request timed out at hop 10+ → Problem between ISP and website
• All hops time out → DNS resolution failed

This tells you WHO'S responsible for the connection failure.

Fix #13: Check Port Availability

Some ISPs or firewalls block specific ports.

Test if port 443 (HTTPS) is open:

Windows:

telnet example.com 443

Mac/Linux:

nc -zv example.com 443

If it says "Connection refused" or times out, that port is blocked.

Common blocked ports:

• Port 80 (HTTP)
• Port 443 (HTTPS)
• Port 21 (FTP)
• Port 25 (Email)

Contact your ISP if standard ports are blocked.

Error Code Specific Solutions

ERR_NAME_NOT_RESOLVED

Means: Your computer can't find the website's IP address.

Fix priority:

1. Flush DNS cache (step 2)
2. Change DNS servers (step 3)
3. Check hosts file (fix #9)
4. Restart router (step 1)

ERR_CONNECTION_REFUSED

Means: The server actively rejected your connection request.

Possible causes:

• Website is blocking your IP
• Firewall blocking the port
• Server is overloaded
• Your IP was flagged (too many requests)

Fixes:

1. Wait 15 minutes and try again
2. Try different network (mobile data)
3. Contact website support
4. Check if you're IP banned

ERR_CONNECTION_TIMED_OUT

Means: Server didn't respond within the timeout period.

Causes:

• Server is overloaded
• Your internet is too slow
• Packet loss in the route
• Server is partially down

Fixes:

1. Wait and retry
2. Check your internet speed
3. Traceroute to see where it's hanging
4. Try during off-peak hours

ERR_CONNECTION_RESET

Means: Connection was established, then suddenly dropped.

Causes:

• Antivirus/firewall interference
• Network adapter glitch
• ISP connection instability
• Server-side rate limiting

Fixes:

1. Disable antivirus temporarily
2. Reset TCP/IP stack (fix #6)
3. Update network drivers (fix #7)
4. Contact ISP about connection drops

Browser-Specific Quirks

Chrome/Edge Issues

Clear SSL State:

1. Settings → Privacy and security
2. Security → Manage certificates
3. Clear SSL state (Windows)

Reset site settings:

1. Visit: chrome://settings/content
2. Reset all permissions

Firefox Issues

Disable DNS over HTTPS:

1. Settings → Privacy & Security
2. Scroll to "DNS over HTTPS"
3. Select "Off"
4. Restart Firefox

This sometimes conflicts with system DNS.

Safari Issues

Clear website data:

1. Safari → Preferences → Privacy
2. Manage Website Data
3. Remove the specific site
4. Try again

When to Suspect Your ISP

Signs your ISP is the problem:

1. Site works on mobile data but not WiFi
2. Multiple devices all have the same issue
3. Some websites load, others don't (selective blocking)
4. Traceroute shows failure at ISP's routers
5. VPN fixes the problem

What ISPs do:

• Block certain websites (legal requirements or their policy)
• Throttle specific traffic (torrents, streaming)
• Have DNS server outages
• Route optimization issues

Action steps:

1. Call ISP support
2. Ask if they're blocking the site
3. Request modem/router restart from their end
4. Ask about known outages in your area
5. Consider switching ISPs if they're blocking legitimate sites

Mobile Network Issues

If you're getting this error on mobile data:

Android:

1. Settings → Network & Internet → Mobile network
2. Toggle "Airplane mode" on for 10 seconds
3. Toggle off
4. Try again

Or:

1. Settings → Apps → Show system apps
2. Find "Chrome" → Storage → Clear cache

iPhone:

1. Settings → General → Reset → Reset Network Settings
2. This will erase saved WiFi passwords (warning!)

Or:

1. Settings → Safari → Clear History and Website Data

Site-Specific Issues

Banking Websites

Banks are paranoid about security (rightfully so).

Common causes:

• VPN blocking
• Outdated SSL certificates on your end
• IP address flagged for suspicious activity
• Browser extensions interfering

Fix:

1. Disable ALL extensions
2. Turn off VPN
3. Clear cookies for that specific site
4. Use Incognito mode
5. Call bank if still failing

Government Websites

Government sites often use outdated technology.

Issues:

• Only work with specific browsers (usually IE or Edge)
• Require outdated TLS versions
• Block modern security features

Fix:

1. Try Internet Explorer or Edge
2. Add site to "compatibility mode"
3. Enable older TLS versions temporarily

Streaming Services (Netflix, Hulu, etc.)

These actively block VPNs and proxies.

Fix:

1. Disable VPN completely
2. Clear cookies
3. Try different browser
4. Restart modem to get new IP

The Nuclear Option: Network Reset

If NOTHING has worked, reset your entire network configuration.

Windows 10/11:

1. Settings → Network & Internet
2. Status → Network reset
3. Reset now
4. Restart computer

This will:

• Remove all network adapters
• Reset to factory defaults
• Delete all WiFi passwords
• Clear all network settings

Mac:

1. Delete: /Library/Preferences/SystemConfiguration/
   • com.apple.airport.preferences.plist
   • com.apple.network.identification.plist
   • NetworkInterfaces.plist
   • preferences.plist
2. Restart Mac

Real User Cases I've Solved

Case 1: Corporate VPN Conflict

User couldn't access any external sites while connected to work VPN. Problem: VPN was routing ALL traffic through corporate servers, and those servers were down.

Fix: Split tunneling in VPN settings - route only work traffic through VPN, everything else direct.

Case 2: Router DNS Cache Poisoning

User's router was caching old DNS records for a website that changed servers. ISP DNS worked fine, but router kept serving old IP.

Fix: Factory reset router (after backing up settings). Problem vanished.

Case 3: ISP Port Blocking

Small ISP was blocking port 443 (HTTPS) to "reduce piracy." User couldn't access ANY secure website.

Fix: Filed FCC complaint. ISP unblocked ports within 48 hours. Sometimes you need the big guns.

Case 4: Antivirus False Positive

Kaspersky was flagging a legitimate e-commerce site as "phishing" and blocking all connections.

Fix: Added site to Kaspersky whitelist. User verified site was legitimate before doing this.

Prevention Tips

To avoid this error in the future:

1. Use reliable DNS servers (Cloudflare 1.1.1.1 or Google 8.8.8.8)
2. Keep your router firmware updated (check manufacturer's site)
3. Restart router weekly (set a phone reminder)
4. Update your OS regularly (network stack improvements)
5. Maintain up-to-date antivirus (but not overly aggressive ones)
6. Monitor your internet speed (use speedtest.net weekly)
7. Keep a backup connection (mobile hotspot as emergency backup)

When to Give Up and Wait

Sometimes the problem is genuinely out of your control.

Give it time if:

• Website is having a major outage (check DownDetector)
• Your ISP confirms infrastructure issues
• You've tried literally everything in this guide
• Multiple people in your area have the same issue

Wait 2-4 hours, then try again.

Most connection issues resolve themselves within this timeframe as servers get rebooted, routes get optimized, or DNS propagates.

FAQ

Q: Why does this error happen more on certain websites?

A: Some websites have stricter security, more complex server setups, or are hosted farther from you geographically. Banks, government sites, and international services are common culprits.

Q: Can malware cause this error?

A: Yes. Malware can modify your hosts file, install proxy settings, or block specific sites. Run a full antivirus scan if you suspect this.

Q: Is there a difference between this error in Chrome vs Firefox?

A: The underlying causes are the same, but browsers display different messages. Chrome says "This site can't be reached," Firefox says "Hmm. We're having trouble finding that site."

Q: Why does the site work on my phone but not my computer?

A: Different network paths. Your phone uses mobile data (different ISP), different DNS servers, and doesn't have the same firewall/antivirus as your computer.

Q: Can I permanently fix this?

A: Yes, if you identify the root cause. Switching to Cloudflare DNS prevents about 40% of these errors long-term. Keeping your system updated prevents another 30%.

Q: Should I contact the website owner?

A: Only if you've confirmed the site IS up for everyone else but still won't load for you after trying everything. They might have accidentally blocked your IP or region.

Q: How long should each fix take?

A: Basic fixes (steps 1-5): 10 minutes total. Intermediate fixes: 20-30 minutes. Advanced troubleshooting: 1-2 hours. If you've spent more than 2 hours, something is seriously wrong—contact professional support.

Q: Will resetting network settings delete my files?

A: No, it only affects network configuration. Your files, programs, and personal data are safe. You'll just need to re-enter WiFi passwords.

Final Checklist

Before you give up, confirm you've tried:

• ✅ Checked if site is down globally
• ✅ Restarted router (with 30-second wait)
• ✅ Flushed DNS cache
• ✅ Changed DNS to 1.1.1.1
• ✅ Disabled VPN/proxy
• ✅ Tried different browser
• ✅ Tried different network (mobile data)
• ✅ Checked firewall/antivirus
• ✅ Reset TCP/IP stack
• ✅ Cleared browser cache completely

If you've done ALL of these and it still doesn't work, the problem is either:

1. The website is blocking you specifically
2. Your ISP is blocking the site
3. There's a deeper system issue requiring professional help

The Most Common Fix (That Everyone Forgets)

Restart your computer.

I know it sounds stupid. I know it's cliché. But your computer's network stack gets cluttered after days of uptime.

A restart clears:

• Memory leaks in network drivers
• Corrupted temporary network settings
• Background processes holding connections
• System cache that needs refreshing

I'd estimate 15% of all "This site can't be reached" errors are fixed by a simple restart that users were too impatient to try.

Takes 2 minutes. Worth it.

Tools That Help Diagnose

Keep these bookmarked:

1. IsYourWebsiteDownRightNow.com - Check if site is globally down
2. Speedtest.net - Test your connection speed
3. DNSChecker.org - Verify DNS propagation
4. Pingdom.com - Test site response from multiple locations
5. DownDetector.com - See if others report outages

Conclusion

"This site can't be reached" is frustrating because it's vague. But now you know it's almost always a DNS issue, firewall block, or network configuration problem.

The three fixes that solve 80% of cases:

1. Change DNS to 1.1.1.1 (most common fix)
2. Restart router properly (30-second unplug)
3. Disable VPN/proxy temporarily (rules out that layer)

Start there. If those don't work, move through the intermediate and advanced fixes methodically.

And remember—if the site works on mobile data but not WiFi, the problem is 100% your home network. Focus on router, firewall, and DNS settings.

Still can't reach a site? Check if it's down globally: Test Website Status Now →

About This Guide

Written by someone who's troubleshot thousands of connection errors professionally. Every solution here has worked in real scenarios, not just theoretical situations. Last updated November 2025 with the latest fixes for Windows 11, macOS Sonoma, and modern browsers.

Was this helpful? Bookmark this page—you'll need it again someday.

Related Guides:

• Website Not Loading? 12 Instant Fixes
• How to Check if a Website is Down: Complete Guide 2025
• ERR_CONNECTION_REFUSED: What It Means and How to Fix It
• DNS Server Not Responding: 10 Proven Solutions

Tested on: Windows 11, macOS Sonoma, Chrome 119, Firefox 120, Edge 119 | November 2025