by
Hasan CALISIR
5 (4 reviews)
Nginx Cache Purge Preload
Nginx cache purge and preload for WordPress (FastCGI, Proxy, SCGI, uWSGI), plus a live Fail2Ban dashboard with attack maps and abuse reports.
Nginx Cache Purge Preload ranks #11,753 among WordPress.org plugins with 200+ active installations, is #300 of 1,658 in the Performance category, a 5/5 rating from 4 reviews, and was last updated Oct 7, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v2.1.8
Current Version v2.1.8
Updated 3 weeks ago
Last Update on 07 Oct, 2026
Refreshed 2 days ago
Last Refreshed on
#300 of 1,658 in Performance
Top 25% by installs
Downloads -29.1% this week
Actively maintained
Rank
#11,753
—
No change
Active Installs
200+
-17%
KW Avg Position
39.2
0.2 better
Downloads
7.1K
+6 today
Support Resolved
0%
—
No change
Rating
100%
Review 5 out of 5
5
(4 reviews)
Next Milestone 300
200+
300+
767
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 35 more installs to reach 300+
Rank Changes
Current
#11,753
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
4 reviews
Overall
100%
5
4
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Support Threads Overview
Resolved
Unresolved
1
Total Threads
0
Resolved
1
Unresolved
0%
Resolution Rate
Security History
Source: WPVulnerability1 known vulnerability on record · 1 in the last 24 months · checked 3 months ago
-
Nginx Cache Purge Preload [fastcgi-cache-purge-and-preload-nginx] < 2.1.3
CVE-2025-6213 · Fixed in v2.1.3
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 2.1.8
- Last Updated
- Oct 07, 2026
- Requires WP
- 6.5+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- Hasan CALISIR
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 4
- Support Threads
- 1
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
LiteSpeed Cache
7M+ installs
#5
Wordfence Security – Firewall, Malware Scan, and Login Security
5M+ installs
#11
Hostinger Tools
3M+ installs
#20
WP Super Cache
1M+ installs
#36
Speed Optimizer – The All-In-One Performance-Boosting Plugin
1M+ installs
#44
WP Fastest Cache – WordPress Cache Plugin
1M+ installs
#47
WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
1M+ installs
#52
Maintenance
1M+ installs
#59
TL;DR
AI summary of the plugin's readmeThis plugin is for WordPress site owners running Nginx (FastCGI, Proxy, SCGI, UWSGI) who need to manage cache purging and preloading from the dashboard. It automates clearing and warming the Nginx cache so pages stay served from a fresh, preloaded cache instead of being manually purged.
- Purge and preload Nginx cache
- WP-CLI command support
- HTTP Purge via ngx_cache_purge
- Auto Purge on content changes
- Scheduled purge via WP Cron
- Remote purge/preload via REST API
- Nginx Cache Analyzer dashboard
- WooCommerce stock-change auto-purge
Frequently Asked Questions
Common questions about Nginx Cache Purge Preload
Yes. NPP is engineered with a highly defensive, multi-layered "Narrow Gate" architecture using a lazy bootstrap mechanism to minimize your server's attack surface. To minimize performance overhead and vulnerability surfaces, NPP stays dormant on anonymous public traffic, verifying entry paths before heavy core files ever load into memory. For hardened environment security, it also ships with its own secure privilege-dropping wrapper, safexec—a custom C-binary utility designed to isolate system commands and execute them under a low-privilege runtime user.
Yes. Nginx must be part of your web server stack. It does not matter if Nginx is configured as a frontend reverse proxy or as the direct backend server—as long as Nginx is handling the caching layer on a Linux environment, the plugin works perfectly. It does not work on standalone Apache setups, restricted shared hosting, or environments where shell_exec and exec are disabled.
Yes. NPP shows your Fail2Ban bans and unbans in a live dashboard with jail activity, repeat offenders, a Top Attack Countries map and network details per IP. It is read-only: Fail2Ban keeps blocking as before, and NPP never bans, unbans or edits your jails. The feature is optional and separate from cache management.
Open the Fail2Ban tab, copy the generated nppp-webhook action file to /etc/fail2ban/action.d/, add the generated line under each jail in jail.local, run sudo systemctl reload fail2ban, then press Test Connection. The Fail2Ban host needs curl and flock and must be able to reach your site. Several servers or jails can report to one dashboard.
Yes. It requires a secret token you can regenerate at any time, validates every field, ignores replayed events and rate-limits requests. The tab also provides an optional Nginx rate-limit snippet, and rejected requests are listed in the Endpoint Attacks card.
No. A report is sent only when an administrator clicks Send in the Fail2Ban tab or runs the WP-CLI command. You can preview each report, send a test email, use dry-run mode, and set a minimum ban count and a per-IP cooldown.
The banned IP, jail, event type, timestamp and looked-up network details, in a dedicated database table. Events are deleted after 90 days by default, can be cleared from the Fail2Ban tab, and are removed on uninstall. See the Privacy Policy and External services sections.
No. The ngx_cache_purge module is optional. When available, NPP uses it as the first 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. Currently relying on ngx_cache_purge module today introduces unnecessary security and stability risks to your server and not recommended. Unproven Security (Lack of updates): The original module project has not been actively maintained for several years. It receives no routine security reviews, vulnerability patches, or bug fixes. Unreliable Codebase (Fragmented availability): Because the original project stalled-abandoned, the community has created multiple independent "forks" just to keep it working. This fragmentation makes it nearly impossible to guarantee which version is actually secure or fully compatible with your nginx config and version. Vulnerable Defaults (Outdated system packages): Due to the lack of an proven, and trusted release, most Linux distributions default to shipping outdated, decade-old versions of this module. These legacy builds lack modern security standards and frequently experience compatibility issues in real-world production scenarios.
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. For large cache-heavy websites, especially when Nginx cache paths are located on FUSE-based mounts (such as bindfs to solve permission issues), ripgrep (rg) is strongly recommended for significantly faster cache purge performance.
Hard Dependencies shell_exec – The primary dependency used for core plugin functionality. exec – Required for executing ripgrep RG Purge. Optional Dependencies: proc_open, proc_close, proc_get_status – Required for the health check of background preload process. putenv, getenv – Required to pass critical runtime flags to the safexec and drive the URL Normalization feature.
