I had this problem before and decided that I was crazy, confused, or the database on the site was suspect, but this is on a brand new site. Also, I was on Digital Ocean spaces, so I thought it might be a problem somehow. I’m trying again to figure out how to keep images on AWS S3 like I think the B…

Perhaps. It’s not a feature likely to be used by normal self hosters,so it’s going to be a low priority. Also, I think that there is soon to be a change in how global settings and shadowed by global work, so it’ll likely get worked out then.

seems the same issue turn me down here @pfaffman need your help do you use cloudfront to achieve the custom domain cdn url or just use the public prefix of bucket objects in cdn url

I’ve just hit this. @pfaffman did you ever get this resolved? I’ve got uploads working by setting the s3_cdn_url manually in site settings, but ideally need to be able to set the ENV variable globally when deploying. When I do, I get the same issue, that Discourse tries to look for assets at the s3…

I think that I just set the value in the database. My guess is that the solution is to find the rake task that will push the assets to S3.

I was wondering if any of the @team could confirm whether this is expected behaviour, that you can’t use an S3 CDN (set globally) for uploads without Discourse also looking for assets there too. It seems like unexpected behaviour unless I’m misunderstanding something.

Here’s some information about this, I was dealing with this last month. [image] Assets not serving from CDN in latest update Support Hello! I couldn’t figure out why in the latest update our installation stopped serving assets from the CDN. We are using …

Amazing. Thanks very much. There doesn’t appear to be much documentation around this at all, and the settings imply that you can just use s3 for uploads only, which I think is what’s catching us all out.

It is in my list to write a howto on this. I hope to do it by the week end.

Yeah, once you understand you need two CloudFront distributions, makes a bit more sense. Also, remeber to upload assets to s3 after each rebuild. There’s an issue with upgrades from Docker Manager where you need to run bundle exec rake s3:upload_assets manually inside the docker container. If you do…

Defining DISCOURSE_S3_CDN_URL links to assets in S3 CDN URL

Product Support

Falco (Falco) March 4, 2020, 3:58pm 15

Yes, that is the behavior.

Setting up S3 CDN will use it for every thing that would be a static file, be it uploads or JS assets.

Topic		Replies	Views
Unable to setup S3 bucket Self-hosting uploads , s3	11	683	January 12, 2025
Rake uploads:migrate_to_s3 fails because DISCOURSE_S3_CDN_URL env var is empty Self-hosting	1	779	September 27, 2019
Issues with AWS CDN and S3 Self-hosting cdn , s3	22	1249	December 30, 2025
Assets not serving from CDN in latest update Product Support	16	2053	February 7, 2020
Configure an S3 compatible object storage provider for uploads Self-Hosting cdn , configuring , how-to , reference	267	53731	September 15, 2026

Defining DISCOURSE_S3_CDN_URL links to assets in S3 CDN URL

Related topics