How to Fix ERR_BLOCKED_BY_CLIENT in Chrome

By ErrorFix · Updated October 26, 2026 · 7 min read

What ERR_BLOCKED_BY_CLIENT means

Most browser errors describe something going wrong on the way to a website: a missing DNS record, a refused connection, a timed-out server. ERR_BLOCKED_BY_CLIENT is different, and the name gives it away — the block happened on the client, meaning your browser or software on your own device. The request never left your computer, so the website never even saw it, and no amount of waiting or refreshing on the site's side will fix it.

In practice, the blocker is usually an extension. Ad blockers work by intercepting every request a page makes and cancelling the ones that match their filter lists: ad scripts, trackers, and sometimes whole pages or images that look like ads. When Chrome cancels a request that way, it shows ERR_BLOCKED_BY_CLIENT. Privacy extensions, script blockers, VPN extensions, and antivirus web shields do the same thing for their own reasons, which is why the fixes below work through each possible blocker in turn, starting with the most common one.

Common causes

• Ad blocker blocking a page resource: the page loads a script, image, or frame that matches a filter-list rule, and the blocker cancels the request.
• Another extension intercepting requests: privacy tools, script blockers, VPN extensions, and coupon finders can all block requests Chrome then reports as client-blocked.
• Antivirus or firewall web shield: security software scanning your traffic can block a page or resource it considers risky, even when the site is safe.
• Corrupted cookies or cached data: a stale cookie or cached redirect for that site can make Chrome treat the request as blocked on repeat visits.
• Chrome settings or unwanted software: a changed Chrome setting, an enterprise policy, or malicious software on your computer can force requests to be blocked.

How to fix ERR_BLOCKED_BY_CLIENT — step by step

Work through these fixes in order. Most cases are fixed by step 2 or 3.

1. Confirm the pattern with a reload and an Incognito window. Start by pinning down exactly what is blocked. Reload the page with Ctrl + F5 (Cmd + Shift + R on a Mac) to rule out a one-off glitch, and note whether the error appears on one site only or on many sites. Then open an Incognito window (Ctrl + Shift + N), where extensions are off by default, and try the same page. If it loads in Incognito but not in a normal window, something installed in your normal profile is blocking it — almost always an extension. If it fails in Incognito too, the blocker is more likely your antivirus, a VPN, or a network-level filter, and steps 5 and 6 will matter more.
2. Whitelist the site in your ad blocker. Ad blockers are the single most common cause of this error: they block scripts, images, or whole pages they classify as ads or trackers, and Chrome reports the block as ERR_BLOCKED_BY_CLIENT. Click your ad blocker icon in the toolbar and choose the option to pause it or allow ads on this site — in uBlock Origin it is the power button, in AdBlock it is the Don't run on pages on this site option. Reload the page. If it loads, you have found the cause and the fix at once: keep the site whitelisted, or, if you prefer to keep blocking ads there, use the blocker's element picker to unblock only the specific resource the page needs instead of allowing everything.
3. Disable extensions one by one to find the culprit. If whitelisting the ad blocker did not help, another extension may be doing the blocking — privacy tools, script blockers, VPN extensions, and coupon finders all intercept requests. Type chrome://extensions in the address bar and toggle off every extension, then reload the page. If it works, turn extensions back on one at a time, reloading after each one, until the error returns: the last one you re-enabled is the culprit. Remove it or keep it disabled for that site. Pay special attention to extensions you installed recently — if the error started right after adding one, that extension is the prime suspect even before you test the rest.
4. Clear the site's cookies and cached data. A corrupted cookie or a stale cached redirect can also trigger a client-side block, especially on sites where you are signed in. Click the lock or tune icon next to the address bar, choose Site settings, and click Delete data (or Clear data) for that site. Alternatively, press Ctrl + Shift + Delete, set the time range to All time, tick Cookies and other site data and Cached images and files, and click Delete data. Sign back in to the site afterward — clearing cookies logs you out — and reload the page. If the error is gone, a bad stored item was the problem, and you do not need to change any extension settings.
5. Turn off your VPN, proxy, and antivirus web shield for a test. Software outside Chrome can block requests before Chrome even reports them, and Chrome blames the client. Disconnect your VPN completely and turn off any proxy in your system settings, then reload the page. If your antivirus has a web shield, web protection, or secure browsing feature, pause it briefly for the test and re-enable it right after — if the page loads while it is paused, add the site to the antivirus allowlist or switch the shield to a less aggressive mode. Re-enable each tool one at a time afterward so you know exactly which one was responsible, and never leave your antivirus off permanently for a single website.
6. Reset Chrome settings and scan for unwanted software. If nothing above helped, reset Chrome to a clean state. Go to Settings, then Reset settings, and choose Restore settings to their original defaults — this disables extensions, clears temporary data, and resets the startup and search settings without deleting your bookmarks, history, or saved passwords. Then run Chrome's built-in safety check under Settings, then Privacy and security, then Safety Check, and let your antivirus run a full scan: malicious or poorly written software installed on your computer can inject a blocking extension or proxy that survives normal troubleshooting. After the reset, reinstall only the extensions you actually use, and test the page before adding each one back.

Did this fix it? Quick checklist

• The page loads without ERR_BLOCKED_BY_CLIENT
• It works with the site whitelisted in your ad blocker
• Other websites still load normally
• The error stays gone after re-enabling your other extensions

If the page loads only with your ad blocker paused, that is a complete fix, not a workaround: whitelisting one site you trust leaves your protection intact everywhere else. If the error follows you to every site and every browser, the blocker is outside Chrome — your antivirus, VPN, or network filter — and step 5 is where the answer lives. And if the error appears only in your normal Chrome profile but never in Incognito, an extension is responsible, and step 3 will name it.