How to Fix the “Site Can’t Be Reached” Error: Complete Guide

Few things are more frustrating than typing in a web address, hitting enter, and staring at the dreaded message: “This site can’t be reached.” If you’re a regular internet user, it feels like hitting a brick wall. If you’re a WordPress site owner, it’s even worse — potential visitors and customers are locked out, and you might not even know why.

The good news? This error isn’t the end of the world. It’s usually something small — a setting is misconfigured, a network issue or a WordPress problem. In this post we’ll go into what the error means, why it happens and step by step solutions from the simple fixes to advanced troubleshooting. By the end you’ll not only fix the problem but also know how to prevent “site can’t be reached” from happening again.

At its core, the “This site can’t be reached” message is a catch-all error displayed by browsers (Chrome, Edge, Firefox, etc.) when they fail to connect to a website. Instead of giving a detailed explanation, the browser shows this generic message, which can be triggered by several underlying issues.

Common Error Codes You Might See Alongside It

When the browser shows this message, it often comes with specific error codes that provide clues:

• DNS_PROBE_FINISHED_NXDOMAIN – The domain name can’t be resolved because the DNS records aren’t pointing correctly or the domain expired.
• ERR_CONNECTION_REFUSED – The server rejected the connection request, often due to firewall blocks or server configuration issues.
• ERR_CONNECTION_RESET – The connection was established but dropped unexpectedly, commonly linked to unstable networks or server crashes.
• ERR_TIMED_OUT – The server took too long to respond, usually caused by heavy traffic, hosting problems, or misconfigurations.
• ERR_SSL_PROTOCOL_ERROR – A problem with the site’s SSL certificate or HTTPS configuration.

Each of these codes tells a slightly different story, and identifying them is the first step to troubleshooting.

Client-Side vs. Server-Side Issues

To solve this error, it’s important to distinguish whether the issue is on your device/network (client-side) or the website’s hosting/server (server-side).

• Client-side causes: Problems with your internet connection, router, device settings, browser cache, DNS, VPN, or antivirus/firewall.
• Server-side causes: Domain misconfiguration, expired SSL, overloaded servers, database crashes, corrupted files, or issues with WordPress itself.

Once you know which side the issue is on, you can apply the right fix without wasting time.

The “This site can’t be reached” message can feel vague, but the root causes usually fall into a handful of categories. Let’s unpack the most common ones so you can start narrowing down where the problem lies.

1. DNS Resolution Problems

DNS (Domain Name System) is like the internet’s phonebook. When you type in a domain (e.g., example.com), DNS translates it into an IP address that browsers can connect to. If DNS fails, your site won’t load.

• Domain not pointing correctly – If your domain’s DNS records (A record, CNAME, NS, etc.) aren’t set up correctly, browsers can’t find the server.
• Domain expired – If the domain registration lapses, the DNS records vanish.
• Propagation delays – When you recently updated DNS, it can take 24–48 hours for changes to spread worldwide. During this time, some users may see the error while others don’t.

Symptom: Usually paired with DNS_PROBE_FINISHED_NXDOMAIN.

2. Network / ISP Issues

Sometimes the problem isn’t the site or domain at all—it’s your network.

• Router/modem problems – Overloaded or outdated firmware can disrupt connections.
• WiFi instability – Weak signals, interference, or congested networks cause timeouts.
• Mobile data restrictions – ISPs may block certain connections or throttle speeds.
• Firewall or antivirus blocks – Overzealous security software can mistakenly block a site.

Symptom: Site loads fine on another network (e.g., switching from WiFi to mobile data).

3. Browser-Side Problems

Browsers themselves can cause trouble if local data or settings interfere with connections.

• Corrupted cache/cookies – Old cache files can block a new connection.
• Proxy/VPN misconfigurations – If traffic is routed through a proxy/VPN that’s unstable or blocked, you’ll see errors.
• Experimental protocols – Features like QUIC or custom browser flags can sometimes interfere.
• Outdated browser – Older versions may not handle modern security protocols properly.

Symptom: Error disappears when testing in another browser or in incognito mode.

4. Server or Hosting Issues

If the client side looks fine, the culprit may be the server hosting the WordPress site.

• Server downtime – Hosting outages or overloaded servers make the site unreachable.
• PHP or database errors – A crashed MySQL database or a PHP fatal error halts WordPress execution.
• Corrupted configuration files – Broken .htaccess (Apache) or misconfigured nginx.conf can block connections.
• Resource limits exceeded – If CPU, RAM, or disk I/O hit max, the server can’t respond.

Symptom: Error appears for everyone across all devices and networks.

5. WordPress-Specific Causes

Because we’re focusing on WordPress, it’s important to highlight issues unique to WP environments.

• Plugin or theme conflict – A faulty plugin/theme update may break site functionality or block connections.
• Corrupt .htaccess file – Often caused by permalink changes or misconfigured plugins.
• Incorrect WordPress URL settings – If site_url or home_url are set wrong (in WP Admin or database), WordPress may redirect incorrectly.
• SSL certificate misconfiguration – Forcing HTTPS without a valid SSL leads to connection failures.
• wp-config.php issues – Wrong database credentials, bad syntax, or missing table prefix can stop WordPress from loading.

Symptom: The error appears right after a WordPress update, plugin activation, or SSL setup.

6. Local Computer or OS-Specific Issues

Finally, sometimes the issue lives entirely on the user’s device.

• Corrupted hosts file – A bad entry may block domain resolution.
• DNS cache issues – Old cached records prevent reaching the updated IP.
• Outdated network drivers – On Windows especially, faulty drivers can block traffic.
• VPN tunneling errors – If using corporate VPNs, DNS resolution can fail for certain domains.

Symptom: Only one device in your household/workplace can’t access the site.

Troubleshooting a “This site can’t be reached” error becomes much easier if you start by gathering evidence instead of blindly trying fixes. Here are the most effective ways to narrow down the cause:

1. Test Across Multiple Devices & Networks

First, check whether the problem is isolated to one device or network.

• Try a phone vs. a computer – If the site loads on your phone (mobile data) but not your PC (WiFi), the issue is with your local network or device.
• Switch between WiFi and mobile data – If the site loads fine over mobile data but fails on WiFi, it’s likely a router or ISP-level issue.
• Ask others – Sometimes, the site is globally down, which you can confirm by asking someone else or using tools like Down for Everyone or Just Me.

Why this matters: This step instantly tells you whether to focus on client-side fixes or server-side investigation.

2. Identify the Error Code Displayed

The browser error code is your biggest clue.

• DNS_PROBE_FINISHED_NXDOMAIN → DNS issue.
• ERR_CONNECTION_REFUSED → Server firewall or misconfiguration.
• ERR_CONNECTION_RESET → Unstable network or overloaded server.
• ERR_TIMED_OUT → Server too slow to respond.
• ERR_SSL_PROTOCOL_ERROR → SSL/HTTPS misconfiguration.

Take note of the exact code—it saves you from unnecessary troubleshooting.

3. Check DNS Records & Resolution

If the issue points to DNS, verify the domain setup.

• Run nslookup yourdomain.com or dig yourdomain.com in terminal/command prompt.
• Use online tools like WhatsMyDNS or MXToolbox to confirm global DNS propagation.
• Ensure the A record points to your hosting server’s IP and that nameservers are correct.

If DNS looks inconsistent worldwide, it’s either propagation delay or misconfigured DNS records.

4. Inspect Server Status

For site owners, the next step is checking the hosting environment.

• Ping or traceroute the server – This shows if the server responds at all.
• Check hosting dashboard – Many hosts display CPU/RAM usage, uptime, or error notifications.
• Review server logs – Apache/nginx logs, PHP error logs, or WordPress debug logs often reveal if scripts crashed.

Example: If the logs show repeated PHP fatal errors, the issue is WordPress-related rather than DNS.

5. Use Browser Developer Tools

For advanced users, the browser itself provides diagnostic tools.

• Open Developer Tools → Console (in Chrome/Edge: Ctrl+Shift+I).
• Look for blocked scripts, SSL warnings, or redirect loops.
• The Network tab shows whether the request even reaches the server.

Helpful when the site partially loads but fails to fetch certain resources.

6. Enable WordPress Debugging

If you’re the site owner and can still access the backend:

• Turn on WP_DEBUG in wp-config.php to capture PHP errors.
• Review the error_log file in your hosting file manager or via FTP.
• Check the Site Health tool in WordPress (under Tools > Site Health) for misconfigurations.

This often points directly to faulty plugins, themes, or misconfigured WordPress URLs.

If you’re just trying to access a website and keep running into the “This site can’t be reached” error, start with these fixes. They address the most common client-side issues like network, browser, or DNS problems.

1. Restart Your Network Equipment

Sometimes the simplest fix is the most effective.

• Power off your router and modem for 30–60 seconds, then turn them back on.
• Restart your device (computer or phone) after reconnecting.

Why it works: Routers often cache DNS or get stuck in a bad state, and a reset clears it.

2. Try a Different Network

Switch to another network to rule out ISP or local WiFi issues.

• Use mobile data instead of WiFi.
• Connect to a different WiFi (e.g., at a café, office, or friend’s house).

If the site loads elsewhere, the issue is with your local ISP or router.

3. Clear Browser Cache & Cookies

Corrupted cache or cookies can block websites.

• In Chrome: Go to Settings > Privacy > Clear Browsing Data.
• Select Cached images and files + Cookies and site data.

If clearing cache fixes the problem, your browser was holding onto outdated or corrupted files.

4. Disable Firewall & Antivirus Temporarily

Security software sometimes blocks legitimate sites by mistake.

• Turn off your antivirus or firewall for a few minutes.
• Refresh the site to see if it loads.

If disabling works, whitelist the site in your antivirus/firewall settings.

5. Flush Your DNS Cache

DNS cache stores IP addresses of websites, but if outdated, it can block access.

Windows: Open Command Prompt and type:

ipconfig /flushdns

macOS: In Terminal, type:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

This forces your system to fetch fresh DNS records.

6. Change Your DNS Servers

If your ISP’s DNS is unreliable, switch to a public DNS for faster, more stable browsing.

• Google DNS: 8.8.8.8 and 8.8.4.4
• Cloudflare DNS: 1.1.1.1 and 1.0.0.1

This fix alone resolves a large percentage of DNS_PROBE_FINISHED_NXDOMAIN errors.

7. Remove Proxy or VPN

A faulty proxy or unstable VPN tunnel can block connections.

• Disable your proxy in Network Settings.
• Disconnect from your VPN and try accessing the site directly.

If the site works without VPN/proxy, the issue is routing-related.

8. Reset Network Settings

If none of the above work, reset all network configurations to factory defaults.

• Windows:
  • Go to Settings > Network & Internet > Status > Network Reset.
    
• macOS:
  • Delete the WiFi profile and reconnect, or reset network settings manually.

This wipes out problematic configurations and gives you a fresh start.

These fixes cover 90% of cases where a visitor encounters the “This site can’t be reached” error. If the site still won’t load after trying them, chances are the problem lies on the server or WordPress side—something only the site owner can fix.

Now let’s get into territory most generic guides skip: WordPress-related reasons for “site can’t be reached.” Even if your domain and server are fine, certain WordPress settings or files can break the connection. Here are the biggest culprits:

1. Plugin or Theme Conflict

• A poorly coded plugin or a theme update can break network responses.
• Try disabling all plugins via FTP or your hosting panel. If the site loads, reactivate them one by one to identify the culprit.

2. Corrupt .htaccess File

• This small configuration file controls redirects and security rules.
• A corrupted .htaccess can block access entirely.
• Solution: rename .htaccess (to .htaccess_old), then regenerate a new one from WordPress Dashboard > Settings > Permalinks > Save.

3. Incorrect WordPress or Site URL

• If WordPress Address (URL) or Site Address (URL) is set incorrectly (say, http instead of https), the site can fail to load.
• Fix via wp-admin > Settings > General or update the values directly in the database (wp_options table).

4. SSL Certificate Issues

• An expired or misconfigured SSL can trigger ERR_SSL_PROTOCOL_ERROR or This site can’t provide a secure connection.
• Renew the SSL certificate or reconfigure HTTPS settings.

5. WP-Config or Database Errors

• Wrong database credentials in wp-config.php can prevent the site from connecting.
• A corrupted database may also stop the server from responding. Running a repair via phpMyAdmin can help.

If you’ve confirmed that the issue isn’t on the visitor’s end, it’s time to investigate your WordPress hosting environment and site configuration. Here are the most effective steps to bring your site back online.

1. Check Domain Registration & DNS Records

Your site won’t load if the domain itself isn’t pointing correctly.

• Log in to your domain registrar and make sure the domain hasn’t expired.
• Verify that your A record points to your hosting server’s correct IP address.
• Double-check nameservers (NS) if using third-party DNS (Cloudflare, Route53, etc.).
• Reduce TTL values to speed up DNS propagation if you’ve recently changed records.

Pro tip: Use WhatsMyDNS to confirm global DNS resolution.

2. Verify Hosting Server Status

Sometimes the server is simply down or overloaded.

• Log into your hosting dashboard (cPanel, Plesk, or custom panel).
• Check CPU, RAM, and bandwidth usage—if maxed out, upgrade or optimize resources.
• Look for alerts about downtime or outages from your hosting provider.

If you can SSH into the server, run:

uptime

top

to see server load.

If the server itself is unreachable, contact your hosting provider.

3. Check SSL Certificate & HTTPS Configuration

If the issue happens only on HTTPS, your SSL setup may be broken.

• Confirm your SSL certificate is valid and hasn’t expired.
• Run your domain through an SSL checker (e.g., SSL Labs Test).
• If using Cloudflare or a CDN, check whether SSL is set to Full (Strict) instead of Flexible, which often causes redirect loops.
• Reinstall or renew your SSL certificate if necessary.

Expired SSL certificates are one of the most common reasons users see ERR_SSL_PROTOCOL_ERROR.

4. Disable Plugins & Themes

Faulty or incompatible plugins/themes can prevent WordPress from loading.

• Via FTP or File Manager: rename the /plugins/ folder to plugins_old.
• Try accessing your site—if it works, one of the plugins is the culprit.
• Re-enable plugins one by one until you find the problematic one.
• Switch to a default theme (e.g., Twenty Twenty-Four) to rule out theme conflicts.

Always test plugins/themes in a staging environment before updating.

5. Reset the .htaccess File (Apache Users)

A corrupted .htaccess file can block connections.

• Access your WordPress root directory via FTP.
• Rename .htaccess to .htaccess_old.
• Log into WordPress Admin > Settings > Permalinks > Save Changes.
• This generates a fresh .htaccess file with default rules.

Nginx users should check their server block configuration instead.

6. Fix WordPress URL / Site URL Settings

If site_url or home_url values are incorrect, WordPress won’t load properly.

• From WordPress Admin: Settings > General.

If you can’t access Admin, update directly in the database:

UPDATE wp_options SET option_value=’https://yourdomain.com’ WHERE option_name=’siteurl’ OR option_name=’home’;

Or update via wp-config.php by adding:

define(‘WP_HOME’,’https://yourdomain.com’);

define(‘WP_SITEURL’,’https://yourdomain.com’);

Misconfigured URLs often happen after migrations or SSL installations.

7. Check wp-config.php for Database Connectivity

If WordPress can’t connect to its database, it may show as unreachable.

• Open wp-config.php and verify:
  • DB_NAME (database name)
  • DB_USER (username)
  • DB_PASSWORD (password)
  • DB_HOST (usually localhost but can vary with managed hosting)
• Test database access manually via phpMyAdmin or SSH.

If credentials are wrong, WordPress won’t establish a connection, leading to downtime.

8. Increase PHP Memory & Timeout Limits

If your site is under heavy load, scripts may time out before completing.

In wp-config.php, add:

define(‘WP_MEMORY_LIMIT’, ‘256M’);

In php.ini (if accessible), adjust:

memory_limit = 256M

max_execution_time = 300

This helps prevent ERR_TIMED_OUT or ERR_CONNECTION_RESET errors.

9. Review Server Error Logs

Logs are the ultimate truth tellers.

• Check Apache/nginx error logs.
• Review error_log in your WordPress root.
• Enable WP_DEBUG in wp-config.php for real-time debugging.

Example: A recurring “Allowed memory size exhausted” error means you need to raise PHP limits.

10. Consider CDN or DNS Provider Issues

If you use Cloudflare or another CDN, issues at their end can cause outages.

• Temporarily pause CDN or bypass it.
• Switch DNS back to your origin server to test.
• Check Cloudflare status pages for outages.

If disabling the CDN fixes the issue, the problem is external, not with your WordPress server.

By following these steps, WordPress site owners can systematically eliminate common causes of the “This site can’t be reached” error on the server side.

For those comfortable with a bit of technical digging, these tools can reveal exactly where the connection is breaking:

1. Command-Line Tools

Ping: Tests whether the server is reachable.

ping yourdomain.com

Traceroute: Shows the path between your device and the server. Useful for spotting ISP or routing issues.

tracert yourdomain.com   (Windows)

traceroute yourdomain.com (Mac/Linux)

Nslookup / Dig: Check DNS records directly.

nslookup yourdomain.com

dig yourdomain.com

2. Curl

Run:

curl -I https://yourdomain.com

This shows the HTTP response headers. A 200 response = good; 500/502/504 = server issue.

3. Online Tools

• SSL Labs → tests SSL configuration.
• GTMetrix or Pingdom → test if the server responds globally.
• Down For Everyone Or Just Me → checks if the outage is widespread.

4. Browser DevTools

• Press F12 → Network tab.
• Reload the page to see what requests fail, and note error codes.

These tools go beyond “try restarting your router.” They help you pinpoint whether the issue is local, network-related, or server-side.

Sometimes, “site can’t be reached” appears under very specific conditions. Let’s cover those competitors often miss:

1. Error Only on HTTPS

• • Usually caused by SSL misconfiguration or mixed content errors.
  • Fix: Ensure the SSL certificate is valid and redirect HTTP → HTTPS correctly.

2. Error Only in One Browser

• • Chrome may show it, but Firefox doesn’t. This often means corrupted cache, extensions, or experimental features in that browser.
  • Fix: Reset or reinstall the problematic browser.

3. Error Only on Mobile Network

• • Your ISP might block certain domains or have routing issues.
  • Fix: Switch DNS servers on your mobile device or use a VPN to bypass restrictions.

4. Error After Plugin or Theme Update

• • A new update may break connectivity (e.g., security plugins blocking access).
  • Fix: Roll back the update or disable the plugin via FTP.

5. Error Only From Certain Countries

• • Geo-blocking or CDN rules might restrict access.
  • Fix: Adjust firewall/CDN settings to allow global access.

Fixing the error is one thing — preventing it is where true peace of mind lies. Here’s how to reduce the chances of “site can’t be reached” happening again:

1. Use Reliable DNS Providers

• • Google DNS or Cloudflare DNS ensure fast, stable lookups.

2. Enable SSL Auto-Renewal

• • If your host supports Let’s Encrypt, turn on automatic renewal.

3. Set Up Uptime Monitoring

• • Tools like UptimeRobot or Pingdom alert you when your site goes down.

4. Regular Site Backups

• • A corrupted file can take your site down. Backups let you restore quickly.

5. Test Updates on Staging Sites

• • Never update plugins or themes directly on your live site. Use a staging environment to test first.

6. Choose Managed WordPress Hosting

• • A reliable host handles server optimization, security patches, and monitoring — drastically reducing errors.

The “site can’t be reached” error is scary, especially when it’s your WordPress site on the line. But it’s a fixable problem once you know where to look. From quick user fixes like clearing cache and flushing DNS to deeper WordPress fixes like SSL or .htaccess the solutions are in your hands.

And by putting preventive measures in place — reliable DNS, SSL auto-renewal, uptime monitoring, and managed hosting — you’ll drastically reduce the chance of seeing this error again. Next time your site refuses to load, you’ll know exactly how to turn frustration into a fix.