Read Aloud extension blocked by Brave — ERR_BLOCKED_BY_CLIENT on extension's own pages

Brave Browser
, ,
1

Read Aloud extension (hdhinadidafjejdhmfkjgnolgimiaplp) blocked by Brave — ERR_BLOCKED_BY_CLIENT

Setup

  • Brave 1.91.171 (Chromium 149), Windows 11 25H2
  • Extension: Read Aloud: A Text to Speech Voice Reader

The problem
When activating the extension, it opens a new tab at chrome-extension://hdhinadidafjejdhmfkjgnolgimiaplp/player.html?autoclose which gets stuck loading forever. Navigating directly to chrome-extension://hdhinadidafjejdhmfkjgnolgimiaplp shows an explicit Brave block page: “hdhinadidafjejdhmfkjgnolgimiaplp is blocked — This page has been blocked by Brave — ERR_BLOCKED_BY_CLIENT”. The Network tab in DevTools shows the player.html request stuck as “Pending” with 0.0 kB.

Key findings

  • The extension works perfectly on Chrome with identical settings
  • The problem occurs on a completely fresh Brave profile with no other extensions installed
  • The console shows no errors — the page never loads enough to run JavaScript
  • Brave is explicitly blocking the extension’s own pages

Everything I’ve tried

  • Disabling/re-enabling and reinstalling the extension
  • Fresh Brave profile
  • Disabling all Shields, fingerprinting protection, and script blocking
  • Turning off Safe Browsing entirely
  • Forcing #brave-extensions-manifest-v2 flag to Enabled
  • Adding @@||chrome-extension://hdhinadidafjejdhmfkjgnolgimiaplp^ as a custom adblock filter
  • Checking brave://adblock — only Cookie Notice and Mobile App Promo filters are enabled, no custom filters
  • Shields not in aggressive mode
  • Checking brave://settings/content/javascript — JavaScript is allowed

Active variations that seem relevant

  • ExtensionsManifestV2StudyRelease:Enabled
  • BraveWebcompatExceptionsServiceReleaseStudy:Enabled

Is there a way to whitelist a specific extension ID from whatever internal blocklist is causing this? Has something changed in 1.91 that would cause Brave to block an extension’s own pages?

2

This might be related to the issue linked below. We have a solution in Nightly 1.93x currently and looking to uplift to the other releases.

If you try from our Nightly instance, do you still see the issue? https://brave.com/download-nightly/

3

Thanks for the reply. The extension team itself fixed the issue 2 days after my initial comment, but my account was new so it took a while for the post to be approved. Thanks anyway.

Not sure if there is something I should do, like close the topic, but for any admins reading, feel free to do so.