3 quick ways to fix blocked by client Chrome error

by Ola-Hassan Bolaji
Ola-Hassan Bolaji
Ola-Hassan Bolaji
A Computer Engineering graduate, he has spent most of his life reading and writing about computers. He finds joy in simplifying complex topics into simple solutions for PC... read more
Affiliate Disclosure
  • ERR_BLOCKED_BY_CLIENT is one of the common errors users face on Chrome majorly due to extensions.
  • Another possible cause is the accumulation of corrupt browser data and files.
  • One quick solution to this error is to disable suspicious add-ons and plugins.
chrome error blocked by client
Instead of fixing issues with Chrome, you can try a better browser: OperaYou deserve a better browser ! 350 million people use Opera daily, a fully-fledged navigation experience that comes with various built-in packages, enhanced resource consumption and great design. Here's what Opera can do:

  • Easy migration: use the Opera assistant to transfer exiting data, such as bookmarks, passwords, etc.
  • Optimize resource usage: your RAM memory is used more efficiently than Chrome does
  • Enhanced privacy: free and unlimited VPN integrated
  • No ads: built-in Ad Blocker speeds up loading of pages and protects against data-mining
  • Download Opera

Chrome is one of the best browsers with adblocker currently available on the market. While the adblocker helps to improve your browsing experience, it is proven to be one of the causes of Chrome error blocked by client.

This is because it checks every URL you try to load on your browser and runs it through its filters. If the URL matches the ad blocker’s flagging requirements, it automatically blocks it. Hence, the err blocked by client prompt.

This guide will help you solve this error, displayed as ERR_BLOCKED_BY_CLIENT, and allow you to visit your valuable websites again without restrictions.

How can I solve the blocked by client error on Chrome?

1. Disable extensions

  1. Click the menu button (the three vertical dots) on the top right corner.
  2. Select the More tools option.
    settings extension
  3. Choose Extensions from the options displayed.
    disable extension chrome error blocked by client
  4. Now, toggle the switch of the Extensions backward to disable them.
  5. Finally, close and relaunch Chrome.

Your target extensions to be disabled should be the adblocker and other security-related ones since they are the chief causes of the failed to load resource: net::err_blocked_by_client issue.

But you can also disable all the extensions and check if the issue is solved. If Chrome works fine, you can start enabling them one after the other to know the one causing the problem.

2. Clear browsing data

  1. Click on the menu button and select the More tools option.
    settings chrome data clear
  2. Select the Clear browsing data… option.
  3. Check the checkboxes for Browsing history, Cookies and other site data, and Cached images and files.
    clear data chrome error blocked by client
  4. Now, click the Clear data button and restart Chrome.

3. Try an alternative browser

If the net::err_blocked_by_client image still appears after attempting all the fixes above, you might want to try out another browser in Opera.

Opera is a versatile browser based on the same Chromium engine as Chrome. Hence, it boasts the speed and other performance features associated with Chrome.

It has an intuitive interface that you can customize to your taste. Thanks to its free VPN and other privacy and security features, it is also one of the most secure browsers.

While it is true that Opera has a built-in ad blocker, it is fully customizable and can be disabled to allow you to visit any website.

It just gives you the security and speed you need without having to face errors frequently.

Get Opera

Being unable to load a popular page like YouTube due to the ERR_BLOCKED_BY_CLIENT can take the fun out of your browsing session. Though it can be pretty annoying, the solutions are simple and direct.

Are you facing other issues like Chrome error code 5? Check out our extensive guide to fixing it.

Feel free to discuss the fix that got Chrome working properly again in the comments section below.

This article covers:Topics: