All plugins not functioning due to CORS error after recent upgrade

@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 to add some CDN-specific configuration. I assumed this topic was about S3 assets, but now I’m not so sure?

For people using a simple CDN against the application server, there shouldn’t have been any extra configuration work required. It should ‘just work’, exactly the same as theme-javascripts and hightlightjs bundles. But it looks like we were indeed missing the header in our default NGINX configuration. Sorry about that!

This should get things working again:

https://github.com/discourse/discourse/pull/39031

Once this is merged, a ./launcher rebuild app will be required for it to take effect. NGINX config changes are not applied during UI updates.

3 Likes