hello all,
I (and other Users) have been encountering a strange issue starting today. see console:
resulting in some components (icons, graphs, etc.) not rendering:
any thoughts on what could be causing this and how to debug??
thanks!!
2 Likes
I see the graphs on your site. If you can still reproduce the issue, please try with a different browser or from a different network.
1 Like
thanks @pmusaraj, it works from Safari.
is there anything I could to get it working from Chrome??
thanks again.
One of my clients hosted by Discourse has the issue as well.
3 Likes
I’m experiencing this on my hosted instance as well. I’ve cleared cache, tried firefox and chrome – same errors in console that others have reported. Seems sjc2.discourse-cdn.com is the culprit – it blocks (or does not respond) to some requests. No issue with any other CDN server. After a hard refresh or two the requests go through.
Apologies, we are investigating this issue and will get it fixed shortly.
There is a bad resource cached on the CDN and we need to get a cache breaker out there. Hold tight.
4 Likes
We deployed a fix for the issue:
https://github.com/discourse/discourse/commit/af4938baf15b4551ba8fc9727e6b9f482afd50c7
This is part of a big change @vinothkannans is working on. Historically Android erroneously reported incorrect cache usage size. The fix uses no opaque requests which end up being reported correctly.
However we need to expire our entire CDN cache when this change applies to avoid a situation where bad CORS settings (that exist now in the CDN) are served or cached on clients.
We reverted the change for now, but will make it again in the coming week with an extra cache breaker to avoid this issue.
10 Likes
thanks @sam & @vinothkannans for quickly addressing the issue, much appreciated.
4 Likes
Indeed, thank you Discourse team!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.