Defining DISCOURSE_S3_CDN_URL links to assets in S3 CDN URL

[eatcodetravel (Orlando Del Aguila)]

I guess this is because you are missing DISCOURSE_CDN_URL. We have it like this in our config

DISCOURSE_CDN_URL: 'https://d16zv78c963s69.cloudfront.net' # this points to the server
DISCOURSE_S3_CDN_URL: 'https://community-cdn-prod.debtcollective.org' # this points to S3 bucket

Stylesheets are fetched from the server so they use DISCOURSE_CDN_URL. JavaScript it’s uploaded to the S3 bucket and uses DISCOURSE_S3_CDN_URL. @Falco explained this to me here.

Assets not serving from CDN in latest update

If you inspect this page you will see that we we have two different Cloudfront URLs, so we use what I said above, two distributions, one for the normal CDN and another for S3. The problem from the title of the OP is this: CSS come from the app and JS from S3. You need a CDN that is aware of where every single asset is coming from and can reach the necessary place or two CDNs. That is why we have two different settings after all.