CheckWebsiteNow

Connection errors

ERR_CONNECTION_CLOSED

The website closed the connection unexpectedly.

Quick answer

The connection ended normally from a technical view, but too early: the page had not been delivered yet. The server or something on the way ended it.

When to wait: Often yes; try again shortly.

If you are visiting the website

  1. Wait and reload Wait a few minutes, then reload the page once. A server that was restarting is often back quickly.
  2. Try another network Switch from Wi-Fi to mobile data, or the other way round. If the site works there, your network or internet provider may be involved.
  3. Try a private window Open the site in a private (incognito) window. If it works there, an extension or saved site data may be the cause.
  4. Remove saved data for this one site Very large or broken cookies can make a server close the connection. Delete data for this site only; you may need to sign in there again, but saved passwords stay.
    Windows
    In Chrome, click the site-information icon left of the address, then Cookies and site data > Manage on-device site data, and delete the entries.
    macOS
    In Chrome, click the site-information icon left of the address, then Cookies and site data > Manage on-device site data, and delete the entries.
    Android
    In Chrome, tap Page info left of the address bar, then Cookies and site data > Delete.
  5. Pause your VPN or proxy briefly A VPN or proxy (a middle server that forwards your traffic) can close connections early. Test once without it, then turn it back on.
  6. Update your browser Install the latest version and restart the browser.

If you run the website

  1. Check server error logs Look at web server and application logs for the time of the error. A crash or restart in the middle of a request closes the connection without a reply.
  2. Check proxy and keep-alive settings Make sure reverse proxies and load balancers do not close connections before the app replies. Their idle limits should be longer than the app's slowest normal answer.
  3. Test the secure handshake Run openssl s_client -connect example.com:443 -servername example.com (use your domain). If the server closes right after connecting, check your HTTPS setup and certificate files.
  4. Check request size limits Very large headers, often from many cookies, can make servers or proxies give up. Keep cookies small and review header limits.

Is it the website or me?

If other devices and networks show the same error, the website is the likely cause. If only your browser fails, try a private window and remove that site's saved data.

A single occurrence during a server restart is normal. Repeated errors need the owner's attention.

How it differs from ERR_CONNECTION_RESET and ERR_EMPTY_RESPONSE

A closed connection is an orderly goodbye that came before the page was delivered. A reset is an abrupt cancel.

ERR_EMPTY_RESPONSE is close too: the server closed without sending a single byte of reply. In all three cases, the server side or something in between ended the conversation early.

For developers: what happens technically

Chromium uses error -100, which corresponds to a TCP FIN (the normal end-of-connection signal) arriving before the response was complete. The sender may be the app server, a proxy or a load balancer.

Look for crashes, worker restarts, idle timeouts and TLS (encryption setup) failures around the time of the error.

Common questions

Will deleting cookies for this site delete my passwords?

No. Saved passwords are stored separately. You may be signed out of that one site and need to sign in again.

Is the website down?

Maybe briefly. Servers that restart close open connections, and the site often works again after a reload. If the error repeats on every network, the site has a real problem.

Why does it happen only on one page of the site?

That page may crash the app or take longer than a proxy allows. Tell the owner the exact page address and the time.

Likely causes

  • Sometimes The server crashed or restarted during the request. (Website side)
  • Sometimes A proxy, VPN or firewall closed the connection. (Either side)

Is the website down? Check it now

One measurement point. Results explain what we saw, not a worldwide verdict.

Sources

Last reviewed: