After turning on Redis, the cart page does not refresh.
]]>Hi, I have a strange problem in our woocommerce setup.
If i disable redis in wodpress (I first flush redis and then disable it). Main attributes and their values are completely gone from the backoffice and front office of several products. Mainly products we created new attributes for in the last 2 months. These are new main attributes assigned to around 150 products.
I dont understand what is causing this, is redis not simply caching the database reads or has this somehow been stored only in redis?
If I enable Redis in WordPress, the attributes appear again.
Hi there, I use Redis Object Cache with my Buddypress member site, which is all dynamic content.
I’m not an expert within caching, but I managed to install and connect to the server, and all lights are green.
But I’m in doubt if BuddyPress can benefit from Redis?. The reason why I’m not sure that the dynamic content is cached, is that the members directory calls the server, every time you visit a member profile, and return to the directory.
The directory is reloaded, and the directory displays all members from the top of the directory again which of course causes a massive server load, so it seems like the content is not cached.
Does Redis actually work with BuddyPress?
As said, I’m a totally novice into caching and server prompts, so probably I should not use Redis at all ;-), but I managed to install Redis succesfully through SSH terminal and all seems to be running. One question comes up, does Redis need any server side maintenance or update once installed and running?
Thanks
Best
Carsten
I’ve discovered what I think is a bug with Redis-cache and S2member when the option “No (send each user a password-setup link after registration; recommended for best security)” is selected for the creation of users using the s2member join form. When this option is set a customised password reset email is sent allowing new users to set their own password. When redis cache is enabled the password set link in the email always generates an InvalidKey error. Disabling the redis-cache plugin and the error goes away.
I’ll post this in the s2member forum as well.
]]>Hello, I am using redis object cache and wp rocket on my wp website. I don’t use woocommerce. I have normal blog website. In day time site runs fine. If I publish 5-7 posts then server load goes high. while checking I can see that mysql sql is using 300-500%
In evening time, without publishing a single post server load goes 500-800%. While checking mysql is using 500%+ cpu. If redis cache is working then why mysql is using high cpu? I am using below lines in wp-config:
define( ‘WP_REDIS_HOST’, ‘127.0.0.1’ );
define( ‘WP_REDIS_PORT’, 6379 );
define( ‘WP_REDIS_PASSWORD’, ‘7a98765287’ );
define( ‘WP_REDIS_TIMEOUT’, 1 );
define( ‘WP_REDIS_READ_TIMEOUT’, 1 );
//change the database for each site to avoid cache collisions
define( ‘WP_REDIS_DATABASE’, 0 );
// supported clients: phpredis, credis, predis and hhvm
define( ‘WP_REDIS_CLIENT’, ‘predis’ );
what wrong I have done? I am not getting. Can you please help? Or should I use memcached? In phpmyadmin advisor it is written to use memcached for query caching. I am confused. Please help.
]]>whats the normal cache ratio for a woocommerce site?
my cache hit ratio is 95% + but my cache ratio is 5-9% even after a day of running before it gets flushed
I was reading on another topic that to use the plugin on a server with multiple websites that the database needs to be set via the WP Config file for each website.
You mentioned to choose a number between 0-16 when using define( 'WP_REDIS_DATABASE', 0);
Is 0-16 the maximum numbers that can be used? I have 2 servers with over 50 websites on each so if I can only go up to 16 how else can I use the plugin on my servers to avoid domains redirecting.
Thanks, William
]]>Hi
When I log in as an admin, the CSS on our Elementor pages breaks, and we get 404 errors on several Elementor CSS files. After flushing Redis everything looks fine again.
How can I solve this problem?
Kind regards
i searched and i know a page cache is recommended but for example wp fastest cache say don’t use Redis plugin, so which page cache and which plugin is recommended to minimize and defer js and css most my pages are WooCommerce product pages with very few statis pages
]]>IS there a way to get the admin menu to reset cache for the pro plugin?
]]>I have Redis installed and running, and it’s reachable at /home/[username]/.redis/redis.sock
The web host uses port 0 for Redis.
I set the port with define( ‘WP_REDIS_PORT’, 0 );
And I tried multiple things for the Redis host:
define( ‘WP_REDIS_HOST’, ‘localhost’ );
define( ‘WP_REDIS_HOST’, ‘[IP.ADD.RE.SS]’ ); (the server’s shared IP)
But I still get the message “Redis is unreachable:?Connection refused” in the plugin. What do I need to do?
]]>Hi everyone, we are using redis cache on our website and we have noticed a substantial improvement in database requests when the listing grid is loaded. However, when a new post is added, the redis cache needs to be cleared completely. Does anyone know how to clear only the redis cache of the CPT or of a URL? Even if it is via the command line, is there a way to do this without having to clear the entire cache?
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.
I have the following problem. I have registered a database on REDIS.IO and have the necessary information to connect the plugin to the database in REDIS.IO:
- Host
define( ‘WP_REDIS_HOST’, ‘redishost.redis-cloud.com’ ); - Port
define( ‘WP_REDIS_PORT’, 19xxx ); - Password
define( ‘WP_REDIS_PASSWORD’, ‘2IW5xxxxxxxxxxxxxxxxxxxxxxxxx’ );
(the showed login information is only as example) - I configure this information as follows and add it to the
wp-config.phpfile in WordPress. I restart the “Redis Object Cache” plugin by deactivating and reactivating it. Then, I go to Settings > Redis, but it still displays the message “Redis is unreachable: Connection timed out [tcp://127.0.0.1:6379]” even though I have set the necessary configurations inwp-config.php.
Could you please let me know what I might be doing wrong and how I can change the settings to connect the “Redis Object Cache” plugin to redis.io?
Thank you in advance for your attention and assistance.
Best regards,
Amex
I’m configuring ElastiCache for Redis to work with my RDS instance and have enabled both encryption-at-rest and encryption-in-transit.
However, when I set transit encryption mode to “Required”, my WordPress plugin Redis Object Cache fails to connect to the ElastiCache cluster. I want to enforce encrypted TCP connections but still maintain plugin functionality.
Could you help identify whether this issue lies with the ElastiCache configuration or the plugin’s compatibility with the required encryption? Any guidance on how to resolve this would be appreciated.
]]>I'm not sure if this is caused by Redis or something else on my server, but since upgrading to version 2.5.3 I've had the Redis server die twice due to memory spikes, last time was definitely when traffic is normally slow on my website. Can you clarify if the latest release change notes address any of this or if I need a dev to investigate further? At this point I'm going to just stop using the plugin if it bricks my site when the Redis server dies.
Here is the info I have from the logs:
var/log/messages-20241020:Oct 18 20:10:42 mail kernel: OOM killed process 4873 (php-fpm) total-vm:524832kB, anon-rss:221484kB, file-rss:9832kB
/var/log/messages-20241020:Oct 18 20:10:43 mail kernel: OOM killed process 4884 (php-fpm) total-vm:475296kB, anon-rss:171212kB, file-rss:9832kB
/var/log/messages-20241020:Oct 18 20:10:43 mail kernel: OOM killed process 4885 (php-fpm) total-vm:485536kB, anon-rss:180048kB, file-rss:9832kB
/var/log/messages-20241020:Oct 18 20:10:43 mail kernel: OOM killed process 4904 (php-fpm) total-vm:487884kB, anon-rss:182848kB, file-rss:9768kB
/var/log/messages-20241020:Oct 18 20:10:44 mail kernel: OOM killed process 4874 (php-fpm) total-vm:454068kB, anon-rss:149556kB, file-rss:9844kB
/var/log/messages-20241020:Oct 18 20:10:44 mail kernel: OOM killed process 4876 (php-fpm) total-vm:453152kB, anon-rss:148816kB, file-rss:9832kB
/var/log/messages-20241020:Oct 18 20:10:44 mail kernel: OOM killed process 4881 (php-fpm) total-vm:453152kB, anon-rss:148024kB, file-rss:9832kB
/var/log/messages-20241020:Oct 18 20:10:44 mail kernel: OOM killed process 4878 (php-fpm) total-vm:453152kB, anon-rss:147548kB, file-rss:9832kB
/var/log/messages-20241020:Oct 18 20:10:45 mail kernel: OOM killed process 4875 (php-fpm) total-vm:450784kB, anon-rss:146672kB, file-rss:9832kB
/var/log/messages-20241020:Oct 18 20:10:45 mail kernel: OOM killed process 4892 (php-fpm) total-vm:452920kB, anon-rss:148844kB, file-rss:9832kB
/var/log/messages-20241020:Oct 18 20:10:45 mail kernel: OOM killed process 4911 (php-fpm) total-vm:452160kB, anon-rss:148160kB, file-rss:9576kB
/var/log/messages-20241020:Oct 18 20:10:46 mail kernel: OOM killed process 4912 (php-fpm) total-vm:456452kB, anon-rss:150752kB, file-rss:9576kB
/var/log/messages-20241020:Oct 18 20:10:46 mail kernel: OOM killed process 4890 (php-fpm) total-vm:458912kB, anon-rss:154856kB, file-rss:9832kB
/var/log/messages-20241020:Oct 18 20:10:47 mail kernel: OOM killed process 4894 (php-fpm) total-vm:463152kB, anon-rss:157352kB, file-rss:9832kB
/var/log/messages-20241020:Oct 18 20:10:47 mail kernel: OOM killed process 4896 (php-fpm) total-vm:457012kB, anon-rss:152128kB, file-rss:9832kB
/var/log/messages-20241020:Oct 18 20:10:47 mail kernel: OOM killed process 13304 (spamd child) total-vm:260024kB, anon-rss:121328kB, file-rss:3424kB
/var/log/messages-20241020:Oct 18 20:10:48 mail systemd: spamd.service: main process exited, code=killed, status=9/KILL
/var/log/messages-20241020:Oct 18 20:10:48 mail systemd: Unit spamd.service entered failed state.
/var/log/messages-20241020:Oct 18 20:10:48 mail systemd: spamd.service failed.
/var/log/messages-20241020:Oct 18 20:10:48 mail systemd: redis.service: main process exited, code=killed, status=9/KILL
/var/log/messages-20241020:Oct 18 20:10:48 mail systemd: Unit redis.service entered failed state.
/var/log/messages-20241020:Oct 18 20:10:48 mail systemd: redis.service failed.
This is from the journalctl logs. It shows that it was killed, but not how or why:
Oct 15 09:16:57 mail.HIDDENURL.com systemd[1]: Starting Redis persistent key-value database...
Oct 15 09:16:57 mail.HIDDENURL.com systemd[1]: Started Redis persistent key-value database.
Oct 18 20:10:48 mail.HIDDENURL.com systemd[1]: redis.service: main process exited, code=killed, status=9/KIL
Oct 18 20:10:48 mail.HIDDENURL.com systemd[1]: Unit redis.service entered failed state.
Oct 18 20:10:48 mail.HIDDENURL.com systemd[1]: redis.service failed.
The last redis log also shows that it was running until the 18th then stopped:
4582:C 18 Oct 20:02:43.354 * DB saved on disk
4582:C 18 Oct 20:02:43.357 * RDB: 2 MB of memory used by copy-on-write
483:M 18 Oct 20:02:43.424 * Background saving terminated with success
483:M 18 Oct 20:07:44.001 * 10 changes in 300 seconds. Saving...
483:M 18 Oct 20:07:44.004 * Background saving started by pid 4722
4722:C 18 Oct 20:07:46.933 * DB saved on disk
4722:C 18 Oct 20:07:46.936 * RDB: 2 MB of memory used by copy-on-write
483:M 18 Oct 20:07:47.010 * Background saving terminated with success
We’ve been trying, for over a month, to get Redis caching to work, but we keep running into the same type of issue. Initially it would, somewhat randomly, start causing 404 errors on all our CSS files, breaking the entire site. So I changed the Avada options to store CSS in the DB. That fixed that issue, but now we sometimes see one of the .JS files for our theme throw a 404, and that prevents images from loading on the site. We’ve confirmed that all these issues are tied to Redis caching.
In all cases the solution has been to hit the “Purge Cache” button. Not the Settings > Redis > Flush Cache button, as that one does not address the problem, but the “Purge Cache” button that, for some reason, only seems to appear in the admin bar and nowhere else. Flushing the Object Cache does not address the 404s.
We’ve run out of settings in Avada to test for this, and Redis has almost no settings of its own. Is there anything else we can try, or should we start looking for other caching solutions?
]]>Trying to enbale Redis, the following error mesage appeared:
“Redis is unreachable:?Connection refused [tcp://127.0.0.1:6379]”
How caN I remedy this, please?
]]>I’m getting this error:
“Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.”
PRECEDENTS: Redis service terminated yesterday due to:
“Out of memory: The process “redis-server” was terminated because the system is low on memory.
Memory Information: Process Total Virtual Memory: 10042792kB. Used: 6.55 GB, Available: 8.96 GB, Installed: 15.51 GB. Uptime: 19 days, 7 hours, 30 minutes, and 42 seconds. “
As site was down. I tried next, in this order:
– Deleted wp-content/object-cache.php, (this resolves the 503 error and get things back to normal, despite object cache is disabled).
– Restarted redis service from terminal
– Issue redis FLUSHALL on terminal. It returns “OK”. Still 503 when enabling redis on the plugin.
– Deinstalled the WP Redis plugin and reinstalled again. Still 503 when enabling it. As it is a production site, I delete object-cache after each 503.
– Deinstalled the redis service on the server and re-installed from the repo (last version). Still 503 when enabling object cache on the plugin.
– Graceful Server reboot. Still 503.
– Checked wp-config, all values seem correct, as suggested on readme.doc. Tried several settings, as add a prefix, change database number, etc.
– Tested the staging site and Redis works perfectly there on staging when enabled. It is the same server, different directory on public_html.
– Deleted all wp transients on production site. Still 503.
– Redis flushall again from terminal. -> returns “OK”.
– Read this forum, everything I’ve tried doesn’t works, still a 503. (I’m aware I can delete object-cache.php to get things back to normal, without oject cache. While staging site works well all time with redis object cache
While error.log shows nothing, var/log/redis shows:
12911:M 14 Oct 2024 12:14:29.065 * 1 changes in 3600 seconds. Saving…
12911:M 14 Oct 2024 12:14:29.066 * Background saving started by pid 28339
28339:C 14 Oct 2024 12:14:29.181 * DB saved on disk
28339:C 14 Oct 2024 12:14:29.184 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
12911:M 14 Oct 2024 12:14:29.268 * Background saving terminated with success
Not sure if this is related to the staging site. However production still shows 503 when enabling redis, both on admin and front end.
Do I’m missing something?
Hello,
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
Thank you for useful plugin.
I have a question.
I installed “Redis Object Cache”on my website and I found this plugin makes “wp” keys in redis memory.
Below “wp’ keys, there are many sub folders like “comment, options, comment queries… etc.”
And I have a question.
If my webserver runs many domains(wordpress websites) and install this plugin,
the keys of same name of many wordpress websites’ are not conflicted?
ex) “a.com and b.com and c.com” have same “wp:comment:1” key.
Won’t names with the same key structure conflict with each other?
Thank you for Reading.
Kindly,
June
]]>Hello, I’m using the free Version. I know that there will be limited support and WP-Rocket. Both plugins should work fine together but I keep getting the problem that after using the Redis Plugin the website CSS is broken. Once I delete the Redis Cache it works fine again.
Unfortunately there is no setting where I can exclude things. Is there any way in solving this problem.
Thanks.
]]>Hello,
I found 2 relevant posts but the solution proposed does not actually address the issue.
I can confirm that this plugin requires 0775 for wp-content to pass the ‘writable’ check. 0755 produces the usual error NO MATTER what the permissions of object-cache.php are (I have even tried to have .redis-write-test.tmp file pre-created with 0777 permissions). Enable/disable cache obviously does not work.
Please fix this, or otherwise please explain why your plugin requires write access to the directory even when the files manipulated by it (inside that directory) are writable.
]]>3 days ago I bought the paid version of the plugin https://objectcache.pro
After testing and working with it, I came to the conclusion that it is not suitable for my site. After that I removed it from the site and requested a refund, but the developer of the plugin ignores all my requests in chat regarding the refund.
Hi Team,
I run 2x nginx container and 2x php container
nginx -> proxy to -> php container
If the redis cache is enabled using the gui it creates a file only in one php container the files is called
object-cache.php and it’s localed in the public/wp-content/object-cache.php
The problem is that wp-content can’t be a global storage as the specific version of plugins are baked in into the container image and they can’t change until the image is rebuild. This is to make sure that release is version controller/tested and can’t change.
Can this file be configurable so it can be created in the different location?
What I end up is to have 2 instances or more when the redis can only be enabled in one container.
]]>Hello,
In the at least two latest plugin versions there is an issue with admin.css file causing unnecessary redirects each time when WordPress dashboard is opened.
The issue is pretty simple. In file:
/redis-cache/includes/class-plugin.phpon the line 336 there is an extra trailing slash:
wp_enqueue_style( 'redis-cache', WP_REDIS_PLUGIN_DIR . '/assets/css/admin.css', [], WP_REDIS_VERSION );While the constant WP_REDIS_PLUGIN_DIR already has it added by the plugin_dir_url function:
define( 'WP_REDIS_PLUGIN_DIR', plugin_dir_url( WP_REDIS_FILE ) );In result this creates a path of:
/wp-content/plugins/redis-cache//assets/css/admin.css?ver=2.5.3which then redirects to:
/wp-content/plugins/redis-cache/assets/css/admin.css?ver=2.5.3The redirect could be caused also by my .htaccess file configuration (haven’t checked it), but either way – a semantic way is to use one trailing slash instead of two.
I hope I helped you with this little bug report. ??
Regards,
Edgars from Media 24
Hello,
I’ve created a thread on the bricks forum where I describe that the search results at the first search iteration they work fine. Subsequent searches fetch the same results until one minute passes or so. When I deactivate Redis plugin, the search function works fine everytime. Is there anything I can do to exclude the search results from being cached by Redis?
[SOLVED: Issue is related to some Bricks builder settings]
]]>Hello and good day.
I’ve been having issues with redis redirecting to other websites on the server after the recent wordpress and elementor update.
Are there any known issues you are aware of?
Disabling the plugin from the wp-content folder and/or deleting the objectcache.php seems to resolve the issue but it returns.
]]>Dear @tillkruess and Redis Object Cache Support Team,
We are currently using the Redis Object Cache plugin on our WordPress website, a high-traffic multilingual news platform that primarily focuses on cryptocurrency and blockchain-related content. Our website has over 56,000 posts in total, available in 8 languages, and we publish 30-50 new articles daily. Our team of 20-30 users, including publishers from various regions, actively works on the website simultaneously—creating, updating, publishing, and translating content.
Recently, we have been encountering several persistent issues that are impacting our site’s performance, detailed below:
- Error Establishing Redis Connection: We frequently receive errors such as
RedisException: read error on connection to /run/redis/redis-server.sock. This typically occurs when clearing the cache for the first time each day, after periods of inactivity, or when creating new posts. Despite having ample resources available, Redis seems unable to handle the connections consistently. - Socket Errors and HTTP 500 Errors: We are experiencing repeated socket read failures and occasional HTTP 500 errors directly linked to Redis performance issues. These disruptions significantly affect our website’s availability and overall user experience.
- Plugin-Related Issues:
- WPML: Our website relies heavily on WPML for multilingual functionality, and we’ve noticed that Redis interactions frequently coincide with performance slowdowns when WPML is active.
- Yoast SEO: Essential for our SEO strategy, Yoast is also generating a high number of Redis requests, which could be contributing to the connection issues.
- Wordfence: Security is a priority for us, and Wordfence is critical. However, it appears to be interacting with Redis in a way that may be contributing to the overall load.
- Post Views Counter: We are currently evaluating whether this plugin is necessary, but it is also making frequent requests to Redis, adding to the load.
PFA :-
https://www.awesomescreenshot.com/image/50430705?key=30ccd35b8b9f97b73d55606783f2019b
https://www.awesomescreenshot.com/image/50430704?key=cba43d0b0718defbee585926508fb7e4
Given these challenges, we are seeking your expertise and guidance. Are there any known fixes, configurations, or optimizations within the Redis Object Cache plugin that could help mitigate these issues? Specifically, are there ways to reduce or optimize the load generated by these plugins or exclude certain requests to Redis?
If there are any previously discussed solutions or recommendations that you could direct us to, it would be greatly appreciated.
Thank you in advance for your assistance. We look forward to your insights on resolving these issues and enhancing the stability and performance of our Redis setup.
Best regards,
Vimal Roy
]]>Status: Not enabled
Client:
Drop-in: Not installed
Disabled: No
PhpRedis: Not loaded
Relay: Not loaded
Predis: 2.1.2
Credis: Not loaded
PHP Version: 8.2.18
Plugin Version: 2.5.3
Redis Version: Unknown
Multisite: No
Metrics: Disabled
Metrics recorded: 0
Filesystem: Writable
WP_REDIS_PLUGIN_PATH: "/home2/quinzl1f/mrkooltech.com/wp-content/plugins/redis-cache"
Drop-ins: []i have it installed and configured my site is WooCommerce with around 5k products, i have a 7-9% cache ration but high cache rate of 96%+ is that normal ? the memory limit is quit high so its not memory limited
]]>