ERR_CONNECTION_CLOSED means Chrome established a connection to the server but the connection was terminated before the server sent any HTTP response. The connection reached the server but came back empty. Chrome displays this as ‘This site can’t be reached’ with the ERR_CONNECTION_CLOSED code.
This is different from ERR_CONNECTION_RESET (where a TCP RST packet abruptly terminated the connection) and ERR_CONNECTION_TIMED_OUT (where the connection attempt never completed). All three produce similar-looking error pages but originate from different causes and benefit from different diagnostic approaches.
ERR_CONNECTION_CLOSED vs Related Chrome Connection Errors
| Error code | What happened technically | Most common causes |
| ERR_CONNECTION_CLOSED | TCP connection established; server or intermediary closed it cleanly without sending HTTP response | Server crash after accepting connection; TLS handshake completed but server dropped connection; keep-alive timeout; firewall closing idle connections; SSL certificate issues causing server to refuse after TLS |
| ERR_CONNECTION_RESET | TCP RST packet received; connection was forcibly reset rather than cleanly closed | Firewall blocking the connection mid-flight; antivirus intercepting and resetting; router or ISP-level filtering; server sending RST due to load |
| ERR_CONNECTION_TIMED_OUT | No response received within Chrome’s timeout period; connection never fully established | Server not running or unreachable; port blocked by firewall; DNS resolved to wrong IP; overloaded server not accepting new connections |
First Diagnostic: Is It One Site or Many?
The most important diagnostic step: test other HTTPS websites. If multiple sites show ERR_CONNECTION_CLOSED, the problem is in your browser, system, or network. If only one specific site shows the error, the problem is almost certainly on that server.
Open incognito mode (Ctrl+Shift+N) and try the failing URL. If it works in incognito but not in your regular window, an extension or cached data is causing the issue.
| Symptom | Likely cause | Start here |
| One specific site fails; others work | Server-side problem or SSL issue on that site | Site owner section below; or report to the site owner |
| Many HTTPS sites fail simultaneously | Browser-side SSL state; network configuration; antivirus | Clear SSL state, flush DNS, check antivirus HTTPS scanning |
| Works in incognito, fails in regular window | Extension or cached browser data | Disable extensions, clear browsing data |
| Works in Chrome but fails in other browsers | Chrome-specific network setting or SSL flag | Reset Chrome flags at chrome://flags, clear SSL state |
| Started after Chrome updated | Chrome update changed TLS/SSL behavior | Check if site supports TLS 1.2+; test with SSL Labs |
SSL and TLS-Related Causes of ERR_CONNECTION_CLOSED
This error has a specific set of SSL and TLS causes that distinguish it from generic connection problems. Because connections are closed after reaching the server rather than being blocked before, many instances involve the TLS handshake or certificate validation phase.
Expired SSL certificate on the server
An expired certificate causes the TLS handshake to fail. The server may accept the TCP connection and begin the TLS negotiation before Chrome rejects the certificate and closes the connection cleanly. The result is a closed connection with no HTTP response. Check the site’s certificate by clicking the padlock (or the warning icon) in Chrome’s address bar and reviewing the certificate details. If the certificate has expired, the site owner needs to renew it.
TLS protocol version mismatch
Chrome 122 and later versions enforce stricter TLS validation and have strengthened requirements around TLS 1.3 cipher suites. Servers configured to use only older TLS versions (1.0 or 1.1) or outdated cipher suites may see increased ERR_CONNECTION_CLOSED errors from Chrome users. Chrome dropped support for TLS 1.0 and TLS 1.1 in Chrome 84 (2020). A server still configured for TLS 1.0/1.1 only causes Chrome to close the connection after the handshake negotiation fails.
For site owners: run the SSL Labs test at ssllabs.com/ssltest. The test shows which TLS versions and cipher suites your server supports. Ensure TLS 1.2 and TLS 1.3 are enabled and that the server does not exclusively offer outdated cipher suites.
Missing intermediate certificate in the chain
A certificate chain that is missing the intermediate CA certificate causes browsers to fail chain validation and close the connection. Unlike some missing-intermediate scenarios where Chrome fetches the intermediate via AIA, the error can appear as ERR_CONNECTION_CLOSED when the connection fails after the TLS handshake if Chrome cannot validate the chain. The SSL Labs Chain Issues field reveals this: ‘Incomplete’ indicates a missing intermediate.
Antivirus or security software HTTPS inspection
Security products that intercept HTTPS connections (Kaspersky, Bitdefender, ESET, Avast Web Shield, Norton HTTPS scanning) intercept the TLS connection and re-encrypt it. If the interception layer has a compatibility issue with the current Chrome version or the specific server’s TLS configuration, it may close the connection after accepting it, producing ERR_CONNECTION_CLOSED. Test by temporarily disabling the antivirus web protection feature (not the entire antivirus) and retrying.
Visitor Fixes: When the Problem Is on Your Device or Network
Clear Chrome’s SSL state and network cache
Chrome caches TLS session data and security state. A corrupted or conflicting cache entry can cause persistent ERR_CONNECTION_CLOSED for a specific site. In Chrome, go to Settings, Privacy and security, Security, Manage certificates. Or use the keyboard shortcut: press F12 to open developer tools, go to Application tab, Storage, and click Clear site data. For the SSL state specifically, navigate to chrome://net-internals/#hsts and enter the failing domain to check for cached HSTS entries that might be causing issues.
| # Flush DNS cache on Windows (run as Administrator):
ipconfig /flushdns
# Reset Winsock and TCP/IP stack (Windows): netsh winsock reset netsh int ip reset # Restart computer after running these commands.
# Flush DNS on macOS: $ sudo dscacheutil -flushcache $ sudo killall -HUP mDNSResponder
# Flush DNS on Linux (systemd-resolved): $ sudo systemd-resolve –flush-caches |
Disable extensions
Extensions that modify network requests, particularly ad blockers, privacy tools, and VPN extensions, can intercept and close connections. In Chrome, navigate to chrome://extensions and disable all extensions. Retry the failing site. If it loads, re-enable extensions one at a time to identify the conflicting one.
Check VPN and proxy settings
VPN software or proxy configurations that route traffic through intermediate servers can close connections when the VPN server has issues, configuration mismatches exist between the VPN and the site’s TLS version, or when the VPN itself is blocking certain connections. Disconnect any active VPN and test the site directly. If the error clears, the VPN configuration or server is the cause.
Reset Chrome flags
Experimental Chrome flags at chrome://flags can affect network and SSL behavior. Navigate to chrome://flags and click Reset all to default. Restart Chrome and test. This is particularly relevant if the error started after manually enabling or disabling specific Chrome flags.
Update Chrome
Chrome updates include TLS and network bug fixes. An older Chrome version may have a bug that causes ERR_CONNECTION_CLOSED for specific server configurations. Go to Chrome menu, Help, About Google Chrome to check for and apply updates.
Site Owner Fixes: When Visitors Report ERR_CONNECTION_CLOSED
If visitors report this error on your site, the server-side causes are the most likely source. Check these in order.
Verify the SSL certificate
Run the SSL Labs test at ssllabs.com/ssltest on your domain. Check the Certificate section for expiry date and validity. Check Certification Paths for Chain Issues: None (a missing intermediate causes chain validation failures that close connections). Check Protocol Details for TLS protocol support: TLS 1.2 and TLS 1.3 should be enabled.
Check web server error logs
The server’s error logs record connection events. For Nginx, check /var/log/nginx/error.log. For Apache, check /var/log/apache2/error.log or /var/log/httpd/error_log. Look for SSL handshake errors, connection limit errors, or timeout messages at the timestamps when users report the error.
Review keep-alive settings
Web servers close idle connections after a keep-alive timeout. If the timeout is too short, connections may close before browsers complete their requests, particularly for slow clients or high-latency connections. For Nginx, check the keepalive_timeout directive. For Apache, check KeepAliveTimeout and the KeepAlive setting in the server configuration. The defaults are generally appropriate; only adjust if logs show frequent premature connection closures.
Check server resource limits
On shared hosting or undersized VPS instances, resource limits (connection limits, PHP process limits, memory limits) can cause the server to accept a TCP connection and then close it when it cannot allocate resources to handle the request. Check hosting provider control panel for resource usage graphs. If the server is hitting limits during peak traffic, upgrades or optimization may be needed.
Frequently Asked Questions
What does ERR_CONNECTION_CLOSED mean?
ERR_CONNECTION_CLOSED means Chrome connected to the server but the connection was closed without receiving any HTTP response. The connection reached the server but nothing came back before it was terminated. Common causes include an expired or invalid SSL certificate causing the TLS handshake to fail, server-side resource limits closing connections, TLS version mismatches between Chrome and the server, antivirus software intercepting and closing the connection, or a misconfigured web server closing keep-alive connections prematurely.
What is the difference between ERR_CONNECTION_CLOSED and ERR_CONNECTION_RESET?
Both errors mean a connection to a server failed, but through different mechanisms. ERR_CONNECTION_CLOSED means the connection was closed cleanly: a proper TCP close sequence occurred, but no HTTP response was sent before the connection ended. ERR_CONNECTION_RESET means the connection was abruptly reset: a TCP RST packet terminated the connection without a proper close sequence. ERR_CONNECTION_RESET is more commonly associated with firewall blocking and ISP filtering. ERR_CONNECTION_CLOSED more commonly suggests server-side issues like SSL failures, resource limits, or timeout configurations.
Why did ERR_CONNECTION_CLOSED start happening after a Chrome update?
Chrome updates frequently include changes to TLS and SSL handling. Chrome 84 removed support for TLS 1.0 and TLS 1.1. Chrome 122 strengthened TLS 1.3 cipher suite validation. If a Chrome update coincided with ERR_CONNECTION_CLOSED appearing on specific sites, those sites may have SSL configurations that no longer meet Chrome’s current TLS requirements. Run the SSL Labs test on the affected sites to identify configuration issues that Chrome’s updated requirements now reject.
