The messages CachePilot shows, what they mean and what to do. Start with wp cachepilot test; it tells you in a few lines whether Redis and the object cache work.
No Redis server found
The Overview shows a connection form instead of the figures. CachePilot tried the places listed in getting started and none answered. Enter host, port and password in the form, or set the WP_REDIS_* constants in wp-config.php.
If Redis answers but rejects the password, the form says Redis rejected the password.
The PHP extension phpredis is missing
CachePilot needs phpredis and stays inactive without it. Check it on the command line:
php -m | grep -i redisIf nothing is listed, ask your host to install the extension for the PHP version of your site.
The drop-in could not be written
The message Redis answered, but the object cache drop-in could not be written to wp-content. means that WordPress may not write to wp-content. Fix the permissions and run:
wp cachepilot dropin installRedis is not reachable
wp cachepilot status ends with Redis Connection: failed and the reason. The site keeps working: after a failed connection the drop-in skips Redis for 30 seconds and WordPress reads from the database. Check that the Redis server runs and that host, port and TLS match.
When Redis is back, CachePilot empties the cache once, so no page is built from stale data.
Pages do not come from the page cache
Request the page as an anonymous visitor and check the header:
curl -sI https://example.com/ | grep -i x-cachepilotNo HIT on the second request? These requests always bypass the page cache:
- Logged-in visitors and visitors with a comment or password cookie
- wp-admin, the REST API, wc-api, feeds, embeds, XML and XSL files and robots.txt
- Search results, 404 pages and incomplete HTML
- Cart, checkout and account pages of WooCommerce
- URLs with query parameters that are not on the list of cacheable parameters, or more than 6 of them
Caution: if another page cache plugin owns advanced-cache.php, CachePilot does not touch it and its own page cache stays off.
The safety check switched a module off
After Autopilot switches on Page Cache or Minify, it loads your pages. If a page answers with a server error, a cached page is cut off or much shorter, or a minified file fails, the module is switched off again. The Autopilot log names the reason.
If the log says that the module could not be checked because the server blocks requests to itself, the module stays on. Allow loopback requests from the server to its own site.
Group flush does not work
The active object cache does not support flushing groups. means that the drop-in in wp-content is not the one of CachePilot. Run wp cachepilot status: the line CachePilot Drop-in should say Yes.
More questions
Still stuck? Beta testers send feedback with the output of wp cachepilot status through their account.
Redis memory is full. What now?
The hourly check of Autopilot warns when Redis memory is full. Give Redis more memory or set an eviction policy on the server.
The admin bar menu is missing on the front end.
That is on purpose. CachePilot loads nothing on the front end; the admin bar menu shows in the admin only.
Debug comments appear in my HTML.
The Debug module adds cache figures as HTML comments, only to HTML pages. Switch it off under CachePilot, Modules.
A page shows an old price.
Price changes purge the product pages. If you changed prices outside WordPress, run wp cachepilot flush.