Well, this is weird.
You tried to load your website, but Chrome is throwing an error.
What in the world is ERR_CONNECTION_CLOSED supposed to mean?
The short answer: ERR_CONNECTION_CLOSED means your browser’s connection to the host server was closed unexpectedly before the page could load.
There are several reasons why this could be happening — from a misbehaving VPN to host downtime. Most often, the cause can be found on your device or network.
Before you throw your laptop in the trash and curse the invention of the Internet, we have some words of reassurance: this error is usually pretty easy to fix.
Work through these steps in order, and you’ll usually find the cause quickly.
What does ERR_CONNECTION_CLOSED actually mean?
ERR_CONNECTION_CLOSED is a Chrome error that means the connection to a website’s server was closed unexpectedly before the page could load. The browser reached out (or was mid-conversation), but the connection was terminated before the transfer finished. The cause is usually a network, browser, or hosting issue, and most fixes take only a few minutes.
When you tried to open that web page, Chrome (or your chosen browser) attempted to set up a connection with the hosting server.
That connection allows the server to send over the content you requested.
Except, this time, the connection was cut off before the job was done. That’s why you’re staring blankly at an ERR_CONNECTION_CLOSED error screen.
It also helps to know this error’s siblings, because the fixes differ. Chromium’s network error list defines ERR_CONNECTION_CLOSED (error -100) as a connection that was closed, corresponding to a TCP FIN. ERR_CONNECTION_RESET (-101) means the connection was forcibly reset mid-transfer, and ERR_CONNECTION_REFUSED (-102) means the server actively turned the connection away, which usually signals a server-side problem. Different codes, different culprits — the fixes below target the CLOSED case.
The possible causes for this problem can largely be grouped into three categories:
- Network issues: Your device simply can’t make contact with the host server.
- Browser gremlins: Either Chrome itself or a browser extension is messing with your connectivity.
- Hosting problems: You could see an error if your site isn’t configured properly or you’ve run out of resources.
There’s a strong chance that your network or browser is to blame.
But if other people struggle to access your website, you might need to visit your hosting panel.
Diagnosing ERR_CONNECTION_CLOSED problems
At this point, you could just scroll down to the possible fixes and start working through the list.
If you have 30 seconds to spare though, it’s worth running a quick test first.
Are you seeing the error on just one website?
If yes, the host server could be to blame.
But if every website you visit is showing the ERR_CONNECTION_CLOSED error, you almost certainly have a misbehaving network or browser on your hands.
One more test: Open the same site in a second browser, like Firefox, Edge, or Safari. If the error only appears in Chrome, jump straight to the browser fixes (6–10). If every browser fails, focus on the network and device fixes first.
Top sleuthing, Sherlock.
12 quick ways to fix the ERR_CONNECTION_CLOSED error
That’s enough homework. Time to fix the problem and forget it ever happened.
The short version: most ERR_CONNECTION_CLOSED errors clear after you reload the page, restart your router, flush the DNS cache, or disable a VPN, proxy, or misbehaving browser extension. In fact, before trying anything below, refresh the page and give it a minute. This error is sometimes a temporary glitch that fixes itself.
Here’s your troubleshooting checklist — starting with the most obvious facepalm-worthy solutions, and ending with issues you might not have considered.
1. Check your Internet connection
It feels stupid to even ask but…is your Internet actually working?
You’d be surprised how often this is the root of the problem.
If your connection has dropped, Chrome won’t be able to reach any site — which is exactly what leads to that ERR_CONNECTION_CLOSED message.
Try loading a couple of reliably up sites, like google.com and cloudflare.com. If they load instantly, your connection is fine, and the problem is specific to one site or your browser. If they crawl or fail too, the trouble is closer to home.
If these aren’t working, take a look at your Wi-Fi signal or ensure your Ethernet cable is firmly plugged in.
It might only take a small nudge to put things right!
2. Reboot your router
The most successful IT remedy of all time? Turn it off and turn it back on.
You can use this tried-and-tested method to fix the ERR_CONNECTION_CLOSED issue. Simply unplug your modem or router for at least 30 seconds, and then restart the device.
This can clear out temporary glitches and reset the connection to your Internet Service Provider (ISP). Once your Internet is back online, you might just find that the error is gone.
3. Reset your device’s network settings
No luck? Let’s look under the hood.
Network settings can become corrupted faster than milk left out on a summer’s day. What started as a smooth connection can turn into a tangled mess of misconfigured protocols and confused network interfaces.
Resetting your network settings essentially flushes the system, and that can be enough to clear the error.
Resetting network settings on Windows
To complete this task, you’ll need to open Command Prompt. Don’t worry, it’s not as scary as it sounds.
1. Open the Start menu and search for “cmd”.
2. You should see “Command Prompt” as the top result. Right-click on the program and choose Run as administrator.
3. Now, we need to run some commands. To reset your TCP/IP settings, paste this and hit Enter:
netsh int ip reset4. To reset your Windows Sockets interface (Winsock), follow the same drill with this command:
netsh winsock reset5. Finish up by restarting your device.
Resetting network settings on macOS
Mac users have it slightly easier. It just requires a few clicks in your “System Settings” — we even have pictures!
From the sidebar menu, select Network.
Next, choose your active Internet interface (e.g., Wi-Fi, Ethernet, etc.).
Click Details next to your active network.
Choose TCP/IP on the left.
Then hit the Renew DHCP Lease button in the right-hand panel.
Finish by clicking OK and restarting your Mac.
With any luck, that might solve the headache!
4. Check your firewall and antivirus
Using security tools to protect your device is highly recommended.
The only problem is, antivirus software and firewalls can sometimes be a little too protective.
Instead of only blocking unwanted attention, they interfere with genuine website traffic.
To test whether this is your problem, you will need to temporarily disable your security tools.
- On Windows: Windows Security handles both antivirus and firewall duties. To pause Microsoft Defender Antivirus, search for “Windows Security” via the Start menu, open the app, and go to Virus & threat protection > Manage settings, then toggle real-time protection off. To test the firewall, head to Firewall & network protection, select your active network, and switch Microsoft Defender Firewall off.
- On macOS: You can control the built-in macOS firewall via System Settings > Network > Firewall.
If you have third-party antivirus software (like Norton, McAfee, Avast, etc.), you’ll need to open that specific application and turn off real-time protection.
Once you’ve lowered your guard, check Chrome to see if the error has cleared. Make sure to re-enable the protections ASAP!
5. Play around with your VPN
In some cases, the ERR_CONNECTION_CLOSED error can be tied to how your Internet traffic is being routed.
Depending on your situation, either using a Virtual Private Network (VPN) or disabling VPN and proxy settings could resolve the issue.
Sounds like a contradiction, we know. Allow us to explain.
When to use a VPN
If you’re struggling to access specific sites, it could be because your ISP is blocking access. Using a VPN should allow you to bypass these restrictions.
If you don’t currently use a VPN, Proton VPN’s free plan (one device, no data cap, no ads) is enough to run the test.
When to disable your VPN
Ironically, the very same app that helps you to bypass restrictions can also interfere with your connection, triggering errors like ERR_CONNECTION_CLOSED.
If you’re having issues with most websites, try temporarily disabling your VPN or proxy settings. It might just clear the error.
6. Clear your browser cache
Your browser’s cache is essentially a short-term memory for websites. It saves bits and pieces of sites you visit (like images and files), so they load faster the next time you go there.
Just occasionally, that saved data becomes outdated or corrupted. This can interfere with loading the current version of a site — potentially causing errors like ERR_CONNECTION_CLOSED.
The fix is to clear the cache.
Here’s how to do it with Chrome: Click the three-dot menu in the top-right corner of any window, and select Delete browsing data….
In the pop-up panel, set the “Time range” to All time.
Then, check the box labeled Cached images and files.
Finish by hitting Delete data.
7. Flush your DNS cache
Just as your browser cache stores website files for quick access, your DNS cache remembers the locations of websites you have visited.
If those records ever become corrupted, the DNS cache could send your browser to completely the wrong part of Internet town.
Here’s how to start again with a clean slate.
Chrome’s internal DNS cache
- Type chrome://net-internals/#dns in your address bar and hit Enter.
- Look for the “Clear host cache” button and click it. Chrome will immediately start building a fresh cache — no need to restart your device.
Windows DNS
- Press the Windows key and type “cmd”.
- Right-click on Command Prompt and select Run as administrator.
- Type the following command and hit Enter:
ipconfig /flushdns - Look for the “Successfully flushed the DNS Resolver Cache” message.
- Restart your device and cross your fingers that it worked.
macOS DNS
- Navigate to Applications > Utilities and open Terminal.
- Paste in this command and smash Enter:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Provide your password when prompted (don’t worry, it’s legit!).
- Once the process is complete, restart your Mac and retest for an error.
That command is the standard flush for current macOS versions, per phoenixnap’s guide to flushing DNS (updated December 2025).
8. Disable your Chrome extensions
Chrome extensions are usually very helpful. But they can go rogue, interfering with how websites load or communicate with your browser.
You can test whether one of your extensions is causing the ERR_CONNECTION_CLOSED error like this:
- Type chrome://extensions/ in the address bar and hit Enter.
- Switch off your extensions one by one, using the little toggle switch next to each tool.
- After disabling each extension, reload the website you were trying to access originally. If the error suddenly clears, the extension you most recently deactivated could be to blame!
9. Update or reinstall Chrome
Google couldn’t be to blame, surely?
Well, it’s just possible that the Chrome browser on your device is having an off day.
To rule out this potential issue, make sure you have the latest version of Chrome. You can check this by visiting chrome://settings/help.
You can also try uninstalling Chrome, and then grabbing a fresh download from the official website. Can’t hurt to try!
10. Reset Chrome’s settings
Another possibility is that your Chrome browser settings are messing with your connection.
The fix here is to reset Chrome to default settings:
Let’s hit that three-dot menu in the top-right corner again. Then, select Settings.
From the left sidebar, click on Reset settings > Restore settings to their original defaults.
Complete the process by hitting Reset settings.
11. Switch your DNS provider
We talked about your DNS cache earlier. That’s basically your computer’s local address book.
Your computer gets those addresses from a larger DNS server, usually provided automatically by your Internet Service Provider (ISP).
If your ISP’s servers have temporary problems, you might stumble upon connection issues.
You can work around this problem by switching to a different DNS provider:
- Cloudflare: 1.1.1.1 and 1.0.0.1
- Google Public DNS: 8.8.8.8 and 8.8.4.4
💡Pro Tip: Cloudflare has great step-by-step instructions on how to install new DNS servers on pretty much any device.
12. Run a malware scan
It’s not a nice thought, but there’s a small chance your connection troubles could be caused by malware.
Just to be on the safe side, we recommend using a trusted program like Malwarebytes (free version available) to run a quick scan. It might resolve the error!
Fixing ERR_CONNECTION_CLOSED on mobile Chrome
Seeing the error on your phone instead? The same logic applies, with phone-sized fixes:
- Toggle airplane mode: Switch it on for a few seconds, then off again. This forces your phone to rebuild its network connections.
- Switch between Wi-Fi and cellular: If the site loads on one but not the other, you’ve found the problem network.
- Clear the Chrome app’s cache: On Android, go to Settings > Apps > Chrome > Storage > Clear cache. On iPhone, open Chrome and clear browsing data via Settings > Privacy and security.
- Reset your phone’s network settings: Both Android and iOS offer a network-settings reset in their system settings. It wipes saved Wi-Fi passwords, so keep those handy.
What if the error keeps coming back?
If a fix works for a day and then the error returns, stop treating the symptom and start isolating the cause:
- Test on a different network: Try another Wi-Fi network or a mobile hotspot. If the error disappears, your home network or ISP is the culprit.
- Update your router firmware and network drivers: Outdated firmware and drivers can drop connections intermittently.
- Consider aging hardware: Routers wear out. If yours is several years old and errors are spreading across devices, a replacement may cost less than the frustration.
- Escalate to your ISP: Keep a note of the dates and times the error appears, then hand that log to your ISP’s support team. Patterns make intermittent faults far easier to trace.
How to fix ERR_CONNECTION_CLOSED on your website
So, you’ve worked through the whole checklist and you’re still seeing the ERR_CONNECTION_CLOSED error on your website.
Bad luck, webmaster. Looks like an issue with your site.
We can fix it, though. Just a few more troubleshooting steps to work through!
Check your hosting IP address
The ERR_CONNECTION_CLOSED error can rear its ugly head when the hosting server of your website is unreachable for some reason. It might be down, for example.
To test this, head over to DNSChecker and type in your website URL. This tool will quickly give you the server IP address.
Next, paste your IP address into the Ping tool on the same site. A reply means the server is reachable. A timeout from every location suggests it’s down or unreachable, although some servers ignore pings by design, so treat the result as a clue, not a verdict.
Check your hosting plan
Every hosting plan has certain limits on things like storage and traffic.
If you go over these limits, it’s possible you’ll just see an error.
You can check this via your hosting panel. At DreamHost, we offer unmetered bandwidth with $0 overage fees on all of our web hosting plans, so this shouldn’t really be an issue.
Just sayin’.
Contact your host
If all else fails, get in touch with your hosting provider. They should be able to figure out what’s going on.
Not to brag, but DreamHost offers 24/7 live support to help you get issues sorted ASAP.
ERR_CONNECTION_CLOSED FAQs
Can a VPN cause ERR_CONNECTION_CLOSED?
Yes. A VPN or proxy that drops or reroutes traffic can close the connection before a page loads. Temporarily disable your VPN and reload the site. If the error clears, try a different VPN server or update the app.
Does ERR_CONNECTION_CLOSED happen in all browsers or just Chrome?
The error code itself belongs to Chrome and other Chromium browsers, like Edge, Brave, and Opera. Firefox and Safari show their own wording for the same failed connection. If one site fails in every browser, suspect that site or its host; if many sites fail, focus on your device or network.
How do I fix ERR_CONNECTION_CLOSED on mobile Chrome?
Toggle airplane mode on and off, switch between Wi-Fi and cellular, and clear the Chrome app’s cache. If the error persists, reset your phone’s network settings (this wipes saved Wi-Fi passwords, so note them first).
What’s the difference between ERR_CONNECTION_CLOSED and ERR_CONNECTION_RESET?
ERR_CONNECTION_CLOSED means the connection was closed unexpectedly, while ERR_CONNECTION_RESET means it was forcibly reset mid-transfer. The fixes overlap, but the causes differ. See our dedicated ERR_CONNECTION_RESET guide for that error.
Is ERR_CONNECTION_CLOSED my website’s fault or my device’s?
Usually your device or network. If only you see the error, the cause is local. If visitors on other networks can’t reach your site either, check your hosting server’s status and contact your hosting provider.
Give your site the gift of reliable hosting
As we’ve discovered in this guide, there are many possible reasons why you could see an ERR_CONNECTION_CLOSED error on your site — from messed up firewall settings to VPN service issues.
Luckily, you don’t have to get too technical to find the fix. Make sure to bookmark this page for the next time you need to troubleshoot!
If your testing points to recurring server-side problems, contact your host first. And if support or reliability keeps falling short, it may be worth comparing providers.
Our plans come with unmetered bandwidth, a 100% uptime guarantee, and 24/7 support. Those features cover the hosting side; your site’s configuration, maintenance, and security still matter.
Compare DreamHost hosting plans to find the right fit for your site.
