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?

There’s this [图片]Configure an S3 compatible object storage provider for uploads 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.

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?

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 Self-hosting 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. frowning_face 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?

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.

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?

Digital Ocean CDN 出现 403 错误

产品支持

pfaffman (Jay Pfaffman) 2020 年12 月 11 日 03:02 2

确实如此

我想你已确认了这一点。

话题		回复	浏览量
Digital Ocean Spaces don’t implement the AWS S3 API for the CORS rule Self-hosting cdn , s3	16	3822	2020 年4 月 22 日
S3, Assets & CDN Error Self-hosting cdn , s3	3	811	2023 年8 月 5 日
Is DO Spaces CDN still broken? Any workarounds? Product Support	4	1840	2022 年8 月 13 日
Digital Ocean Spaces (S3) "unable to sign request without credentials set" Product Support uploads , backups , s3	19	940	2026 年1 月 7 日
Looking for doc to connect discourse with digital ocean spaces Product Support	6	2021	2020 年12 月 10 日

Digital Ocean CDN 出现 403 错误

相关话题