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

Product Support Self-hosting

AI-generated summary

The user sweetbeems changed their Discourse server’s IP address, causing issues with their CloudFront CDN domain. After commenting out DISCOURSE_CDN_URL in the YAML and rebuilding, the site still loaded the old CDN URL in the browser cache, even in incognito mode. pfaffman suggested that DNS propagation might be the issue and advised clearing the browser cache. sweetbeems clarified that the problem wasn’t related to post baking or asset URLs in posts, but eventually resolved the issue after DNS fully propagated.

1

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: https://forums.learnnatively.com/
bad CDN url: https://deyr2qldo994j.cloudfront.net/

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 https://do4ryrayvtpwi.cloudfront.net/. So I don’t think post baking should be an issue?

2

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.

3

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.