Removed CDN, but discourse still points to it in browser cache?

I unfortunately changed my discourse server’s ip address, which has caused issues with my cloudfront domain.

So, I commented out DISCOURSE_CDN_URL from the yaml file and rebuilt. However, when I go to the discourse app with a browser cache (i.e. not incognito), the html contains my cloudfront url and I get the wheel of death.

I originally thought it might be a post baking issue, but then incognito wouldn’t work either.

Is there a way to bust the browser cache?

discourse app:
bad CDN url:

Any help would be great, thanks!

Edit: Just to be clear all my images / uploads are in a different CDN which is not an issue. That cdn is So I don’t think post baking should be an issue?

If that’s the case then you just need to wait for dns to propagate. Or maybe dns is broken in some way that cloud front is using the old dns.

It’s always dns.

Google “clear browser cache browser name”

If you’re going to get rid of the CDN, you must rebuild so that the assets got precompiled, and to do need to rebake all posts.


Thanks for your responses!

That doesn’t seem to be the case with non-uploads cdn? It doesn’t seem that there’s any asset urls inside the baked post content as far as I can tell.

Unfortunately that’s not really a solution for users, was hoping for something like a get param cache buster. Although I must admit, i’m not fully clear why the cache was impacting it… there was just a difference between incognito & non-incognito behavior.

In any case, it seems to have resolved itself, as the DNS has full propagated.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.