Nginx Cache Purge Preload

توسط Hasan CALISIR

NPP lets WordPress users manage Nginx Cache Purge and Preload (FastCGI, Proxy, SCGI, UWSGI) operations directly from the WordPress admin dashboard — actively warming the cache via site crawl, so your Nginx cache is always preloaded and ready.

➡️ Resources:

• Visit the NPP Main Development Repository – Docs, issues & contributions and more.
• Visit the safexec Main Development Repository – NPP’s privilege-dropping C wrapper.
• Explore NPP Containerized – Ready to run full stack Nginx Docker setup.
• Refer to the plugin’s Help tab for additional guidance.

Features

🧹 Purge All Nginx Cache: Completely clear all cached data stored by Nginx.

🔄 Preload All Nginx Cache: Warm the Nginx cache with the most recent data for the entire website.

🎯 HTTP Purge (ngx_cache_purge): When the Nginx cache module is available, NPP uses it as the fastest purge path. Falls back gracefully to index and filesystem purge when the module is not present.

🚀 Auto Preload Nginx Cache: Automatically preloads the cache when Auto Purge is enabled for a POST/PAGE or after the Purge All action.

🧼 Auto Purge Nginx Cache: Purge cache on Post/Page content changes, comment status updates, theme/plugin updates, or when compatible Cache Plugins trigger a purge. Nginx cache is preloaded automatically if Auto Preload is enabled (for the entire site or individual page).

🔗 Purge Scope (Related Pages): Automatically purge related pages such as the Homepage, WooCommerce Shop page, and Category/Tag archives when a single URL is purged. Optionally preload those pages to keep the cache warm.

⏰ Schedule Nginx Cache Purge & Preload via WP Cron: Automate the purge and preload process using WordPress Cron jobs.

🧭 Proxy Support for Preload: Route preload requests through a proxy server for edge-case environments and containerized deployments.

⏱️ Live Preload Progress Monitoring: Watch the Nginx cache preload process in real time — complete with a dynamic progress bar, currently processed URL, 404 tracking, server load, and total completion time.

🌐 Remote Nginx Cache Purge & Preload via REST API: Remotely trigger cache purging and preloading through REST API endpoints.

⚙️ Manual Nginx Cache Purge & Preload: Allow manual purging and preloading of cache through the table view in the Advanced Tab.

📚 Nginx Cache Analyzer: Full HIT/MISS cache analyzer dashboard, from the last preload crawl with what is currently stored in the Nginx cache. Instantly spot uncached pages and Purge or Preload them directly in the Advanced Tab.

🔍 On-Page Nginx Cache Purge & Preload: Manually purge and preload Nginx cache for the currently visited page directly from the frontend.

🗝️ Custom Cache Key Support: Define a regex pattern to parse URLs based on your custom _cache_key format.

📊 Monitor Plugin and Nginx Cache Status: Monitor plugin status, cache status, and Nginx status from the Status tab.

📈 Cache Coverage Ratio: Live gauge in the WordPress dashboard widget showing the cache coverage ratio, based on the last preload snapshot. Refreshable on demand without a page reload.

☁️ Cloudflare APO Sync: Automatically mirrors NPP purge actions to Cloudflare APO to keep edge cache synchronized with your Nginx cache.

🔴 Redis Object Cache Sync: Bidirectional sync between NPP and Redis Object Cache. NPP Purge All flushes the Redis object cache, and a Redis flush triggers a full Nginx cache purge via NPP (when auto-purge is enabled).

🛒 WooCommerce Auto-Purge: Automatically purges Nginx cache when WooCommerce product stock quantity changes, stock status changes (in stock / out of stock / on backorder), or when an order is cancelled and stock is restored.

🔒 Concurrent Purge Serialization: Atomic lock mechanism prevents simultaneous purge operations from colliding, ensuring cache integrity during concurrent admin actions or background events.

🧩 Modular by Design: Easily integrate with external scripts and automation tools.

🖥️ User-Friendly Interface: Easy-to-use AJAX-powered settings, integrated into the WordPress admin bar and dashboard for quick access.

📋 Admin Notices and Logs: Receive notifications and view logs for plugin status and all cache-related actions within the WordPress admin area.

📧 Email Notifications: Receive email alerts upon completion of preload actions, with customizable templates to suit your needs.

Credits

This plugin is developed and maintained by Hasan CALISIR.

Privacy Policy

Prior to version 2.1.5, NPP optionally collected basic anonymous usage data when users explicitly opted in. As of version 2.1.5, all data collection and the opt-in mechanism have been completely removed. NPP collects no data whatsoever.

Support

For support and assistance, please contact Hasan CALISIR at hasan.calisir@psauxit.com.

License

This plugin is licensed under the GPLv2 or later.For more information, visit the plugin development page: Nginx Cache Purge Preload

Manual Installation

Upload the “fastcgi-cache-purge-and-preload-nginx” folder to the “/wp-content/plugins/” directory.
Activate the plugin through the “Plugins” menu in the WordPress admin dashboard.
Configure plugin settings under “Settings” -> “Nginx Cache Purge Preload” in the WordPress admin dashboard.
Access “Nginx Cache Purge Preload” operations from the WordPress admin bar (frontend & backend), the Admin Dashboard, and the Plugin Settings page.

Automatic Installation

Log in to your WordPress admin panel, navigate to the “Plugins” menu and click “Add New”.
In the search field type “Nginx Cache Purge Preload” and click “Search Plugins”. From the search results, pick “Nginx Cache Purge Preload” and click “Install Now”. WordPress will ask you to confirm to complete the installation.

سوالات متداول

Does this plugin require Nginx?

Yes. NPP is designed exclusively for Nginx web servers running on Linux. It does not work on Apache, shared hosting, or environments where shell_exec is disabled.

Does it require the ngx_cache_purge Nginx module?

No. The ngx_cache_purge module is optional. When available, NPP uses it as the fastest purge path (HTTP Purge). If it is not present, NPP automatically falls back to a URL index lookup and then a full filesystem scan. Nothing breaks either way.

What server dependencies are required?

Mostly basic, built-in shell tools are required. wget is required for cache preloading. For hardened shell execution, safexec is highly recommended — see the Help tab for installation instructions.

Why is the plugin not working on my environment?

The most common reasons are: shell_exec is disabled, the PHP-FPM user lacks write permission to the Nginx cache directory, or nginx.conf is not detected. See the Help tab for a full environment checklist and solutions.

I am getting permission errors. What should I do?

This is the most common issue in environments where the WEBSERVER-USER (nginx/www-data) and PHP-FPM-USER are different. NPP provides a one-liner bash script to automate the fix using bindfs on monolithic servers. For containerized environments, users can review the full configuration setup via NPP Containerized See the Help tab Permission Issues section or the GitHub repository for details.

Does it work with Cloudflare?

Yes. NPP has built-in Cloudflare APO Sync that mirrors every purge to Cloudflare’s edge cache automatically. Requires the official Cloudflare WordPress plugin. Enable it under Settings.

Does it work with Redis Object Cache?

Yes. NPP supports bidirectional sync with the Redis Object Cache plugin. A Purge All in NPP flushes Redis, and a Redis flush triggers a full Nginx cache purge. Enable it under Settings.

Is it compatible with WooCommerce?

Yes. NPP includes built-in WooCommerce Auto-Purge for stock changes and order events, and supports purging the Shop page as a related URL when a product is updated.

Can I use it alongside other caching plugins?

Yes, but disable page caching in other plugins to avoid conflicts. You can keep their frontend optimization features (minification, lazy loading, CDN) active. See the Help tab for details.

Where can I find the allowed Nginx cache paths?

NPP restricts cache paths to prevent accidental deletion of system files. Allowed roots are /dev/shm/, /tmp/, /var/, and /cache/. The path must be at least one level deep (e.g. /var/cache/nginx). Full details in the Help tab.