ERR_CONNECTION_CLOSED: Troubleshooting Guide for Visitors and Site Owners

Key Takeaways

• The ERR_CONNECTION_CLOSED error means the connection between your browser and the website’s server was started but then abruptly ended before the page could load.
• Fixes can be divided into two main areas: client-side issues (like a weak internet connection, bad browser data, or a strict firewall) and server-side issues (such as a server-side firewall, SSL misconfiguration, or limited server resources).
• Troubleshooting this error requires a process of elimination, starting with simple fixes on your end before moving to more advanced solutions or contacting your hosting provider.

Ever been in the position where you try to open a site in Chrome only to see the message “This Site Can’t be Reached”, along with ERR_CONNECTION_CLOSED? It’s one of those errors that make you ask yourself whether the issue lies with your computer, your internet connection, or the website itself.

The reality is that it can be multiple issues at once. Sometimes it’s just a quick network hiccup that disappears if you reload the page. Other times, it needs a bit of troubleshooting to get things back on track.

In this article, we will explain exactly what the ERR_CONNECTION_CLOSED error means, and explore plausible fixes. We will look at options for general users who are simply looking to access a specific site again, and for website owners who need to make sure their site is accessible to everyone.

What Is the ERR_CONNECTION_CLOSED Error

You type a web address. Chrome reaches out to the site’s server. If all goes well, it pulls down the page bits—HTML, images, scripts—and shows the site.

With ERR_CONNECTION_CLOSED, that handshake starts and then drops. Chrome did try to connect; the line just didn’t stay open long enough to load the page. That can be on your side (network, browser settings, a noisy extension) or on the site’s side (serv

Here’s how the error looks on Google Chrome:

This isn’t the same as ERR_CONNECTION_REFUSED. “Refused” is the door shut right away. “Closed” is the door opened, then shut mid-conversation.

One more note: the code is Chrome’s label, but other browsers show the same kind of failure with different wording (Firefox often says the connection was reset; Safari says the server dropped the connection). The problem is the same—you just get a different message.

How To Fix the “ERR_CONNECTION_CLOSED” Error

Like I said earlier, this error doesn’t always have a single cause, which means the fix can vary depending on whether you’re just browsing or if you actually manage the site that’s throwing the error.

Below, we’ll go through the most common solutions for both groups.

For Regular Visitors / Users

If you’re just trying to open a site and run into this message, start here. Most of the time, the problem is something on your own device or network, and you can usually clear it up with one of the following quick fixes.

1. Check Your Internet Connection

A shaky internet line is one of the most common reasons for the ERR_CONNECTION_CLOSED error. If your connection drops, even for a second, the browser loses its link to the site and can’t finish loading the page.

To rule this out, switch to another network if you can — try mobile data instead of Wi-Fi, or plug your device straight into the router. If the site opens on the other connection, the problem is with your internet, not the site.

2. Reset Your Router or Network Settings

Sometimes the problem isn’t the internet itself but the way your device is connecting to it. Routers can hang onto bad settings or simply get stuck, which ends up cutting connections short. Restarting the router is the easiest fix—turn it off, wait a few seconds, then power it back on.

If that doesn’t help, a full network reset on your computer can clear out old or corrupted settings. The steps vary between Windows and macOS, but both give you an option to reset your network back to its defaults.

• On Windows: Go to Settings > Network & internet > Advanced network settings > Network rest. Then hit the Reset now button.

• On macOS: Open System Preferences > Network, select your active network, and hit the minus (-) button to remove it. Then add it back using the plus (+) button.

This puts your network back to its default state, which often clears the error.

3. Clear Browser Cache and Data

Every browser stores bits of websites—like images, scripts, and style files—in a local cache so pages load faster the next time you visit. But if that stored data gets corrupted or out of sync, it can cause connection errors, including ERR_CONNECTION_CLOSED.

Clearing your browser’s cache gives it a clean slate. On Chrome, go to Settings > then Privacy and security, then Delete browsing data.

Select “All time” just to be thorough. Make sure to select the “Cached images and files” option, then hit the Delete data button.

• On Firefox:
  • Open the menu, go to Settings > Privacy & Security, scroll to Cookies and Site Data, and hit Clear Data.

• For Safari (macOS):
• • Open Safari and click Safari > Preferences from the menu bar.
  • Go to the Privacy tab.
  • Click Manage Website Data.
  • From there, you can either remove data for specific sites or hit Remove All to clear everything.

Once cleared, reload the site to see if the error disappears.

4. Flush Your DNS cache

Your computer keeps a temporary record of websites you visit, called the DNS cache. This helps speed up repeat visits by storing the IP addresses of sites locally. However, if those records become outdated or corrupted, your browser may fail to connect properly and show errors such as ERR_CONNECTION_CLOSED.

Flushing the DNS cache forces your system to clear those stored entries and retrieve fresh records from the DNS server. The process is quick and can often resolve connection errors.

• On Windows, open up Command Prompt, and pick Run as administrator.

• Type this command: ipconfig /flushdns.
• Hit enter and you’ll see this message: Successfully flushed the DNS Resolver Cache.

• On macOS, open up Terminal and paste this command: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
• Hit enter. You may be required to enter your password.

After you clear the cache, try reloading the site to confirm whether the issue has been resolved.

5. Update or Reinstall Your Browser

Running an outdated browser can sometimes be the reason you see errors like ERR_CONNECTION_CLOSED. Older versions may have bugs, compatibility gaps, or broken settings that interfere with the connection.

The simplest first step is to check for updates. If you’re on Chrome:

• Open the menu (three dots).
• Go to Help → About Google Chrome.

• This page will show you your browser’s version and will automatically start updating if needed.

If the error still shows up after updating, consider reinstalling Chrome (or whichever browser you’re using). A fresh install clears out corrupted files or misconfigurations that might be lingering in the background.

6. Reset Browser Settings

Another issue that might be causing the problem is misconfigured browser settings. Over time, extensions, flags, or changes you don’t even remember making can interfere with connections and trigger the ERR_CONNECTION_CLOSED error. Resetting the browser to its default state is a simple way to rule this out.

If you’re on Chrome, here’s how:

• Click the three-dot menu in the top right and choose Settings.
• In the left sidebar, go to Reset settings.

• Select Restore settings to their original defaults, then confirm with Reset settings.

This step disables extensions and clears temporary data. Don’t worry, this won’t affect your bookmarks and saved passwords.

7. Disable Browser Extensions

Another thing that can get in the way is your browser extensions. These small add-ons run in the background and sometimes interfere with how sites connect. If one of them is causing the ERR_CONNECTION_CLOSED error, the easiest way to find out is by turning them off.

Disable your extensions one at a time, then reload the page after each. If the site starts working, you’ll know which extension was the problem.

In Chrome:

• Click the three-dot menu in the top right.
• Choose Extensions > Manage extensions.

• Then disable all extensions one by one.

8. Disable Antivirus or Firewall Temporarily

Your firewall or antivirus might interrupt the connection and cause the ERR_CONNECTION_CLOSED error.

A fix can be to turn them off briefly and reload the page.

Every antivirus program is different, so, look in settings for options like “pause” or “temporarily disable” protection.

If you’re on Windows:

• Go to Control Panel > System and Security > Windows Defender Firewall.

• Select Turn Windows Defender Firewall on or off in the left menu.
• Now, choose Turn off for both private and public networks.

Finally, reload the site. If the error is gone, good for you. If not, it’s okay to cry a bit. Re-enable protection and move on to other fixes.

9. Turn Off VPN or Proxy Connections

Sometimes a VPN or proxy can interfere with the connection and cause the ERR_CONNECTION_CLOSED error. The quickest way to check is to turn off your VPN and reload the page.

Go ahead and disable your VPN first.

If you’re on Windows and using a proxy:

• Press Windows Key + I to open Settings.
• Go to Network & Internet > Proxy.

• Make sure Use a proxy server is set to Off.

After making the change, try opening the website again to see if the error is resolved.

10. Change DNS Servers (e.g., use Cloudflare 1.1.1.1)

If the DNS servers assigned by your ISP are unstable or slow, this may contribute to the ERR_CONNECTION_CLOSED error. Switching to a reliable public DNS service, like Google DNS or Cloudflare, can help restore access and even speed up browsing.

On Windows:

• Press Win + R, type ncpa.cpl, and hit Enter.

• In Network Connections, right-click your active adapter (Wi-Fi or Ethernet) and select Properties.
• Highlight Internet Protocol Version 4 (TCP/IPv4) and click Properties.

• Select Use the following DNS server addresses.
  • Google DNS → 8.8.8.8 (Preferred) and 8.8.4.4 (Alternate).
  • Cloudflare DNS → 1.1.1.1 (Preferred) and 1.0.0.1 (Alternate).
• Click OK to save, then flush your DNS cache for the changes to apply right away.

Once that’s done, reload the website to see if the error clears.

Keep Your Website Running Without Errors

With reliable WordPress hosting, you don’t have to worry about sudden errors cutting off your visitors. Enjoy smooth performance and peace of mind, every time.

TRY NOW

For Website Owners / Site Administrators

If it’s your website showing this error to visitors, the issue may lie on the server side. In that case, you’ll want to check a few key settings and configurations to make sure your site stays accessible.

1. Check If Your Hosting Provider Is Having Issues

To start off, check if your hosting provider is experiencing an outage. Hosting-related downtime can sometimes trigger the ERR_CONNECTION_CLOSED error, even if everything is fine on your local device.

For example, Cloudways has a dedicated status page where you can quickly see if there are any ongoing incidents or scheduled maintenance.

If nothing is reported but you still suspect downtime, try testing your server directly:

• Windows: Press Win + R, type cmd, and hit Enter. In the Command Prompt, type ping yourserverip and press Enter.

• macOS: Open Terminal, type ping yourserverip, and press Enter.

If the server doesn’t respond, try a server reboot. With a managed hosting provider like Cloudways, this process is super simple. Just select your server from the Cloudways dashboard and hit Restart.

Finally check if the issue is resolved. If not, then it’s likely an issue on your hosting provider’s side, and you’ll need to contact their support team.

2. Review Server Firewall and Security Plugins

Another possible cause of the ERR_CONNECTION_CLOSED error is your server firewall or a security plugin being too aggressive. Even a small configuration change or update can result in legitimate traffic getting blocked.

• Check your firewall: Make sure that HTTP (port 80) and HTTPS (port 443) are open. If these ports are blocked, your site won’t load.
• Check WordPress security plugins: Tools like Wordfence or Sucuri may sometimes flag safe IPs or requests by mistake. Review recent logs or blocked requests.
• Whitelist your IP: If you suspect your own IP is being blocked, whitelist it to confirm. For example, on Cloudways you can manage IP whitelisting directly from the platform dashboard.

If the site loads after adjusting these settings, you’ve found the culprit.

3. Review Server SSL/TLS Configuration

If your SSL certificate is invalid or misconfigured, browsers may refuse to establish a secure connection and instead return the ERR_CONNECTION_CLOSED error. To rule this out, start by verifying your SSL setup.

Check if your SSL certificate is valid:

• Run a scan with a tool like SSL Labs’ SSL Test. This will show whether your certificate is expired, if the chain of trust is broken, or if all your domains and subdomains are properly covered.

Install a trusted SSL certificate:

• If you’re using a self-signed certificate, or if your site doesn’t have one at all, replace it with a valid SSL certificate from a trusted provider like Let’s Encrypt (free), DigiCert, or Sectigo.

If you’re hosting on Cloudways, we make this process super easy:

• Log in to your Cloudways dashboard.

• Go to Applications → Your App → SSL Certificate.

• Select Let’s Encrypt, enter your domain, and click Install.

Once your SSL certificate is valid and properly installed, reload the site to confirm the error is resolved.

4. Use a VPN to Test Site Accessibility From Different Regions

The ERR_CONNECTION_CLOSED error can also occur because of regional or network-level restrictions.

For example, your ISP might be having routing issues, or access to your server may be blocked in certain locations.

One quick way to confirm this is by using a VPN. A VPN lets you connect through servers in different regions, so you can see whether the site loads outside your current network.

• If the site works with the VPN, the issue may lie with your ISP or regional routing.
• If it doesn’t load anywhere, it’s more likely a server- or configuration-level problem.

This step won’t fix the issue directly, but it helps narrow down whether the problem is local to your network or global to your site.

5. Check Server Resource Limits

If your server is running out of resources—such as RAM, CPU, or disk space—it can disrupt active connections. This often happens when traffic spikes beyond what your hosting plan can handle, or when background processes consume more resources than expected.

To rule this out, log into your hosting account and check the usage metrics for your server. Pay attention to CPU and memory usage in particular. If either is consistently maxed out, you’ll need to optimize your application, reduce unnecessary processes, or consider upgrading your hosting resources.

On Cloudways, server resources can be monitored in real time and scaled up directly from the dashboard, making it easier to prevent these issues before they affect your website’s availability.

6. Inspect .htaccess or Server Rules

A corrupted or misconfigured .htaccess file can also cause connection issues, including the ERR_CONNECTION_CLOSED error. This file controls important server rules such as redirects, URL rewriting, and access permissions. Even a small error in its syntax can prevent your site from loading correctly.

If you suspect this might be the issue, check the file directly:

Using an FTP client (e.g., FileZilla):

• Connect to your server with your FTP login details.
• Navigate to the root directory of your WordPress site (public_html).
• Look for the .htaccess file and open it in a text editor.

For Cloudways users:

• Log in to the Cloudways platform and go to Servers.
• Select your server and copy the Master Credentials from Server Management.

• Paste these into your FTP client like FileZilla and click Quickconnect.
• Open applications → public_html, where you’ll find the .htaccess file.

If the file looks corrupted or overly complex, you can temporarily disable it by renaming it (for example, to .htaccess_old). Then reload your site. WordPress will often generate a fresh .htaccess automatically when you reset permalinks from the dashboard.

Wrapping Up

The ERR_CONNECTION_CLOSED error can be confusing to fix, but as you’ve seen, it’s not a complete dead end. By working through the fixes we covered in this guide—from a simple router restart on your end to checking your SSL certificate on the server—you can almost always find the root cause and get things working again.

For site owners, this is where having the right hosting partner makes a big difference. With Cloudways, a lot of the more technical fixes are just a few clicks away. You can reboot your server, manage your SSL, and scale resources right from the dashboard, which takes a lot of the stress out of it.

And for anything else, our 24/7 support is always here to lend a hand.