ERR_FAILED Error: Causes & Step-by-Step Fixes

If you see ERR_FAILED or net::ERR_FAILED (often paired with “This site can’t be reached”) in Google Chrome, the request did not complete — but Chrome gives you almost no details why.  Good news: Most people fix this in under 5 minutes by following the quick steps below.

What Does ERR_FAILED Mean in Chrome?

ERR_FAILED is Chrome’s generic way of saying “the request did not complete,” without giving the exact reason. It can be caused by the browser, your network, security software, or the website itself.

It commonly appears when:

A page refuses to load

A file upload stops halfway

An API request fails in Chrome DevTools

Localhost or a development server does not respond correctly

A security tool blocks the request

A proxy, CDN, or server times out

Quick way to narrow it down:

Only in Chrome → likely browser or local issue.  

Across browsers or devices → network, server, or CDN issue.

Most Common Causes of ERR_FAILED

The error usually falls into one of these five groups:

Browser-side (cache, extensions, outdated Chrome, Service Workers)

Network/DNS problems

Security software/VPN interference

Server/development issues (CORS, SSL, timeouts)

CDN/infrastructure blocking (especially Cloudflare)

First: Quickly Identify the Cause

Use this simple table to zero in on the problem:

Scenario	Likely Cause
Only one website fails	Server or site-specific issue
All websites fail in Chrome	Browser, profile, extensions, or local network
Only one device is affected	Local system problem
Only one network is affected	DNS, router, VPN, proxy, or firewall
Only Chrome is affected	Extensions, cache, profile corruption
Only uploads or API requests fail	CORS, timeouts, security rules, or proxy settings

Quick Fixes That Solve Most Cases

Try these in exact order. The majority of users solve the error with steps 1–5.

0. Confirm your internet works

Open the same page in another browser (Edge, Firefox) or on your phone. If it fails everywhere, the issue is your network, router, or the site itself — not Chrome.

1. Hard refresh the page

Windows: Ctrl + F5

Mac: Cmd + Shift + R

2. Open the page in Incognito mode

Windows: Ctrl + Shift + N

Mac: Cmd + Shift + N

If it works here → an extension is causing the problem.

3. Clear cache and cookies

Go to chrome://settings/clearBrowserData

Select:

• Cached images and files  
• Cookies and other site data

Time range: All time → Clear data → Restart Chrome.

4. Disable all extensions

Go to chrome://extensions/

Toggle everything off, test the page, then re-enable one by one.

5. Disable hardware acceleration (often overlooked fix)

Go to chrome://settings/system

Turn off Use hardware acceleration when available → Relaunch Chrome.

6. Flush DNS and reset network stack

Windows (Command Prompt as Admin):  

ipconfig /flushdns

netsh winsock reset

netsh int ip reset

ipconfig /release

ipconfig /renew

Restart your computer.

macOS (Terminal):  

sudo dscacheutil -flushcache

sudo killall -HUP mDNSResponder

Reconnect to the network.

7. Temporarily disable antivirus, firewall, or VPN

Turn them off → reload the page. If it works, add the site to the allowlist.

8. Switch to public DNS servers

Try Google (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1 / 1.0.0.1). Restart Chrome.

9. Update Chrome

Go to chrome://settings/help → Check for updates → Restart.

10. Reset Chrome settings (last resort)

Go to chrome://settings/reset → Restore settings to original defaults.

Bonus quick check: Make sure your computer’s date and time are set correctly — wrong system time often triggers silent ERR_FAILED errors.

Fixes for Specific Scenarios: ERR_FAILED on Localhost, Uploads, Cloudflare

Localhost and API Requests (Developers)

Verify correct Access-Control-Allow-Origin header (never use * with credentials).  

Use a trusted local SSL certificate.  

In DevTools → Application tab → unregister any broken Service Worker.  

Clear any Service Worker cookies named after your app.  

For React/Vite/etc.: double-check dev server proxy settings.

File Uploads

Increase server request timeout and upload size limits.  

Check reverse-proxy timeout settings.  

Pro tip: In Chrome DevTools → Network tab, look at the failed request. Empty or zero Response Headers usually means a timeout.  

Look in server/proxy logs for “context timeout”, “canceled”, or “request terminated”.  

Test by temporarily bypassing the proxy.

If the server or CDN seems to be filtering your IP, test the upload from a different IP address quickly.

Cloudflare-Protected Sites

Check Cloudflare Security Events / Firewall / Bot Management.  

Look for rate limiting, Managed Challenge, Bot Fight Mode, or challenge/block actions.  

Whitelist the IP or adjust the rule causing the block.  

Suspicious request headers are a common culprit on POST/API requests.

If Cloudflare appears to be blocking your IP, try a reliable proxy to route your request through a different residential IP and test whether the block is IP-specific.

macOS and Enterprise Environments

Create a new Chrome profile.  

Test in Chrome Canary.  

Check endpoint protection/antivirus rules.  

Try a different network to see if it’s organization-wide.

Advanced Diagnostics(If Quick Fixes Still Don’t Work)

1. Open DevTools (F12) → Network tab and inspect the failed request.  

2. Right-click the request → Copy as cURL and test it in your terminal.  

3. Go to chrome://net-export/ to export full network logs.  

4. Check Service Workers in DevTools → Application tab.

Still not fixed? Reply with your exact scenario (localhost? upload? specific site?), what you’ve already tried, and a screenshot of the Network tab — the cause is almost always visible there or in server logs.

How to Prevent ERR_FAILED in the Future

You cannot prevent every network failure, but you can reduce the chance dramatically:

Keep Chrome updated  

Clear cache every few weeks  

Use only essential extensions  

Test sites in multiple browsers  

Stick with stable DNS servers  

Monitor server, CDN, and proxy logs  

For developers: validate CORS, cache-control headers, and upload limits before release

FAQs

1. What does ERR_FAILED mean in Chrome?

Chrome could not complete the request, but it doesn’t specify why.

2. Is ERR_FAILED a browser error or a server error?

It can be either. Chrome-only = browser issue. Happens everywhere = server/network/CDN issue.

3. Why does ERR_FAILED happen on localhost?

Usually CORS, SSL certificate, Service Worker, or proxy misconfiguration.

4. Why does ERR_FAILED happen during uploads?

Timeouts, size limits, proxy interruptions, or security filters.

5. Why does ERR_FAILED appear only in Chrome?

Cache, extensions, profile corruption, or Chrome-specific settings.

6. What is the fastest fix to try first?

Incognito mode → clear cache & cookies → disable extensions.

Final Thoughts

ERR_FAILED is deliberately vague, but the cause is almost always one of the fixes above. Start with the quick steps and diagnosis table, then move to the specific scenarios if needed.  For everyday users, cache/extensions or DNS fixes solve it. For developers and IT teams, it’s usually CORS, Service Workers, proxy timeouts, or Cloudflare rules.