# uMatrix browser add-on causes white pages when visiting Discourse instances

**URL:** <https://meta.discourse.org/t/umatrix-browser-add-on-causes-white-pages-when-visiting-discourse-instances/155239>\
**Category:** Product Support\
**Created:** [18 ביוני,‏ 2020,‏ 3:59pm UTC](https://meta.discourse.org/t/umatrix-browser-add-on-causes-white-pages-when-visiting-discourse-instances/155239 "2020-06-18T15:59:50Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [1 באפריל,‏ 2021,‏ 8:36pm UTC](https://meta.discourse.org/t/umatrix-browser-add-on-causes-white-pages-when-visiting-discourse-instances/155239/9 "2021-04-01T20:36:57Z")

</div>

Ah, this would be because of the serviceworker caching. All the resource requests get proxied by a script, so you need to allow the script to make requests (the XHR box).

> [@mmcm](#):
>
> FWIW, serving _all_ content from the same domain consistently works with uMatrix’s default 1st-party rules. I’m not a devops kinda person so I don’t know if that makes any sense, but from what I’ve seen it works quite nicely for small-to-medium size communities.

And that’s the default for open-source Discourse installs, but we have large customers on our hosting so it’s easier to just give the CDN to everyone 🙂

---

_[View the full topic](https://meta.discourse.org/t/umatrix-browser-add-on-causes-white-pages-when-visiting-discourse-instances/155239)._
