Ludachris
Well-known member
Didn’t work.Admincp > tools > rebuild user cache
Didn’t work.Admincp > tools > rebuild user cache
Oh, you have SOME caching most likely going on... at the least probably php opcache (although it shouldn't cause this issue).... that's why I suggested restarting the server. Every now and then I've come across a quirk on my site that a simple restart of nginx, php processor and memcached resolved. I'd suggest trying it as it should not take your site(s) that long to come back up. Simply set up a time you are going to do it and post notices on the appropriate sites that they will be down for about a 10-15 minute period (shouldn't take near that long to restart).I haven’t rebooted the server yet but there are no caching systems in place for the website on the front end.
Yes, I agree to check in with them...This is surely because of Ezoic CDN caching.
Ask them to disable it.
I have a feeling this is it too - it makes sense that it's something 3rd party that's doing it since nothing changed on our end.This is surely because of Ezoic CDN caching.
Ask them to disable it.
It's due to the server being configured to use a reverse proxy (which is constantly changing) and the real IP address not being exposed consistently and/or CloudFlare being in use.
It's doing what it's supposed to - the config.php switch works around the issue caused by it.
Sure did. I had to do that a while back for the same reason mentioned in that thread. But that was a separate issue. I actually tried removing that from the config file to see if it helped.... it didn't.Hey @Ludachris try this?
XF 2.2 - Cannot log into admin after a few failed attempts
Hi folks, I switched from Chrome to FF and I mistakenly used the wrong password to log into admin. When I try log in now it just takes me back to the admin login screen. No message of anything. I've tried: Truncating the admin session cache table Promoting another test account I had to admin...xenforo.com
This is surely because of Ezoic CDN caching.
Ask them to disable it.
It was Ezoic. They disabled the caching and it fixed the issue immediately. What a pain in the ass that was. Thanks for all of the suggestions.Yes, I agree to check in with them...
We've had similar issues on one of our sites where they aggressively cached things that shouldn't be (logged in content).
They managed to turn it off for pages that were served with a specific logged-in cookie set...
Cache-Control: private, no-cache, max-age=0
private
directive they are given (do not store in a cache server, EVER), they are also told that even if you store the cache when I told you not to, you need to validate if the cache has changed with the server (which they also ignore apparently). And just so there's no confusion, you are allowed to store the cached content no longer than 0 seconds.Sounds like Ezoic sucks... they are running a cache server in all the wrong ways. No wonder I never heard of them.
We use essential cookies to make this site work, and optional cookies to enhance your experience.