Browser / Network

ERR_BLOCKED_BY_CLIENT

A browser extension (usually an ad/tracker blocker) blocked the request — not the server.

What it looks like

GET https://www.google-analytics.com/analytics.js net::ERR_BLOCKED_BY_CLIENT

What does "ERR_BLOCKED_BY_CLIENT" mean?

Shown in the DevTools console or Network tab. “Client” means the browser itself: an extension cancelled the request before it left your machine, so the server never saw it and there is nothing to fix on the server.

What causes "ERR_BLOCKED_BY_CLIENT"?

• An ad blocker or privacy extension matched the URL.
• The path contains words like ads, track, analytics.

How do I confirm the cause?

1. Reload in a private window with extensions disabled. If the error disappears, an extension is responsible.
2. Look at the blocked URL — paths with words like ad, ads, banner, track or analytics are what filter lists usually match.
3. Disable extensions one at a time to find which one is doing the blocking.
4. In Chrome’s Network tab these requests show a status of (blocked:other) instead of an HTTP code, confirming the block happened inside the browser.

How do I fix "ERR_BLOCKED_BY_CLIENT"?

• Disable extensions and retry to confirm.
• Rename/relocate the blocked endpoint if it's your own.
• It's harmless if it's a third-party tracker.

How do I stop it happening again?

• Avoid naming your own files and endpoints with ad or tracking keywords (ads.js, /track, banner.png).
• Make the page work even when analytics or ad scripts fail to load, so a blocker cannot break it.

Got a different error? Paste it into the Explain This Error tool → Identifies the family and the fix — runs locally, nothing uploaded.

Related errors