How to fix ERR_BLOCKED_BY_CLIENT

If you are someone who heavily relies to Chrome Console to get jobs done, you’ll most likely see a few of these errors pop up every once in a while : ERR_BLOCKED_BY_CLIENT. This error can happens to numerous browsers based on Chromium, namely Google Chrome, Edge, Vivaldi, Opera, Brave, etc. When the error happens, the console would look like this :

In rare cases, the error may be displayed when you visit a specific page.

This article will help you understand why the error happens and what you can do to fix it.

Also see: How to fix “no lapack/blas resources found” on Windows

Why does ERR_BLOCKED_BY_CLIENT error happen?

The error messages pretty much said for itself, but we want to dig deeper into this a bit more.

ERR_BLOCKED_BY_CLIENT usually happens when you let an ad blocker run while browsing the web. The error can be seen more often if you visit modern, complex websites such as Youtube or Google services.

The ad blocker checks each and every URL that the browser request against its list of filters upon a page load. Once an URL match, the ad blocker will automatically block it, sending a “blocked” signal to the browser.

Any URL that was blocked by the ad blocker will be displayed in Chromium Console followed by net::ERR_BLOCKED_BY_CLIENT.

Sometimes, the error message may be a bit different, like Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

Fix ERR_BLOCKED_BY_CLIENT

Since ERR_BLOCKED_BY_CLIENT was caused by an extension, you need to find the extension responsible for the error. Usually it would be one of these : uBlock Origin, Adblock, AdGuard or any extension with “ad” or “block” in its name.

Disabling all extensions and plugins will help you fix “ERR_BLOCKED_BY_CLIENT” in case you don’t know which extension causes the error. If you don’t know how to disable extensions from Chrome, try the steps below:

Step 1: Open Chrome, click the three dots on the upper right corner of the window and then choose More tools from the pop-up window.

Step 2: Then select Extensions from a list of options.

Step 3: Scroll down to find the extension and click the Remove button of the extension. Then, disable them one by one.

Once you’ve disabled all the Chrome extension, the “ERR_BLOCKED_BY_CLIENT” issue should be fixed.

Alternatively, you can create a brand new Chrome profile to avoid manually disabling extensions. If you haven’t done that before, follow these steps :

1. Open Google Chrome.
2. Click the Profile button on the top-right corner.
3. Click the Manage people option.Chrome profile settings
4. Click the Add person button.Create new profile on Chrome
5. Type a name for the new profile.
6. Select an image to identify the profile.
7. Click the Add button.

Once you complete the steps, the new profile will open as an entirely different persona with its own settings, bookmarks, history, passwords, and cookies.

We’ve also written a few other guides on fixing common Chrome error messages, such as How to fix ERR_SSL_PROTOCOL_ERROR, ERR_CLEARTEXT_NOT_PERMITTED, and ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION that you may want to check out.