How to Fix “This Site Can’t Be Reached” Error (2026 Guide)

Key Takeaways

• The error is a generic browser message with specific error codes underneath that identify the real cause.
• DNS_PROBE_FINISHED_NXDOMAIN means the domain could not be resolved to an IP address.
• ERR_CONNECTION_RESET and ERR_CONNECTION_REFUSED mean DNS resolved correctly but the server rejected the connection.
• Most visitor-side errors resolve with a router restart, DNS flush, or browser cache clear.

You’re trying to visit a website, but instead of the page loading, you see the message, “This site can’t be reached.” It’s frustrating and leaves you wondering what went wrong.

The issue could be with your network, DNS settings, or the website itself. In this guide, we’ll explain what’s causing the error and how to fix it.

We’ll walk you through solutions to fix this common WordPress error for both visitors and website owners. Additionally, we’ll show how Cloudways can help prevent these problems before they even occur.

What Does “This Site Can’t Be Reached” Mean in Chrome and Other Browsers?

When Chrome displays this message, it means: “I tried to connect, but I couldn’t.” That could be due to DNS lookup failure, connection reset, or server refusal. The browser doesn’t go into detail, that part is left to the underlying error code.

The Universal Browser Error Explained

This error is a generic fallback across browsers, a user-friendly notice signal rather than a technical explanation. It avoids overwhelming non-technical users with jargon, but the accompanying error codes give tech people clues.

Underneath, Chrome reports status like “Server IP address could not be found” meaning DNS lookup failed. Safari may report “Safari can’t find the server.”

Those are the real diagnostics behind the simple error message. The codes let us dig deeper whether DNS, firewall, or server-level configuration is at fault.

Common Error Codes Behind This Message

• DNS_PROBE_FINISHED_NXDOMAIN, here DNS failed to resolve the domain name into an IP. NXDOMAIN literally means “non‑existent domain.” It signals DNS configuration issues or propagation delays.
• ERR_CONNECTION_RESET, ERR_CONNECTION_REFUSED, or timeouts, these occur when your browser reaches an IP but connection fails, often due to firewalls or server software refusing traffic. Knowing which error you see helps you choose the right fix.

Another similar error you might encounter is ERR_ADDRESS_UNREACHABLE, which indicates your browser cannot reach the server at the specified IP or address. This often happens due to network misconfigurations, VPN interference, or incorrect URL entrie

These errors can also occur due to poor internet connectivity, firewall or antivirus interference, or VPN issues. Visitors can often fix them by restarting their router, clearing browser cache and cookies, temporarily disabling VPN/antivirus, or flushing the DNS cache on their device.

Why You’re Seeing “This Site Can’t Be Reached” – Common Root Causes

Wondering why this happens? Mostly because the link from domain name to server fails somewhere along the path. Common root causes fall into categories:

• DNS resolution issues: outdated DNS cache or faulty records. Or your DNS provider isn’t responding.
• Network or ISP issues: router glitches or even ISP outages. A simple reboot often resolves these.

DNS Resolution Issues

DNS acts as the internet’s directory. If your device or network fails to resolve the domain’s A or CNAME record, browsers throw NXDOMAIN.

That often means stale cache entries, misconfigured records, or TTL delays. Flushing your DNS cache can help (like using ipconfig /flushdns).

You can check the DNS records propagation via online tools as well such as DNS Checker or whatsmydns.

Network or ISP Connectivity Problems

Even if DNS is working fine, your network could still drop. ISP outages, router issues, or DHCP glitches can block access. A simple router restart often solves the problem.

Firewall, Antivirus, or VPN Interference

Sometimes your security tools block legitimate traffic. VPN software or antivirus can misidentify domains and refuse access.

Temporarily disabling these can immediately restore access, like we’ve done successfully during internal troubleshooting sessions.

Browser or Cache Corruption

A corrupted browser or DNS cache can misdirect your traffic. Chrome stores both DNS and HTTP cache locally.

Clearing them through Chrome settings or using chrome://net-internals/#dns often resolves the issue. After clearing the host cache, the site should load without any problems.

SSL/TLS or HTTPS Conflicts

While most SSL issues yield certificate warnings rather than this generic error, misconfigured HTTPS redirects or expired certificates sometimes cause connection resets.

It’s rare but worth checking if none of the usual fixes work.

Server Misconfiguration or Downtime

If the server is offline or overloaded, the browser simply can’t reach it. This usually leads to timeouts or connection errors.

Cloudways helps by monitoring server health and automatically fixing issues before downtime affects your site.

How to Fix “This Site Can’t Be Reached” – Step‑by‑Step (For Visitors)

If you’re a visitor encountering this error, following the steps below can be helpful.

1. Restart Your Router and Device

You can try unplugging your router for 30 seconds and restart your device. This resets DHCP leases and clears cached DNS at the network level. If that resolves the issue, great. If not, move on to deeper troubleshooting.

2. Clear Browser Cache and Cookies

Next we can try clearing browser cache to help us in this regard.

For example in Chrome browser, you can go to Settings → Privacy → Clear Browsing Data. Check “Cached images and files” and “Cookies.” Click Clear data.

Following this step will remove all stale information and this may fix your issue.

3. Flush DNS and Renew IP

You can flush the DNS cache to fix this error with the following Windows commands:

ipconfig /release  
ipconfig /flushdns  
ipconfig /renew

For macOS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Then renew the DHCP lease. This clears stale DNS and reassigns IP—a fix users personally tested several times.

4. Change to Public DNS (Google or Cloudflare)

Switch to 8.8.8.8/8.8.4.4 (Google) or 1.1.1.1/1.0.0.1 (Cloudflare) in your network adapter settings.

• Windows: Control Panel → Network → Adapter → IPv4 Properties.

• macOS: System Preferences → Network → Advanced → DNS tab.

This step often solves misrouting and stale DNS issues.

5. Disable Antivirus, VPN, or Proxy Temporarily

You can try turning off your antivirus or VPN, then try reloading the site. If it loads, you’ve found the culprit, you can adjust settings or whitelist the site accordingly.

6. Reset Chrome Settings and Flags

You can reset Chrome settings and Flags, you need to visit chrome://flags → click Reset all.

Then open chrome://net-internals/#dns and click Clear host cache. Restart Chrome and test again.

This often resolves conflicts caused by experimental features; a step many users personally found useful.

7. Try a Different Browser or Incognito Mode

Switch to Incognito or move to Firefox, Edge, or Safari. If that works, the issue is isolated to your Chrome profile or extensions.

Disabling extensions or resetting profile settings often fixes the glitch.

How to Fix “This Site Can’t Be Reached” – Website Owner’s Checklist

As a website owner, your troubleshooting requires backend checks. Cloudways offers tools that simplify many of these processes.

1. Verify Domain Registration and DNS Propagation

Confirm your domain is active, not expired and that recent DNS changes have propagated (typically within 48 hours but may take longer). Use WHOIS tools or dig to check DNS record status.

2. Check and Fix DNS Records

Ensure your domain’s A-record and CNAMEs are pointing correctly. Mistakes here trigger NXDOMAIN.

If you use Cloudways’ DNS Made Easy addon, you can manage this centrally, no juggling multiple dashboards.

3. Ensure the Server Is Running and Not Overloaded

You need to make sure your server is not overloaded. If you are a Cloudways user then you can go to the monitoring dashboard to observe CPU, RAM, and disk usage.

With auto-healing servers, Cloudways restarts services automatically when crashing, minimizing downtime and connection failures.

4. Review SSL/HTTPS Configuration

You may also need to review your SSL/HTTPS configuration by reaching out to your hosting provider.

As for Cloudway’s users, you don’t need to worry about this as Cloudways’ SSL Manager installs and renews Let’s Encrypt certificates automatically. Confirm redirection settings to avoid redirect loops. Misconfigured SSL can silently block users even before page loads.

5. Disable Conflicting Plugins (WordPress-Specific)

Deactivate problematic plugins, especially redirect or security plugins, one at a time while testing. Choose vetted tools like Cloudways’ built-in Breeze cache plugin, which is optimized for their stack and less likely to cause DNS or redirect conflicts.

6. Check Firewall and IP Blocking Rules

If you’re using a WAF, ensure legitimate traffic isn’t blocked. Cloudways integrates with Cloudflare WAF, which manages filtering intelligently. Review access logs and whitelist appropriate IP ranges as needed.

Get Your Website Live Faster with Cloudways DNS Made Easy.

Manage domains for just $0.50/month and gain complete control over your website’s online presence.

TRY NOW

How Cloudways Platform Minimizes “Site Can’t Be Reached” Errors

We have listed down the pointers to help you understand how Cloudways Platform minimizes this error with all its advanced features.

Auto‑Healing Servers & Proactive Monitoring

Cloudways constantly monitors server health by tracking CPU, RAM, and process status. If something crashes, the server automatically reboots.

As per the experience, this resolves connection issues faster than a manual restart, often before visitors even notice.

Cloudways combines DNS Made Easy with Cloudflare Enterprise DNS/CDN—providing low-latency, reliable DNS globally. That means fewer DNS lookup failures and faster resolve speeds overall.

Each website runs in its own isolated container. One app misbehaving doesn’t bring others down. That stack-level separation reduces outage risk for multi-site servers.

24/7 Expert Support

Whether it’s DNS misconfiguration, SSL issues, or server logs, Cloudways support is available anytime to help troubleshoot—even outside business hours with live chat.

How to Prevent This Error from Happening Again

Keep your site reliable with these best practices:

• Clear DNS and browser cache regularly, especially after updates or migrations.
• Keep DNS records in sync and update them promptly if server IPs change.
• Monitor server resource usage with alerts, using Cloudways or tools like Pingdom.
• Enable Cloudflare CDN via Cloudways to offload traffic and reduce server stress.
• Review security extensions on user devices, as VPNs or firewalls can occasionally block access.

Final Thoughts: Don’t Let Browser Errors Disrupt Your Website Experience

Although “This site can’t be reached” may seem vague, it actually flags specific problems in DNS, network, or server configuration. Users can often fix it on their end with simple steps.

For visitors, the fastest path to a fix is: restart your router, flush DNS, clear browser cache, and disable VPN. These four steps resolve the vast majority of visitor-side cases.

For site owners, the critical checks are: verify DNS A records point to the correct IP, confirm the server is running and not overloaded, validate SSL certificate status, and identify any plugin or firewall conflicts blocking incoming traffic.