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

<div class="post-metadata">

### Author: ![tanya\_byrne](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tanya_byrne/32/444826_2.png) [@tanya\_byrne](https://meta.discourse.org/u/tanya_byrne)
#### Post date: [March 31, 2026, 11:22pm UTC](https://meta.discourse.org/t/all-plugins-not-functioning-due-to-cors-error-after-recent-upgrade/399466/8 "2026-03-31T23:22:14Z")

</div>

Just a heads up for folks, if you are using Azure Classic CDN this issue has started to occur. I am trying out a fix on the CDN side, but I may need to migrate to proper front door rather than classic CDN

---

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