I’m still struggling getting uploads moved to Spaces. When s3_cdn_url is defined, discourse points to the s3_cdn for assets and they aren’t there. I tried `rake s3:upload_assets and get root@shadrack-rbx:/var/www/discourse# rake s3:upload_assets …

Why do you need to push assets to S3? Can’t they be served from a push CDN like normal? Uploads assets means JS files not uploads.

[afbeelding] Falco: Why do you need to push assets to S3? Can’t they be served from a push CDN like normal? That’s what I thought, but what’s happening is that all the assets are linked to the S3 CDN url and they aren’t there. I’d assumed that they’d either be served by the CDN like normal (I…

[afbeelding] Falco: Uploads assets means JS files not uploads. Making sure you saw this @pfaffman because this topic makes very little sense the way it is phrased now. Do you mean “uploads” as in “uploaded files”?

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. [afbeelding] codinghorror: this topic makes very litt…

Looks like spaces don’t implement the AWS S3 API for the CORS rule. That is a must have since assets can contain fonts, and those really need CORS. Maybe work on a way to disable the rules insertion and took care of that manually? @rishabh did this already with the tombstone rule to allow our S3 c…

So if I want to move this site to S3 maybe I should just give in and stick this on AWS S3 and then stick CloudFlare or KeyCDN in front of it?

No. That means that if you want to use the GlobalSettings for S3 in the current state you will need to deal with the missing feature in the S3-like service in Digital Ocean, patching around it somehow. You already have a workaround (use a normal site setting), and we know that we need a setting to…

Sorry I’m dense. I’ve been working on this off and on for months. Ah, so as long as I don’t use GlobalSettings it’ll work just fine? (Because GlobalSettings also wants assets to be in S3?)

I’m not sure if you (or anyone else) is still having problems with this, or if the below would resolve it, but since I came across this when troubleshooting my own issue, I thought I’d share: If you are using Digital Ocean Spaces for S3 storage, and You have themes with uploaded fonts, e.g. WOFF, …

So the whole topic conclusion was a misunderstanding. I spent a full day testing Discourse compatibility with DO offerings, and the CORS thing here was a red herring. The problem is that DO Spaces don’t implement the tagging header in their S3 Clone. Fix for the upload_assets task is pretty simpl…

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

Ondersteuning Installatie

Falco (Falco) 22 april 2020 om 22:51 17

This is working now.

Just follow Using Object Storage for Uploads (S3 Clones)

Topic		Antwoorden	Weergaven
Defining DISCOURSE_S3_CDN_URL links to assets in S3 CDN URL Support	42	6469	22 april 2020
Digital Ocean Spaces (S3) "unable to sign request without credentials set" Support uploads , backups , s3	19	383	7 januari 2026
Migrate_to_s3 for Digital Ocean Spaces woes Self-hosting s3	25	3341	28 maart 2019
Issues with AWS CDN and S3 Self-hosting cdn , s3	22	474	30 december 2025
Configure an S3 compatible object storage provider for uploads Self-Hosting cdn , configuring , how-to , reference	263	47044	20 mei 2026

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

Gerelateerde topics