# Chrome adblock extension house ads issue

**URL:** https://meta.discourse.org/t/chrome-adblock-extension-house-ads-issue/284097
**Category:** Development
**Created:** [November 1, 2023, 10:49am UTC](https://meta.discourse.org/t/chrome-adblock-extension-house-ads-issue/284097 "2023-11-01T10:49:33Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [November 1, 2023, 10:49am UTC](https://meta.discourse.org/t/chrome-adblock-extension-house-ads-issue/284097/1 "2023-11-01T10:49:34Z")

</div>

I’m fairly sure this is related to the issue discussed here: [ServiceWorker thinks I'm offline when I'm not](https://meta.discourse.org/t/serviceworker-thinks-im-offline-when-im-not/77886).

Testing on the latest Chrome browser on Ubuntu with both the Adblock and Adblock Plus browser extensions, having either extension installed but disabled for a single Discourse site prevents the House Ads navigation item from being added to the nav bar:

 ![image](https://global.discourse-cdn.com/meta/original/4X/f/4/a/f4a5adcaff8928d0c65a079cbd019835236d2b97.png)

The error in the console is

`NetworkFirst.js:120 Uncaught (in promise) no-response: no-response :: [{"url":"https://global.discourse-cdn.com/business4/assets/plugins/discourse-adplugin-78e860fa781ab21eafa70bfb3c8514cc572a1ff6eb65774509c6c022e1fbf211.br.js"}] at u._handle (https://global.discourse-cdn.com/business4/assets/workbox-77b0e3e0dd4773bcd6c7e74f302f7c69/workbox-strategies.prod.js:54:13) at async u.Rt (https://global.discourse-cdn.com/business4/assets/workbox-77b0e3e0dd4773bcd6c7e74f302f7c69/workbox-strategies.prod.js:40:10)`

If I go to the web inspector’s Application tab and select the “Bypass for network” checkbox, the file loads without any issues.

This wouldn’t be a huge deal, but the issue also affects house ads that are served with a script. For example, house ads that are served from a revive adserver. In that case, the paused adblocker prevents the revive server’s `/asyncjs.php` file from being served. It produces the same error as I posted above.

This seems to be an issue with the extension and not with Discourse, but I wonder if there’s anything Discourse could do to deal with it.

It seems like the problem has been around for a while. Here’s an Adblock Plus bug report from 2018, posted by someone from the Financial TImes: [Adblock Plus Help Center](https://forum.adblockplus.org/viewtopic.php?p=176568)