What Is ERR_FAILED and How Do You Fix It in Chrome?

ERR_FAILED is a generic error code that Chrome shows when it fails to load a page or resource. The browser then shows ERR_FAILED on the “This site can’t be reached” or “This page isn’t working” screen, and in the Console tab of the developer tools it appears as net::ERR_FAILED. Because the code is generic, it has no single cause; in this guide we go through the most common causes and fixes in order.

What Does ERR_FAILED Mean?

Chrome’s network layer usually reports why a request failed with a specific code (for example ERR_CONNECTION_TIMED_OUT for a timeout). ERR_FAILED means the request failed but no more specific code was given. To fix it, you first need to work out whether the problem is in the browser, on the computer or on the site.

Causes of the Error

• Browser extensions: Ad blockers, privacy and VPN extensions that block or modify requests.
• Damaged cache or profile: Corrupted cache files or a damaged Chrome user profile.
• Security software and firewalls: Antivirus web protection can cut Chrome’s connection.
• Proxy settings: If an unreachable proxy is configured, requests fail.
• Service Worker problems: If a site’s background script returns a faulty response, the page may not open.
• CORS blocking (for developers): When a request to another domain is blocked because the server does not send the required CORS headers, the console shows net::ERR_FAILED.

How to Fix ERR_FAILED

1. Open the Page in an Incognito Window

Open an incognito window with Ctrl + Shift + N and try the site. Extensions are off by default in incognito windows. If the page opens, the problem is an extension: turn extensions off one by one on the chrome://extensions page to find the problem one.

2. Clear the Cache and Site Data

At chrome://settings/clearBrowserData, clear “Cached images and files” and “Cookies and other site data”. If only one site has the problem, deleting that site’s data from the site information icon in the address bar may be enough; this also removes the site’s Service Worker registration.

3. Check Security Software and Proxy Settings

Briefly turn off your antivirus web protection or HTTPS scanning and try again. On Windows, if a manual proxy is set under Settings > Network & Internet > Proxy, turn it off. Make sure Chrome is not blocked in the firewall.

4. Reset Chrome Settings or Try a New Profile

Use “Restore settings to their original defaults” on the chrome://settings/reset page. This does not delete your bookmarks or saved passwords. If the problem continues, create a new Chrome profile and try again; if it works in the new profile, the old profile may be damaged.

5. Reset Network Settings

Open Command Prompt as administrator, run the commands below, then restart the computer:

ipconfig /flushdns
netsh winsock reset
netsh int ip reset

For Developers: net::ERR_FAILED in the Console

If the console shows net::ERR_FAILED together with “has been blocked by CORS policy”, the request was blocked by the browser’s CORS rules. The server receiving the request must return the Access-Control-Allow-Origin header with your site’s origin and answer preflight (OPTIONS) requests correctly. The problem is not in the browser but in the configuration of the API being called.

For similar cases where the server closes the connection, see our guide on ERR_CONNECTION_CLOSED, and for cases where it is reset, see ERR_CONNECTION_RESET.

Conclusion

ERR_FAILED is a generic error code and is usually caused by extensions, a damaged cache, security software or proxy settings. Testing in an incognito window quickly shows where the problem comes from. If you are a developer, look at the CORS messages in the console and the headers of the server being called.