Google Chrome ERR_HTTP_RESPONSE_CODE_FAILURE: How to Fix It

Easy 10-30 minutes Medium Severity Verified June 2026
Summarize with ChatGPTSummarize with ClaudeSummarize with Perplexity Add as Preferred Source on Google
Error Code
ERR_HTTP_RESPONSE_CODE_FAILURE
Brand
Google Chrome
Product Type
browser
Severity
Medium
DIY Difficulty
Easy
Estimated Fix Time
10-30 minutes
The ERR_HTTP_RESPONSE_CODE_FAILURE error in Google Chrome appears when a web server returns a non-2xx HTTP status code — such as 400, 403, 404, 500, or 503 — and Chrome treats that response as a fatal failure rather than loading the page. This can be triggered by server-side problems, misconfigured extensions, corrupted browser cache, or overly strict network security settings. In most cases you can resolve it yourself in just a few minutes by following the steps below.
Ad

Tools You'll Need

How to Fix Error Code ERR_HTTP_RESPONSE_CODE_FAILURE

  1. Reload the Page and Check the URL

  2. Clear Chrome's Browsing Cache and Cookies

    Clearing cookies will sign you out of most websites. Make sure you know your login credentials before proceeding.

  3. Disable All Browser Extensions

  4. Disable Any Active VPN or Proxy

  5. Flush Your DNS Cache and Renew IP Address

  6. Temporarily Disable Antivirus or Firewall HTTPS Scanning

    Only disable antivirus protection temporarily for testing. Re-enable it as soon as you confirm whether it is the cause.

  7. Change Your DNS Server to a Public DNS

  8. Reset Chrome Flags to Default

  9. Reset Google Chrome Settings

  10. Reinstall Google Chrome

    Before uninstalling, ensure your bookmarks and passwords are synced to your Google account or exported manually so you don't lose them.
Ad

When to Call a Professional

If the error only occurs on one specific website and all other sites load normally, the problem is almost certainly on the website's server, not your browser or network — contact the website administrator or webmaster and report the HTTP error code you see in Chrome's DevTools (press F12, click the Network tab, reload the page, and note the status code next to the failing request). If the error appears across all websites and persists after completing every step above, contact your Internet Service Provider (ISP), as they may have a network-level filtering or proxy issue causing unexpected HTTP responses.

Frequently Asked Questions

What does ERR_HTTP_RESPONSE_CODE_FAILURE mean in Chrome?
It means the web server returned an HTTP status code outside the 200–299 success range — for example, a 400 (Bad Request), 403 (Forbidden), 404 (Not Found), 500 (Internal Server Error), or 503 (Service Unavailable) — and Chrome treated that response as a failure instead of displaying a normal error page. The cause can be on the server side, in your network, or inside Chrome itself.
Is ERR_HTTP_RESPONSE_CODE_FAILURE a problem with the website or my browser?
It can be either. If the error only appears for one specific site and you can reproduce it on a different device or network, the website's server is the likely cause. If the error appears on multiple websites or only in Chrome (while other browsers work fine), the problem is on your end — typically a corrupted cache, a misbehaving extension, an antivirus HTTPS scanner, or a misconfigured proxy or VPN.
How do I find the exact HTTP status code Chrome is receiving?
Press F12 to open Chrome DevTools, click the 'Network' tab, make sure 'Preserve log' is checked, then reload the page. Look for the failing request in the list and check the 'Status' column. Common codes include 403 (access denied), 404 (page not found), 500 (server error), and 503 (server unavailable). This tells you whether the problem originates on the server or in your browser.
Why does ERR_HTTP_RESPONSE_CODE_FAILURE only happen in Chrome and not in Firefox or Edge?
Chrome has its own unique way of handling certain HTTP responses and may flag non-2xx codes as hard failures in situations where other browsers silently redirect or display the response body. Chrome-specific extensions, flags, or cached data can also cause this behavior. If Firefox or Edge loads the same page successfully, start troubleshooting by clearing Chrome's cache, disabling extensions, and resetting Chrome settings.
Can a VPN cause ERR_HTTP_RESPONSE_CODE_FAILURE in Chrome?
Yes. A VPN can alter the routing of your HTTP requests, cause mismatched headers, or route traffic through a server that returns unexpected HTTP responses. Try disconnecting your VPN entirely and reloading the page. If the page loads without the VPN, try switching to a different VPN server location or contact your VPN provider for support.

Related Error Codes