Since last week, all plugins both core and installed have stopped functioning even when enabled on our forum. Initially I thought this was something to do with the previously mentioned bug FIX: Compile missing rollup plugin bundles on demand in development - #8 but we have run multiple updates since…

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: [image] Code highlighting failed because bunny.net CDN Support Someone compained that code highlightin…

Thanks Jay, we have Bunny and the fix you mentioned has sorted all the issues out now! Thank you and everyone for the help and support on this one, our forum is back to normal. Well as normal as it can be :smiley:

Glad to hear you got it sorted! [image] pfaffman: I don’t understand why this problem started when I upgraded In the new plugin system, we use script type="module", which requires the correct CORS headers to be set. Old-style script type="text/javascript" do not require those headers. We’ve…

[image] david: We’ve been slowly migrating different systems Aha. That’s what I would not have guessed.

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

[image] david: In the new plugin system, we use script type="module", which requires the correct CORS headers to be set. Old-style script type="text/javascript" do not require those headers. Yep, confirmed this issue on Azure Classic CDN too. You need to add a new rule to the rules engine, e…

weirdly this issue hasn’t impacted themes, only plugins for us.

@pfaffman @TomoftheFog @tanya_byrne @denvergeeks please could you confirm how your assets are configured? Do you just have a CDN + the application server? Or do you also store assets on S3/S3-compatible storage? If you are using S3/S3-compatible storage, then unfortunately the only reliable way is …

Added this information to the main topic: [image] Introducing a new build system for plugins 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 to the …

All plugins not functioning due to CORS error after recent upgrade

Support Self-hosting

denvergeeks April 1, 2026, 1:28am 11

Is there somewhere to find instructions or guidance regarding these recent changes regarding CORS for those of us using Cloudflare?

Topic		Replies	Views
Code highlighting failed because bunny.net CDN Support cdn , cors	4	1305	March 8, 2024
Issue with Relative Path Causing CORS Error on Discourse Sites Bug	7	457	May 18, 2025
Latest update requires cache purge in CloudFlare Self-hosting	71	6129	May 5, 2019
Aborting! CDN must have a protocol specified Support	7	949	May 27, 2019
Sporadic infinite load after update Support	11	608	September 30, 2023

All plugins not functioning due to CORS error after recent upgrade

Related topics