ERR_EMPTY_RESPONSE in Chrome

• Estimated time: 3 min
• Easy
• Low risk

Scope the failure without losing forms or changing the whole connection.

1. If submitting a payment or form, check its outcome through a safe channel before repeating it and preserve unsaved text. For a public page, check the address and reload once.

2. Open two independent sites and the affected address in another available browser on the same device. Only one site fails: follow that branch. Several fail only in Chrome: compare sessions. Several fail in both browsers: compare device/network. Do not install another browser just to complete the test.

• Estimated time: 5 min
• Easy
• Low risk

1. Try the same public page on another trusted device/network if available. If only that site fails across comparisons while others open, check its official status channel or contact its operator. A confirmed incident is a reason to wait, not reset your network.

2. If it opens in another browser on the same device, follow the Chrome session comparison. If it opens only from another network, follow the network branch: the path or filtering may differ, rather than the site being globally down.

• Estimated time: 10 min
• Easy
• Low risk

1. Open the same public page in Incognito without closing the tab containing unfinished work. If it works, the normal session and its data/extensions become more relevant; this does not identify a specific extension. A page requiring sign-in may not be an equivalent comparison.

2. In chrome://extensions, review only extensions you manage. Temporarily disable those that may affect that browsing and re-enable them one at a time after checking. Also check which are allowed in Incognito: do not assume all are absent there. If one reproduces the failure, leave it disabled and contact its developer.

3. If Incognito works but no extension is identified, retain that difference for support before deleting session data. If both modes fail while another browser works, check the version in Help > About Google Chrome and install an offered update. Save forms before relaunching; if unchanged, report the comparison to Chrome support without reinstalling or erasing the profile.

• Estimated time: 10 min
• Easy
• Low risk

1. On another device on the same network, open the same sites; on a phone, make sure it is not silently using mobile data. If they work there, the first device’s configuration becomes more relevant. If they also fail, move to the network branch.

2. Check whether it began after enabling or changing a VPN/proxy you configured. Only on your own unmanaged device, with permission and a public page containing no private data, temporarily compare with the known previous configuration and restore it afterward. If the result changes, contact that connection’s provider with the comparison; do not call it fixed by leaving protection disabled.

3. If there was no known change, do not erase proxy settings, certificates or policies. Inspect security-software alerts without disabling it. On a managed device, give IT the sites, time and comparison with another device.

• Estimated time: 10 min
• Easy
• Low risk

1. If several devices fail, check local connectivity and any expected access portal. If another authorized trusted network is available, test the same sites from the same device; a hotspot may consume data. Do not send credentials over unfamiliar networks.

2. If it works on the other network, the original path—router, provider or filtering—becomes more relevant. Check outages and contact the administrator/provider; on your own home network, a normal router restart may be appropriate if general access also fails and there is no active outage. Warn users first; do not factory-reset it.

3. If the same site fails on different networks while others work, return to the site branch. If everything fails only on one device even after changing networks, return to its configuration. Without another network available, report that limitation instead of changing DNS or TCP/IP to replace the comparison.