# 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:** 13

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [April 1, 2026, 10:03am UTC](https://meta.discourse.org/t/all-plugins-not-functioning-due-to-cors-error-after-recent-upgrade/399466/13 "2026-04-01T10:03:34Z")

</div>

Added this information to the main topic:

> [@Introducing a new build system for plugins](https://meta.discourse.org/t/introducing-a-new-build-system-for-plugins/398713/1):
>
> ### CORS / Access-Control-Allow-Origin Errors
> 
> If you experience CORS errors after the update, and you use a CDN, then you should run a full CLI rebuild (`./launcher rebuild app`) to pull in [this change](https://github.com/discourse/discourse/commit/2790b1731888c8f2396ee00b5ac3fde1ff8518ea) to the NGINX configuration.
> 
> If you use S3 (or S3 compatible) storage for assets, then you need to configure your CDN to add the `Access-Control-Allow-Origin: *` response header to all assets.

Sorry for the disruption here! We should’ve done some more extensive testing with different CDN configurations. Please let us know if you’re still experiencing any issues after a rebuild.

---

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