All plugins not functioning due to CORS error after recent upgrade

[david (David Taylor)]

Added this information to the main topic:

@david

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 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.