403 Error with digital ocean cdn

support
1

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?

2

There’s this

Which I think you’ve confirmed.

3

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?

1 Like
4

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

Can you share how the error was resolved?

5

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.

1 Like
6

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?