Let us Examine the error WordPress err_blocked_by_client and the necessary steps to remove the error. At Bobcares our Server Management Support services will give you a detailed overview of the error and the troubleshooting steps.

WordPress err_blocked_by_client error: Cause 

Adblock or browser safety extensions rely on a set of rules to determine what will get the ban. They contain a list of filters against which a web page’s URI test carry out upon page load. If it gains specific assets and a filter will trigger.

The assets will not be available to the user and the Chrome Console will display the WordPress err_blocked_by_client message.

There could be a difference, such as:

• “failed to load resource: net::ERR_BLOCKED_BY_CLIENT”.

• “chrome failed to load resource: net::ERR_BLOCKED_BY_CLIENT”. The message could also be app- or specific to plugin, such as:

“woocommerce” failed to load resource: net::ERR_BLOCKED_BY_CLIENT”.

How to Fix the “WordPress err_blocked_by_client” Error?

Solving ERR_BLOCKED_BY_CLIENT

There are a few ways to debug and solve a WordPress err_blocked_by_client message.

• Deactivate the add on. This is the most simple solution for a website visitor. Just disable the ad blocker add on causing the issue. This will also allow us to see the resources that are currently under the block stage.
• Register the domain. Many apps that cause this problem allow us to white list specific domains. Just Consider that there is a domain and we do not wish to block any resources. This will also resolve the WordPress err_blocked_by_client  problem.
• Debug the problem. Debugging the error giving assets is the best way. This allows us to avoid issuing an ERR BLOCKED BY CLIENT message to a visitor. Certain add on’s, such as AdBlock Plus, allow us to see which rules are stopping the resources.

Install the ABP, click the ABP extension icon and select Open Blockable Items. This will return a list of URLs as well as the filter that causes the block to trigger. In the following example, the filter.net/ads/ is active.

This causes the assets to ban and Chrome to return an ERR BLOCKED BY CLIENT message. Knowing which filters are causing the resources to block can aid in the error removal process. If a file name has text that triggers the filter we can identify it.

[Need assistance with similar queries? We are here to help]

Conclusion

To conclude we have now gone through the WordPress err_blocked_by_client error by adjusting a few settings put the word by our Server Management support Services at Bobcares.