# 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:** 4
### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman) #### Post date: [March 29, 2026, 6:31pm UTC](https://meta.discourse.org/t/all-plugins-not-functioning-due-to-cors-error-after-recent-upgrade/399466/4 "2026-03-29T18:31:48Z")
I’ve got the same problem with a bunnycdn. It was working fine until a recent update. I tried adding `.js` to the CORS headers at `bunny.net` as described here: > [@Code highlighting failed because bunny.net CDN](https://meta.discourse.org/t/code-highlighting-failed-because-bunny-net-cdn/296333): > > Someone compained that code highlighting isn’t working on their site. I’ve replicated the issue on mine. The issue seems to be that the CDN is blocked by CORS policy: [image] I fixed the problem by adding js to the “add cors header” setting on the cors page: [image] If enabled, [bunny.net](http://bunny.net) will automatically add CORS headers (Cross-Origin Resource Sharing) to all requests to files with extensions from the list. This post is to document it in case someone else has an issue with a [bunny.net](http://bunny.net) CD… As was the case then, I don’t understand why this problem started when I upgraded to 6800ad3adf3ef9c3caeb9a4d849997c7a3dc98d7 last week. --- _[View the full topic](https://meta.discourse.org/t/all-plugins-not-functioning-due-to-cors-error-after-recent-upgrade/399466)._