@beachholiday are you able to provide us a Report ID?
Ther report is sent to Litespeed and it generates an ID that is shareable.
Go to LSC => Toolbox => Report. Click on “Send to Litespeed” and share the ID generated
Dear @litetim
We have rolled back to version 7.7.
We can send a report ID for this version. Does this help and work? We can’t send a report ID with 7.8.0.1 installed.
many thanks for clarifying.
Piet
@beachholiday Please send report, even with 7.7
Settings are the same.
Thank you 🙂
Dear @litetim
Many thanks for your reply.
We have now generated a new report and sent it to you:
- Last Report Number: TKWOZQJA
- Last Report Date: 04/01/2026 04:55:22
Let me know, if there is anything else you need when you had a chance to review this report.
Kind regards,
Piet
@beachholiday
Let’s try this:
– disable Object cache from LSC: https://docs.litespeedtech.com/lscache/lscwp/cache/#object-tab
– update to latest version
– test if login works
Dear @litetim
Many thanks for your suggestion. We have tried this out and I can confirm that your fix works:
- Object Cache: we disable object cache within LSC
- version 7.8.1: we updated the plugin to this version
- Admin: we find that we can now login to /wp-admin/ without issues.
What is the permanent solution because we would like to re-enable Object Caching for our website?
Many thanks for your help with this.
Piet
@beachholiday can you confirm the site is working now?
If everything is ok, please enable Object Cache and see what happens.
-
This reply was modified 2 weeks, 2 days ago by
litetim.
Dear @litetim
We have re-enabled Object Cache and all is working.
We believe the error might have been caused but the Litespeed Redis Cache Service being disabled at the server level, either inadvertently or for another reason, e.g. crash.
Could this be the cause?
Many thanks for your help with this.
Piet
@beachholiday we discovered a but in 7.8.1 that when OC is enabled from CLI it throws a error and enabled OC from web with wrong configuration.
But the error is only limited to that action. After a refresh it works.
Might be related to wrong configuration somehow.
Glad it was resolved 🙂
Dear @litetim
Many thanks for the update.
What we do notice repeatedly is that after every plugin update (when Object Cache is enabled within the Litespeed Cache plugin) that we need to ‘flush’ the cache via the LiteSpeed Redis Cache Manager on the server. A simple refresh of the /wp-admin/ page in the browser does not suffice.
The front-end of the website continues to work flawlessly and it is only the /wp-admin/ backend that goes blank.
Kind regards,
Piet
@beachholiday happy that you resolved it! 🙂
