403 Error with digital ocean cdn

[Pierre]

I’m not sure if this is related so decided to create another post

Successfully connected Discourse with digital ocean spaces (I think)
https://meta.discourse.org/t/looking-for-doc-to-connect-discourse-with-digital-ocean-spaces/172917/8

and there’s an option within the ‘do spaces settings’ to enable cdn. After enabling and visiting Discourse I see many 403 errors pointing to the following urls

https://cdn.example.com/assets/*
https://cdn.exameplc.om/stylesheets/*
https://cdn.example.com/uploads/*

Did I miss something?

[pfaffman (Jay Pfaffman)]

There’s this

@Falco

DO offering is good and works out of the box. Only problem is that their CDN offering is awfully broken, so you need to use a different CDN for the files.

Which I think you’ve confirmed.

[michaeld (Michael - Communiteq)]

Their CDN is “broken” because it sends incorrect headers, not because it returns Forbidden responses.

@Pierre so it does work without CDN?
If so, how did you configure the 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?

[Pierre]

Hi @michaeld

To be honest I’m not even sure if things are working correctly. I’ve been struggling with different configurations and there have been many changes trying to get Discorse to work with Digital Ocean Spaces. I will need to do a clean install.

[pfaffman (Jay Pfaffman)]

Sorry. I may not have paid close enough attention to your specifics.

The problem that I believe I had in that topic, which cost me 17 hours of down time for a high priority client during my vacation, is solved by adding the s3:upload assets to the app.yml.,and, I think, using the env variables to configure the S3 stuff. Did you do that?