403 Error with digital ocean cdn

[Pierre]

Hi @pfaffman I found your post which also mentions the 403 error. It’s marked as closed.

Digital Ocean Spaces don’t implement the AWS S3 API for the CORS rule

No, I really mean assets (uploads seem fine). It seems that when GlobalSettings.s3_cdn_url is defined, discourse expects assets (i.e., the javascript stuff) to be in the S3 CDN, so the site is broken because none of the assets are available. It makes zero sense to me either. I just set SiteSettings.s3_cdn_url (not in GlobalSettings) and assets seem to still be coming from the server, not the CDN. So maybe it’s a bug with GlobalSettings.s3_cdn_url? Yup. Re-setting the value in…

Can you share how the error was resolved?