I checked with my hosting provider and they confirmed that Redis is enabled on the server and the port is correct. How can this be enabled?

Thanks – Danny

I’m currently using Redis + WP Rocket, but I’m facing an issue where I have to clear the entire Redis cache each time I add a new post for it to appear.

I’d really like to only clear the cache for a specific URL where my grid listing is displayed. I noticed that W3 Total Cache has Redis support and can clear just one post, identifying the calls related to that post to clear only what’s necessary.

Would anyone know if there’s a way to achieve this with WP Rocket, or if switching to W3 Total Cache might help here?

Even if it is not clearing the cache, but signaling redis to update the cache of that URL on the next load would also solve the problem.

Is there any way to do this? It’s heartbreaking to see a nice 2GB cache being wiped.

“Redis is unreachable:?Connection refused [tcp://127.0.0.1:6379]”

How caN I remedy this, please?

I would like to propose an enhancement for the plugin that would significantly improve its usability for website owners using Redis. Currently, the plugin connects to Redis using the default port, 6379. However, there may be instances where Redis is running on a different port, depending on the hosting environment.

Without an option to specify a custom port in the plugin settings, users are forced to edit the plugin’s code directly. This creates challenges when it comes to future updates of the plugin, as any changes made will be overwritten.

Introducing an option to set a custom Redis port in the settings would be a valuable addition. It would provide flexibility for users and streamline the configuration process, ensuring that website owners can easily connect to their Redis server without modifying the core files.

I believe this change would enhance the overall experience for those utilizing Redis and make the plugin more versatile. Thank you for considering this suggestion!

Best regards,
Christopher

I’ve encountered a situation regarding the Redis Object Cache feature in the LiteSpeed Cache plugin and would appreciate some clarification.

In the Object Cache settings, with Redis enabled, the “Test Connection” status shows as “Passed,” indicating that the connection to Redis is working. However, I’ve noticed that even if Redis is running on the server but not configured for Object Cache, the plugin still reports that Object Cache is active simply because the connection to Redis is successful.

This raises a concern: Is the “Test Connection” status actually confirming that Object Cache is being utilized properly by the plugin, or is it only testing the availability of Redis on the server? If the latter is true, it could lead to a misunderstanding, as many users might assume that Object Cache is working, when in reality, Redis might not be configured for caching purposes at all.

Could you confirm if the “Test Connection” reflects actual usage of Redis for Object Cache, or just the connection status? If it’s the latter, I believe this could be a significant oversight, as many websites might not be taking full advantage of Object Cache while assuming they are.

I’m raising this issue because my hosting support has informed me that the server doesn’t support the LSCache extension. However, in the plugin settings on my site, Redis is marked as “Enabled” and the connection test shows “Passed.” It seems the plugin is incorrectly indicating that Object Cache is active on my site.

Thank you for your clarification on this matter!

Best regards,
Chris

Thanks.