Wordpress LScache Plugin: Memcached/Redis Connection Test: Failed Learn More
Last Updated on: Wed, 15 Apr 2026 00:00:02 Memcached Extension: Enabled Redis Extension: Enabled Connection Test: Failed Learn More Ive spoken to my host and this is the message I got at the end I am afraid Object Cache was disabled a few update cycles ago and as this is rarely requested we on the frontline support were not aware and it was only when this was escaled to 2nd line support that it was found out. The reason is because Object Cache such as Redis and memcached typically runs a shared pool of memory and there is a high risk of cache poisoning (which is deemed to be a security risk) by other users on the same server. Note that some providers may claim to offer this functionality on the market, even for reseller/shared users, but we have our doubts on whether that is truly implemented correctly. Real Object Cache that is dedicated to each user is extremely complicated to configure and involves many systems, so it is possible they are using a shared pool and advertising without the risks being known to the end user. Hi, yes , thats correct, so you need to separated the redis or memcached to each hosting Best regards, Sorry, I dont understand, how do you mean? Hi, I mean if your hosting provider doesnt give you redis or memcached , then object cache wont work Best regards, thanks
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference