# All plugins not functioning due to CORS error after recent upgrade

**URL:** https://meta.discourse.org/t/all-plugins-not-functioning-due-to-cors-error-after-recent-upgrade/399466
**Category:** Self-hosting
**Tags:** cdn
**Created:** [March 27, 2026, 8:35pm UTC](https://meta.discourse.org/t/all-plugins-not-functioning-due-to-cors-error-after-recent-upgrade/399466 "2026-03-27T20:35:59Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![amiantos](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/amiantos/32/543620_2.png) [@amiantos](https://meta.discourse.org/u/amiantos)
#### Post date: [April 2, 2026, 6:03pm UTC](https://meta.discourse.org/t/all-plugins-not-functioning-due-to-cors-error-after-recent-upgrade/399466/17 "2026-04-02T18:03:52Z")

</div>

I was having a hard time getting the CORS settings in Cloudflare R2 to work for this with a custom domain. I ended up brute forcing it by using a header transform rule to always insert the right header for my CDN domain. Just in case this helps someone else.

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

---

_[View the full topic](https://meta.discourse.org/t/all-plugins-not-functioning-due-to-cors-error-after-recent-upgrade/399466)._