ERR_CONNECTION_CLOSED means Chrome’s connection to a page ended before the page finished loading. The message does not tell you whether Chrome, an extension, security software, a VPN, the network or the website closed it.
Start by comparing the same page in another browser, on another device and, if available, on another trusted network. These checks can narrow the problem before you delete browser data or change router settings. They do not prove which system closed the connection.
What the error does and does not mean
Google lists ERR_CONNECTION_CLOSED among Chrome’s unavailable-page errors. Chromium’s network error definitions describe it as a closed connection. The code alone is not proof of bad DNS, a broken router or a blocked website.
ERR_CONNECTION_REFUSED means the connection attempt was refused; ERR_CONNECTION_RESET means the connection was reset. The practical checks overlap, but record the exact message rather than treating every loading error as the same fault.
Start with browser, device and network comparisons
| Comparison result | What to check next |
|---|---|
| Only one website fails | Check the site’s status and whether a device or network filter affects that site. |
| The same URL works in another browser | Compare Chrome’s session, updates and optional extensions. |
| Another device works on the same home WiFi | Focus on the affected device’s browser, VPN or security-software logs. |
| Multiple devices fail on home WiFi but work on a trusted hotspot | Check the home connection, router and provider path. |
| The site fails across browsers, devices and networks | Contact the website with the URL and time; avoid repeated local resets. |
Write down the results and the exact URL. The table gives a direction for the next test, not a diagnosis. A website can behave differently across browsers or networks, and an intermittent fault may disappear between tests.
Reload once and check the address
Confirm the web address is correct and reload once. Open the site’s home page rather than an old deep link. A temporary maintenance event or changed page path may clear without any local action.
Do not keep refreshing a payment, form submission or account action. Repeating it can create duplicate requests even when the response page did not load.
Try another browser and Incognito
Open the same URL in another installed browser. If it works there, use Chrome’s menu to open a New Incognito window. Google explains that Incognito starts a separate browsing session, without automatically signing you into sites. Our guide to a website working in one browser but not another covers that branch in more detail.
If Incognito works, cookies, sign-in state or extensions may explain the difference. It is not proof of an extension fault: extensions can be explicitly allowed in Incognito. In More > Extensions > Manage extensions, review recent optional extensions you installed. Test one non-security extension at a time and restore it if nothing changes. Do not switch off security, parental-control or organization-managed extensions. See Google’s extension management instructions.
Restart Chrome and the device normally
Save unfinished work and check active downloads, then quit Chrome and reopen it. If the error remains, restart the computer or phone. Google includes browser and device restarts in its Chrome troubleshooting guidance.
A restart closes stuck processes without changing saved passwords, network profiles or router settings. Test before moving to a more disruptive step.
Check VPN and proxy paths
If you use a VPN or proxy, check its connection status and service notices. Update the client through its official tools. If the service offers another approved server or profile, compare it only when your account and organization policies permit that change.
Do not disconnect required protection or bypass a school or workplace control to make a page load. Contact the administrator or VPN provider with the URL, time and error. A difference between approved profiles is useful evidence, not a reason to change router security.
Check security logs while keeping protection on
If a security or filtering product records a blocked connection at the same time as the error, save that information for support. Check its update status and the vendor’s advice for the specific event. An empty log does not rule the product out.
Keep antivirus, web protection and firewalls enabled. Microsoft warns that turning off Windows Firewall increases exposure to unauthorized access. Do not add broad exceptions, open ports or change organization policies based on this error code.
Use another device on the same WiFi
Open the page on a phone or tablet connected to the same home network. If every device fails on one site, check the site’s public status or contact its owner. If every site fails, test the internet connection itself.
If only one computer fails, router changes are unlikely to be the first answer. Return to the browser, VPN, proxy, security software and operating-system network settings on that device.
Compare the home network with a hotspot
If your device and data plan allow it, connect to a phone hotspot you trust and load the same page. Follow workplace rules for managed devices. Success there makes the home connection worth investigating, but does not identify whether the router, provider, filter or website’s handling of that path is responsible.
Stop after the test if mobile data is limited. Do not download large files just to prove that a simple page opens.
Restart the router without resetting it
If multiple home devices show the error, restart the modem, gateway or router with its normal power procedure. Wait for the provider connection and standard status lights before testing again.
Do not press a recessed Reset button. A factory reset erases configuration and is not part of Google’s ordinary recommendation to restart the modem and router.
Check public WiFi sign-in
If the error happens only on hotel, airport or cafe WiFi, check whether the network requires a sign-in page. Use its official notification or ask the venue for the correct portal. Google’s connection and loading guidance includes checking public-network sign-in.
Do not dismiss certificate warnings, disconnect required protection or enter confidential information just to complete a test. Completing a portal does not make a public network trustworthy. Use another approved connection if the portal conflicts with your security requirements.
Update Chrome and the operating system
Install current stable Chrome and operating-system updates through their official update tools. Restart if requested. An outdated browser or network component can fail after a website or security service changes.
Do not download a browser installer from an ad or third-party software site. Before considering reinstallation, collect the comparison results and follow the browser vendor’s instructions, including any warning about data loss.
Do not assume DNS is the cause
ERR_CONNECTION_CLOSED is not a DNS-specific code. If the hostname cannot be resolved, Chrome normally reports a name-resolution error. Leave DNS on its known-good automatic setting unless a separate test or administrator identifies the resolver.
Random command-line flushes, network resets and public DNS addresses can hide the original pattern. Use them only when the operating-system or network vendor’s current instructions match the evidence.
Compare nearby Chrome error codes
If the code changes to ERR_CONNECTION_RESET, record the new message before continuing. If it changes to ERR_CONNECTION_REFUSED, use the refused-connection checks. Neither message identifies the responsible component by itself.
Google’s common Chrome error guide groups page-loading codes by what Chrome observed. Keep the newest exact message in your notes.
When to contact the website, provider or device support
- Contact the site owner when only that site fails across browsers, devices and networks.
- Contact the internet provider when multiple devices fail only on the home connection.
- Contact device or security-software support when one device fails on every network.
Report the exact code, URL, time and comparison results. Say whether the error is constant or intermittent. These details help support choose a focused test; they do not establish who closed the connection.
Keep the fix matched to the pattern
Use each comparison to choose the next check. If Incognito works, compare the normal Chrome session and optional extensions. If a hotspot works, investigate the home connection. If the same site fails across browsers and networks, contact its operator. Change one thing at a time so you can tell what affected the result.
After an approved change, repeat the same URL in the same browser and record the result. Keep security protections on throughout. If the page only works after bypassing a control, ask the responsible provider or administrator to resolve it.
