ERR_FAILED in Chrome: Generic Error Causes and Fixes

ERR_FAILED is Chrome's generic failure code: "This page isn't working" or "This site can't be reached" with ERR_FAILED at the bottom. Chrome did not get a more specific reason, so the message does not say what went wrong. Because it is a catch-all, the fastest approach is a process of elimination that separates the browser, the network and the site.

You may also see it in DevTools as net::ERR_FAILED next to a request that failed in the Network tab, which is common with cross-origin requests, blocked redirects and failed preflights. Console details usually tell you more than the page does.

Triage in two minutes

1. Open the same URL in another browser and on another network (mobile data).
2. Use Down From Where to see whether the site responds from other regions.
3. Open the URL in an incognito window.

If you are a visitor

1. Reload and check the URL. Typos and stale bookmarks cause failed navigations.
2. Disable extensions. Ad blockers, privacy tools, download managers and VPN extensions often produce ERR_FAILED. Use chrome://extensions and disable them one by one. Blocked requests may show ERR_BLOCKED_BY_CLIENT instead.
3. Clear cache and cookies for the site, or for all time if you suspect corruption.
4. Check for a managed browser. On a work or school computer, enterprise policy can block sites or protocols. Visit chrome://policy to see active policies; only an administrator can change them.
5. Turn off VPN or proxy, and review proxy settings in the operating system. See ERR_PROXY_CONNECTION_FAILED.
6. Flush DNS (ipconfig /flushdns on Windows) and try a public resolver.
7. Update Chrome, then relaunch. Outdated builds can fail on modern TLS or HTTP/3 features.
8. Check for a local file path. If the URL starts with file://, you are probably looking for ERR_FILE_NOT_FOUND.
9. Reset Chrome settings (Settings, Reset settings) as a last measure before reinstalling.

If you own the site

1. Read the real error in DevTools

Open DevTools, Network tab, and select the failed request. Check Status, Headers and the Console message. A failed fetch to another origin typically also logs a CORS message; see CORS: no Access-Control-Allow-Origin and test with the CORS Checker.

2. Download or content-type problems

Chrome shows ERR_FAILED for a download that is blocked, for example by Content-Disposition issues, unsafe file types or a mismatch with the declared size. Inspect headers with the HTTP Header Checker:

curl -sI https://example.com/file.zip

3. Redirect trouble

Redirects to a blocked scheme (such as a custom protocol), to an unsafe port or to a host that fails will end in this error. Trace them with the Redirect Checker. Port issues are covered in ERR_UNSAFE_PORT.

4. TLS and certificates

Chrome may fail without a friendly page if a subresource has a broken certificate or a client certificate is required. Check with the SSL Checker. Related: ERR_BAD_SSL_CLIENT_AUTH_CERT.

5. Server crashes and aborted responses

If the server drops the connection during the body, Chrome may report a generic failure. Check the error logs and test with:

curl -v https://example.com/ -o /dev/null

See ERR_CONNECTION_RESET and ERR_EMPTY_RESPONSE.

6. Service workers and extensions you ship

A buggy service worker can make requests fail with this code, since it intercepts fetches. In DevTools, open Application, Service Workers, tick "Bypass for network" or unregister the worker, then reload.

7. Content Security and framing

A page that tries to load in a frame disallowed by headers shows different errors, but misconfigured policies can also cause generic failures. See refused to display in a frame.

Verify

Reproduce the failing request in an incognito window with extensions off. Confirm a clean 200 with the HTTP Status Checker and run the Website Health Check.

Next steps

• Read Why is my website down?.
• See the general this site can't be reached page.
• Check ERR_TIMED_OUT for the timeout variant.
• Learn about SSL/TLS certificate errors.

FAQ

What does ERR_FAILED mean?

Chrome could not complete the request and had no more specific code to show. You must examine the extension, network and server layers to find the cause.

Is it Chrome's fault or the site's?

Test in another browser and network. If it fails everywhere, the site is at fault; if only in Chrome, suspect extensions or policy.

Why do I see it only in DevTools?

Subresource requests, such as scripts or API calls, can fail with net::ERR_FAILED while the page itself loads. CORS and blockers are common reasons.

Does clearing cookies help?

Sometimes, if a bad cookie or cached redirect is involved. It is cheap to try but not a universal fix.

This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.