The WordPress Redis connection error is a problem that most site owners never encounter — because Redis is not a default WordPress component. If you are seeing it, your site is configured to use Redis as an object cache, and something has broken the connection between WordPress and the Redis server. The WordPress Redis connection error typically manifests as a site-breaking message in the WordPress admin dashboard or on the front end: "Error establishing a Redis connection" or a similar message from the Redis object cache plugin. Without the object cache working, WordPress either falls back to slower database queries for every cached request, or — depending on the plugin — it refuses to load at all until the WordPress Redis connection error is resolved. This guide covers every cause of the WordPress Redis connection error and the specific fix for each, including how to gracefully disable Redis if it cannot be made to work in your current environment.
What the WordPress Redis Connection Error Actually Means
Redis is an in-memory data store that WordPress uses as an object cache — storing frequently accessed database query results, processed data, and computation-heavy outputs in RAM so they do not need to be recalculated on every page request. The connection between WordPress and Redis is managed by a plugin — most commonly Redis Object Cache by Till Krüss, or the WP Redis plugin by Pantheon — which intercepts WordPress's caching calls and routes them to the Redis server instead of the default file-based or database-based caching. The WordPress Redis connection error occurs when this plugin cannot reach the Redis server to read or write cached data.
The WordPress Redis connection error is different in character from most WordPress errors because it is a connection failure to an external service rather than a PHP error or a file system problem. Redis runs as a separate server process — either on the same server as WordPress or on a dedicated caching server — and the connection requires the correct host, port, authentication password (on secured Redis instances), and database index. Any of these being wrong, or the Redis service itself being unavailable, produces the WordPress Redis connection error regardless of what WordPress or PHP are doing correctly.
The sites most likely to encounter the WordPress Redis connection error are those on managed WordPress hosting platforms that include Redis as a performance feature — Kinsta, WP Engine, Cloudways, Flywheel, and similar hosts typically provide Redis as an opt-in caching layer. The WordPress Redis connection error on these platforms usually appears after a hosting configuration change, a Redis service restart that was not communicated to the WordPress configuration, or an upgrade to a different hosting plan that changed the Redis server's address or authentication requirements. On self-hosted VPS environments, the WordPress Redis connection error most commonly appears after a server reboot where Redis was not configured to start automatically.
Diagnose the WordPress Redis Connection Error by Checking Redis Server Status
Before fixing the WordPress configuration, confirm that Redis itself is running. A WordPress Redis connection error caused by a stopped or crashed Redis process requires restarting the service, not reconfiguring the WordPress plugin. Attempting to fix the WordPress configuration while Redis is not running wastes time and will not resolve the error.
- If you have SSH access to the server: run
redis-cli pingin the terminal. If Redis is running and accessible, it responds withPONG. Any other response — connection refused, timeout — confirms the WordPress Redis connection error is at the service level. - Check whether the Redis service is running:
systemctl status redisorservice redis statusdepending on your Linux distribution. - If Redis is stopped: start it with
systemctl start redisorsudo service redis start. - If Redis is running but
redis-cli pingstill fails: check the Redis configuration file (typically at/etc/redis/redis.conf) for the bind address and port settings. Redis bound to127.0.0.1only accepts local connections — if WordPress is connecting via a different IP, the connection is refused. - After confirming Redis is running, return to the WordPress admin and check whether the WordPress Redis connection error has cleared in the Redis Object Cache plugin's settings panel.
On managed WordPress hosting where you do not have SSH access, contact the hosting provider's support team and ask them to confirm the Redis service is operational for your account. Managed hosts typically have a status dashboard or a support channel specifically for infrastructure issues. If the WordPress Redis connection error appeared after a hosting plan change or a recent infrastructure event on the host's side, the host can restore the Redis connection from their end without any changes needed in WordPress.
Fix WordPress Redis Connection Error From Configuration Problems
When Redis is confirmed to be running but the WordPress Redis connection error persists, the problem is in the connection configuration — the host, port, password, or database index that WordPress is using to connect to Redis does not match what the Redis server is actually configured to accept. The Redis Object Cache plugin stores these settings in wp-config.php as defined constants.
The standard Redis connection constants in wp-config.php look like this:
define( 'WP_REDIS_HOST', '127.0.0.1' ); // Redis server address
define( 'WP_REDIS_PORT', 6379 ); // Redis port (default: 6379)
define( 'WP_REDIS_PASSWORD', 'your_password' ); // Only if Redis requires auth
define( 'WP_REDIS_DATABASE', 0 ); // Database index (default: 0)
define( 'WP_REDIS_TIMEOUT', 1 ); // Connection timeout in seconds
define( 'WP_REDIS_READ_TIMEOUT', 1 ); // Read timeout in seconds
The most common configuration cause of the WordPress Redis connection error is an incorrect host address. If Redis is on the same server as WordPress, the host should be 127.0.0.1 (localhost). On managed hosting platforms where Redis runs on a separate server — common on platforms that provide Redis as an infrastructure service — the host is a specific IP or hostname that the hosting provider supplies. Verify the host value in wp-config.php matches what your hosting provider has specified for your Redis instance. A host value that was correct for a previous server is one of the most common post-migration causes of the WordPress Redis connection error.
Password authentication is the second most common configuration cause of the WordPress Redis connection error. Redis requires a password when the requirepass directive is set in redis.conf. If WP_REDIS_PASSWORD is absent in wp-config.php but Redis requires authentication, or if the password in wp-config.php does not match the current Redis password, the authentication fails and the WordPress Redis connection error results. On managed hosts that rotate Redis credentials, the hosting provider's dashboard or environment variables are the source of the current correct password.
Authentication and PHP Extension Requirements
The WordPress Redis connection error can also appear when the PHP-Redis extension required to communicate with Redis is missing or installed incorrectly. The Redis Object Cache plugin can use one of two PHP extensions to communicate with Redis: phpredis (a compiled PHP extension that provides the best performance) or Predis (a PHP library that requires no compiled extension). If neither is available, the WordPress plugin cannot communicate with Redis regardless of whether the Redis server itself is running correctly.
| Client type | What is required | Performance | Installation |
|---|---|---|---|
| phpredis extension | PHP extension compiled for your PHP version | Best — native C extension | Requires server-level installation; contact host |
| Predis library | Composer package or bundled library | Good — pure PHP | Can be enabled without server access |
| Neither available | N/A | N/A | WordPress Redis connection error on all connection attempts |
Check which client is being used in the Redis Object Cache plugin settings — it shows the detected client type on the status page. If the plugin shows "Client: not connected" or lists no client, neither extension is available and that is the root of the WordPress Redis connection error. To enable Predis as a fallback without server access, add define( 'WP_REDIS_CLIENT', 'predis' ); to wp-config.php. To install phpredis, contact your hosting provider — it requires installing a PHP extension at the server level, which is not possible from within WordPress.
Temporarily Disable Redis to Restore Site Function
When the WordPress Redis connection error cannot be resolved immediately — because the Redis service is down and the hosting provider needs time to restore it, or because configuration changes require server-level access that is not immediately available — disabling Redis caching entirely restores the site to normal function while the WordPress Redis connection error is addressed separately. A site without Redis object caching is slower than one with it, but it is functional. A site blocked by the WordPress Redis connection error is not.
The quickest way to disable Redis without needing to access the WordPress dashboard (which may itself be showing the WordPress Redis connection error) is to rename or remove the object cache drop-in file. Connect via FTP and look for a file named object-cache.php in the wp-content/ directory. This file is the drop-in that routes WordPress caching calls to Redis. Renaming it to object-cache.php.disabled immediately disables Redis object caching — WordPress falls back to its default caching behaviour, and the WordPress Redis connection error stops blocking site function. The site operates normally without the drop-in, using WordPress's native WP_Object_Cache class backed by memory within the request instead of Redis.
Our guide on fixing the WordPress database connection error covers the database-level connection problems that can appear alongside the WordPress Redis connection error on sites undergoing infrastructure changes — both are connection failures to backend services, and addressing them together on a newly migrated site is more efficient than treating them separately. Our guide on how to optimise WordPress performance covers Redis object caching in the context of the broader WordPress performance stack, including when Redis is and is not the right caching tool for a given site's architecture. The Redis documentation covers the configuration directives — bind address, requirepass, maxmemory, and persistence settings — that most commonly produce the WordPress Redis connection error when set incorrectly for a WordPress hosting environment.
Top comments (0)