XF 2.3 CSS file goes missing a few times per day, so strange...

drastic

Well-known member
I THINK my CSS file is doing a disappearing act on me a few times per day.

The forum will randomly stop displaying the style correctly. Sometimes works, sometimes doesn't. We can't figure out what would cause this.

We're on CloudFlare Pro, latest XF, PHP 8.3.12, and don't have the CF add-on installed atm. This happened when we had the CF add-on, so turned it off to see what happens. Same thing, random vanishing act by the CSS.

And.... rocketloader is already disabled.

wtfffffff.webp
 
when it happens, pop open the f12 toolbar and look at the network tab. it should show some sort of error for the css files.

see what code it's throwing.


Also, it's likely a cache issue. are you running something like redis?
 
when it happens, pop open the f12 toolbar and look at the network tab. it should show some sort of error for the css files.

see what code it's throwing.


Also, it's likely a cache issue. are you running something like redis?

Redis is more query cache, his issue is likely local cache.
 
I'm having the exact same issue as reported by some of my users. Only a few specific Cloudflare POPs appear to be affected. I was able to confirm it by using a VPN to affected users' area.

Specifically, only CSS delivered via XenForo's css.php files are broken (other custom CSS files served by my site, including those on my XenForo pages, are not affected).

Closer inspection shows files which should look like this:

CSS:
@charset "UTF-8";

/********* public:normalize.css ********/
/*! normalize.css v7.0.0 | MIT License | github.com/necolas/normalize.css */
button,hr,input{overflow:visible}...

Are prematurely truncated to only the first line:

CSS:
@charset "UTF-8";

Clearing the cache for these files does nothing, nor does disabling caching on these files, as confirmed by the presence of cf-cache-status: DYNAMIC in the response headers.

I've filed an issue with Cloudflare, but a response is unlikely. Hopefully it will resolve itself.

EDIT: The issue did resolve itself... for now.
 
Last edited:
Back
Top Bottom