Fix “Requests to the server have been blocked by an extension” in Chrome/Microsoft Edge

At the moment, the lion's share of the desktop browser market belongs to Google Chrome, and there is every reason for this.The Chromium project, on which Google Chrome is mainly based, is a very good browser by design. It can be used as a framework to quickly create a fast, modern and feature-packed browser.

A few notable name in the market are Google Chrome itself, Microsoft Edge, Vivaldi, Brave, Opera. They all share the same browser core, therefore if you use one of them, there's a high chance you might have seen "Requests to the server have been blocked by an extension" error. The error message should look like the image below.

Requests to the server have been blocked by an extension error in Chrome or Microsoft Edge

This article will explain why "Requests to the server have been blocked by an extension" happens and go through a few ways you can do to fix it on Chrome/Microsoft Edge and Chromium based browsers.

What causes "Requests to the server have been blocked by an extension" error?

Requests to the server have been blocked by an extension followed by ERR_BLOCKED_BY_CLIENT error code usually happens when you have an extension that have access to browsing data turned on.

Simple, ordinary websites don't often trigger this kind of error, but visiting modern, complex web applications like Youtube or GMail which sends and receive hundreds of requests at a time can trigger "Requests to the server have been blocked by an extension".

Most of the time, the extension we're referring to is an adblocker. 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 prevent it from loading, sending a "blocked" signal to the browser.

Fix "Requests to the server have been blocked by an extension"

Since the error 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.

Disable Chrome extensions

Most of the time, disabling all extensions and plugins should fix "Requests to the server have been blocked by an extension", since one of them could cause the page block. If you have never done this before, don't worry, we got step by step instructions below :

Step 1: Open Chrome, click the three dots button near the top right corner of the window and select More tools.

More tools

Step 2: Choose Extensions from the submenu.

Step 3: In each section, there is a Remove button in case you want to uninstall it completely. However, disabling them will temporarily isolate which extension causes the error. To disable an extension, click the switch in the lower right corner of each section.

Disable an extension

Once you've disabled all the Chrome extension, the "Requests to the server have been blocked by an extension" error should be fixed.

Create a fresh Chrome profile

Chrome allows you to create a brand new profile as a way to enable multiple users to use the same Chrome installation. In this case, you can start a new profile to avoid manually disabling each extension, which can be time-consuming. Follow the step-by-step instructions below :

  1. Open up Google Chrome.
  2. Click the Profile button (the human button on the upper right corner of the window) and select Add.Add New Profile
  3. You will be asked to specify a name for the new profile as well as customize a color for easy identification. You can also choose a custom avatar here.Customize New profile
  4. Select Done and a new Chrome window will be opened immediately without any bookmarks, history, passwords, and cookies.

Of course, no extension is installed by default in the new profile, therefore the "Requests to the server have been blocked by an extension" error should be gone by now.

Click to rate this post!
[Total: 24 Average: 5]

Leave a Comment