Quick answer: ERR_INVALID_RESPONSE: Chrome was able to connect to the server, but the server failed to respond in a way that is acceptable to Chrome. One of the reasons for this is normally some kind of browser extension, a corrupt browser cache, using a VPN or proxy, or simply the behaviour of the server or CDN
What This Error Means
The request that was sent by Chrome was malformed, unexpected or interrupted while waiting for a response. This distinguishes it from a failure in DNS to find the server, and from a failure to make the connection, because the server doesn’t respond.
Most of the published guides contain this code’s brother-sisters, like ERR_EMPTY_RESPONSE, ERR_HTTP2_PROTOCOL_ERROR, etc., but not this particular one. Troubleshooting strategy is mostly common and the logic is the same for all these errors, which are the result of an unexpected response, and that is why I’ve used it here. If you need an exact definition, check the list of network errors for Chromium.
One guide cites that the server is sending the message that one it did not anticipate at all, and Chrome simply closes. Another states that in Chromium browsers, ERR_EMPTY_RESPONSE is an error code returned by value of -324.
The Split Test Ladder
The Split Test Ladder (Original Framework)
Rather than attempt all the fixes, identify where the problem resides. This is an editorial approach instead of it being an official Chrome procedure.
- Open Incognito Browser. Incognito disables extensions and does not accept your normal cookies, therefore, things that use extensions and cookies are disassociable with those that use server and connection causes. If the page does load up, the reason is local.
- Change the browser/device. If it fails everywhere, then it’s likely that the site or your network is at fault.
- Use another network. You can switch from Wi-Fi to mobile data or turn off your VPN. If so, it’s likely the network or VPN is modifying the response.
- Review the original answer. To view what the server returns, just use curl -v https://example.com from a terminal.
| Result | Likely location |
| Corrupted cache or extension (Incognito). | |
| Works on another network | VPN, proxy, DNS or ISP |
| Fails on all devices and networks | Server / CDN / site configuration |
| Received unexplained or empty reply from curl | Problem on the server side |
Fixes You Can Try as a Visitor
Work from least to most disruptive.
- Disable extensions. Responses can be blocked or response header modified by using an ad blocker, VPN extension, security tools. Switch off everything that is an extension in chrome://extensions and switch them back on, one by one, to determine which one is the cause.
- Clear Cache and Cookies. When a cache entry is corrupted, it may persist in returning a bogus answer. Clearing clears corrupt files and cookies.
- Flush DNS. DNS records are cached by both Chrome and your operating system. Empty Clear Chrome’s cache (chrome://net-internals/#dns) and then flush the system’s DNS cache.
- Switch to a different DNS server. If your DNS is misbehaving then one suggestion is to use public resolvers 8.8.8.8 or 8.8.4.4.
- Disable VPN or proxy. Virtual Private Network (VPN) or proxy can be used to rewrite traffic before it enters Chrome.
- Update Chrome. A common reason for browser-based error is the outdated versions of browsers.
- Or, reset or reinstall Chrome. Use these only when necessary. The sibling error list suggests reinstalling Chrome and resetting everything up to now as among the things that normally don’t fix it.
If none of this helps, then the server itself must be wrong and there is no you can do to correct this. If so, wait for the owner of the website to fix it.
Fixes If You Run the Site
If you are running the Site, there is a Fixes If You Run the Site section.
If visitors report the error, be sure and check the server side. The points are as per general practice and the sibling error guidance, so please check the points on your own stack.
- Review server logs for script failures, crashing processes or unexpected stoppage.
- Skip the CD or proxy. CDN or proxy services, like Cloudflare, may not be able to communicate with the origin and deliver empty or invalid reply. Go to proxy turned off or bypass.
- Check for damage to configuration. Bad .htaccess file in Apache, or a WordPress plugin can prevent the server from completing requests.
- Review resource limits. If no full HTTP response is received, correct configuration errors or increase the ressources limits.
- Check firewall rules. If this is a corporate network or a hosting network, a firewall could stop requests without notifying.
- Purge caches. Clearing a server-side cache causes the server to return a new response.
Related Errors at a Glance
Quick + easy comparison of related errors at a glance for the software (Original comparison)
It is an editorial comparison out of several scenarios encoded in the code.
| Error | Signals what error type it is |
| ERR_INVALID_RESPONSE | Reply received, but not valid. |
| ERR_EMPTY_RESPONSE | Connection made, but no response was received. |
| ERR_CONNECTION_REFUSED | The error message is ERR_CONNECTION_REFUSED (because the server refused the connection). |
| ERR_HTTP2_PROTOCOL_ERROR | The response was not as expected on HTTP/2. |
Troubleshooting Checklist
Troubleshooting Checklist (Linkable Asset):
- Examine the page in anonymous (Incognito) window
- Used other web browser and other device
- Switches network or disables the VPN
- Disabled extensions and re-enabled one at a time
- Removed cookies and data from the website and cache
- Cleaning of the flushed Chrome and system DNS caches
- Updated Chrome
- Try making a curl to the URL and check the response.
- Checked server logs, CDN settings and plugins
- As the final step, reset and reinstall it.
Guest Post Angles
The following topics are appropriate for web hosting/browser/browser support publications:
- Understanding Chrome error codes: ERR_ What happened?
- CDN and origin issues: troubleshooting when Cloudflare is failing.
- Why Incognito fixes pages: extension, cookies and cache explained.
Divide and Conquer Approach
Divide and conquer Approach:formerly known as ‘Divide and conquer’ approach.
The next time ERR_INVALID_RESPONSE shows up, it’s best not to attempt all err invalid response fixes at once. The four split tests, determine if the issue is the browser, network and/or server, and then only update those fixes. That way you will save time as well as know if the site owner was at fault for the busted website, or yours was.
