LiteSpeed Cache - Community 1.0.4.3

[Optic]

Has anyone ever experienced an issue every now and then where it appears you are getting a public cache page (evident as it shows you're logged out even though you ticked "Remember Me" on previous login) but then if you immediately refresh you are logged in OK?

I unfortunately can't seem to reproduce this consistently.

 

[lsKevin]

Hi @Optic

Do you have any other web applications with a LiteSpeed Cache plugin? This sometimes happens when someone is logged into one web application and not another, and it caches the not-logged-in web application. Try changing the Login Cookie setting (this will likely result in people needing to log back in). More on this here.

Let us know how it goes!

Cheers,
Kevin

 

[Alpha1]

Yes, we plan on developing an enterprise version capable of supporting logged in users later this year.

Is this still planned or has it been scrapped last year?

 

[lsKevin]

Hi @Alfa1

It's currently in the works. We're looking into the nuances of XenForo to determine the optimal set up. Obviously, things may change, but we're still looking into it.

Cheers,
Kevin

 

[Mike Fara]

Hey @IsKevin. I'm wondering if you are aware that enabling QUIC seems to mess up the plugin under LSWS 5.2?

 

[lsKevin]

Hi @Mike Fara

Thanks for the heads up. No, we are not aware of any issues - could you describe what you are experiencing?

Cheers,
Kevin

 

[lsKevin]

Hi @Mike Fara

Please try the latest build. We had an issue with cookies within quic that may be related to the issue you experienced.

Cheers,
Kevin

 

[Mike Fara]

Hi @IsKevin,

To elaborate, the login/logout logic seems to be problematic with the cache with QUIC enabled. Of course going back to HTTP2 seems to resolve the issue (or disabling the cache plugin). Basically, you are sometimes able to login, but be unable to to see yourself as logged in, and when logged out, vice versa. Occasionally, clicking login will actually do nothing. With build 4 of LSWS 5.2 this still seems to be an issue for XenForo, so I am thinking it is either the implementation of QUIC or how sessions are handled with the cache under QUIC. Even if you hard refresh a page ctrl-shift-r in Chrome, the issue will persist.

 

[lsKevin]

Hi @Mike Fara

Did you use the debug flag when upgrading the server? I will need to verify what build number we are on, but the issue was that when multiple cookies are set - some are not actually sent out in the quic request. If you open your browser's inspector and try to log in, is there a difference in the cookies set when using HTTP/2 vs QUIC?

 

[Mike Fara]

Hi @Mike Fara

Did you use the debug flag when upgrading the server? I will need to verify what build number we are on, but the issue was that when multiple cookies are set - some are not actually sent out in the quic request. If you open your browser's inspector and try to log in, is there a difference in the cookies set when using HTTP/2 vs QUIC?

Debug flag was not initially used. Oddly, I'm not seeing missing cookies, but the cache issue does appear to happen a few hours after the page cache is turned on. I also ran lsup.sh -d -f -v 5.2 and it went to Build 4, but this might be a newer Build 4 than the one being served (Not really sure about that one). In any case, I noticed that a crontab entry to clear the cache automatically needed to be customized for the /home/your_account/lscache directory instead of just /tmp/diskcache

This may also have something to do with the problem. I'll keep the cache on for a few hours and let you know if the problem reappears. Interesting what is happening here. I think its possible the homepage (forum index) keeps getting served stale but I'm not 100% sure.

 

[lsKevin]

We will be sending out a new build sometime today hopefully.

One thing you can test with the home page stale is if you just create a test post, it should update/purge from the cache to be updated, so on refresh from a logged out browser, the test post should be displayed even on the front page.

 

[Alpha1]

Another thing to check is to compare the php.inis. If phpinfo doesn't mention anything about redis, it might not be loaded in PHP, which would explain why it's not working with LiteSpeed only.

redis support is enabled in phpinfo.
After 5 months with thousands of daily errors we are looking into removing litespeed enterprise and moving to NGINX.
Please take note that XenForo 2 will have redis support built in.

 

[lsKevin]

Hi @Alfa1

Apologies for all the troubles that you are encountering.

Are you still using DirectAdmin? If so, could you please try the following wiki? https://www.litespeedtech.com/suppo...eed_wiki:directadmin:custombuild-installation

It seems that there is an issue with using lsphp built in the web admin with DirectAdmin. The steps above should switch the php interface to use LSPHP and the server to LSWS. After that, everything you do for Apache is the exact same for LSWS (however you install Redis for Apache, do the same for LSWS via DirectAdmin).

Please let us know how this goes! If this doesn't work, send us a ticket (bug at litespeedtech) and we'll gladly follow up.

Thanks,
Kevin

 

[Alpha1]

The steps above should switch the php interface to use LSPHP and the server to LSWS.

While we are not using custombuild, all php processes do use LSPHP. Do you think it is still necessary to recompile using custombuild?

 

[lsKevin]

CustomBuild handles most of the integration between LSWS and DirectAdmin, so using it should minimize unknown complications at least. We want to ensure that your system is working correctly, and this should help that.

 

[lsKevin]

Hi @Alfa1

Did you have a chance to try CustomBuild? Just checking in to see how it went.

Cheers,
Kevin

 

[Alpha1]

We are currently trying to figure out how we can do a rollback if it goes wrong. The host is unsure about this.

 

[lsKevin]

Let us know if we can be of any help!

CustomBuild is a DirectAdmin built in tool, so everything should transition smoothly, but we understand that it is a major change. For what it's worth, building PHP through web admin is not officially compatible for DirectAdmin servers, so that may explain why the issues occurred.

 

[Alpha1]

We are implementing Custombuild tomorrow morning when its a little less active. Shoutout to @Xon so he's aware.

 

[alpdarslan]

hi,
my litespeed cache is working?