Fatal error: Uncaught Error: Class "Redis" not found
“Uncaught Error: Class "Redis" not found” in WordPress: causes and what to check
# Common log entries
PHP Fatal error: Uncaught Error: Class "Redis" not found in /wp-content/object-cache.php
This error comes from a Redis object-cache drop-in (wp-content/object-cache.php) running on a server without the PhpRedis extension. WordPress loads the drop-in before any plugin, so the whole site stops, even when the cache plugin itself was deactivated.
Which of these do you see?
The drop-in moved with wp-content, but the PHP on the new server was built without the Redis extension.
PHP extensions are installed per PHP version, so switching versions can leave PhpRedis out.
Common causes
References
Rather not fix it yourself? Let WP119 handle it automatically.
Errors caused by stale cache files or a lost object-cache backend are handled automatically: the system removes the stuck cache files and, when the cache backend is unreachable, removes the leftover configuration. Fixes are made on a copy of your site in the recovery station and written back only after re-verification passes. In your site’s database, the protected tables (members, comments, orders and form submissions) are copied as structure only. In SSH and FTP mode, the system creates a pre-recovery backup on your host before writing back and restores from it if verification after write-back fails. If the recovery cannot be completed, the recovery fee is refunded in full.
- Initial assessment: Site URL entry
- Copy to the recovery station: Work on a copy
- Diagnosis: Item-by-item checks
- Recovery and verification: Home and inner pages
- Write-back or delivery: Only after verification passes
Use WP119 when this message stops the site or the admin area from loading.
Check my site →