Unexplainable login session issues

I’m ripping my hair out trying to fix weird login session issues I’m having on multiple Concrete CMS websites I run and I think I’ve had this problem for years without realising it.

Both are Concrete CMS v8.5.x and due to addons they rely upon that are no longer getting updated, they cannot upgrade to v9.x any time soon. So this is my problem and I’m trying to find a solution.

The issue is that after logging in, there are pages that work as if I am logged in, and then there are pages that act as if I am not logged in at all. The pages that act as if I am not logged in “fix” the session issue when the page is refreshed with F5, however, they are not fixed by browsing to another page and back to the same page.

This is also a problem because I don’t want to tell new users to the websites to “just press F5” to fix session issues, as to me that’s a junk answer that kicks the can down the road. Plus there will be people who just leave the site without even telling me they have problems.

I’ve gone through a lot of permutations of troubleshooting to establish a pattern and a possible root-cause, but so far I can’t find much of a reliable pattern, nor an indicator of a root-cause.

I’ve eliminated the reverse-proxy in-front of it by overriding my hosts file to connect to the Concrete CMS websites directly (on LAN).

Clearing cache on the sites (including thumbnails) do not seem to change the results.

I’ve taken a few attempts to switch to session handler “database” but I’m not entirely sure if I did that correctly, and it didn’t seem to change the results.

I’ve of course tried this in multiple different incognito browsers (Firefox, Chromium, etc) and the results do not seem to be tied to a specific browser.

So… I think I need a dev to help me here, or some other keen individual, as at this point I’m not sure what to try next or what to do about it. My google-fu has not turned up useful results.

Does anyone have any ideas as to what this could be? Thanks for anyone chiming in!

This could be your web server running a background cache system.
If you have cPanel take a look in the ‘Advanced’ section for web cache manager or something similar.

I have total root access to the host, this is 100% self-hosted. HTTPD on the relevant Concrete CMS systems are Apache2.

So I’m going to need you to be a bit more specific than that please.

Sorry I cannot be more specific other than you are looking for some kind of server cache rather than your concrete or browser caches.

The system hosting it is running Apache2 and PHP, following recommended configurations from Concrete CMS documentation. So I really do need specific recommendations on what to do here as I’ve already combed through the configurations for both and thus-far not found what is causing the problem. :confused:

So far it looks like switching Full Page caching from “On - in all cases” to “On - If blocks on the particular page allow it.” does the trick. Getting users to test again but in my rigorous testing this appears to reliably solve it.

Just my 2 cents and others may strongly disagree but I have never once run any concrete sites with full page caching on at all. It causes more support calls than any other issue because owners/editors must see the ‘fruits of their editing labors’ immediately or else frustration ensues.

Roger that! :slight_smile: 20char