Designed for ea-NGINX (Cache/Proxy) on cPanel+WHM. Made to help you fly online! 🚀

Merlot Digital (by TNC)

TNC Toolbox aims to enhance your WordPress experience with NGINX-on-cPanel (ea-nginx).
Built for our Managed Server clients, we’ve open-sourced it so others can enjoy it too!
With a heavy focus on the Apache + NGINX as Reverse Caching Proxy web stack, the plugin aims to help with Website Management, Performance and Security.
<blockquote>
❤️ FOSS by <a href="https://tnc.works" rel="nofollow ugc">The Network Crew Pty Ltd</a> (TNC) for <a href="https://merlot.digital" rel="nofollow ugc">Merlot Digital</a> & the world. ❤️
</blockquote>
<h3>Functionality</h3>
At the moment, TNC Toolbox:
<ul>
<li>Allows you to enable, disable and purge the NGINX User Cache</li>
<li>Purges the NGINX Cache magically on post/page publish/update!</li>
<li>Also purges the Cache when the WP Core is successfully updated</li>
<li>Lets you know if the plugin is activated but not yet configured</li>
<li>Only allows Admins to enable/disable caching & edit configs</li>
<li>Shows you the status of cP UAPI via disk usage info</li>
<li>Purge when any ACF config options are saved</li>
<li>Supports scheduled post publishing!</li>
</ul>
Eager for even more capabilities?
We plan to add further features as clients & the community request it.
Please let us know your ideas on <a href="https://github.com/The-Network-Crew/TNC-Toolbox-for-WordPress/" rel="nofollow ugc">GitHub</a> – we’d love to hear from you!
<h3>Caching Deployments</h3>
Caching ideals: 
– Don’t forget, ea-NGINX (reverse proxy caching) is meant to be 2nd-level 
– ie. Make sure your WP site also has on-site caching, like WP Super Cache 
– You can go further with caching, and should: like browser-caching assets!
3-layer Cache: 
1. NGINX Caching Proxy (ahead of Apache) 
2. WP Super Cache, WP Rocket, etc on-site 
3. htaccess/etc rules for Browser Caching
This way, you can ensure maximum efficiency!
The key is to purge when stale, so properly configuring your WP Plugin Cache is critical to ensuring that you don’t end up with cache misses due to stale data that could’ve/should’ve been purged by garbage collection, preloading, etc, rule-sets.
<h3>Updating from v1 to v2.x.x</h3>
On every website running the plugin, check that:
<ol>
<li>Website is reporting v2.x.x plugin version.</li>
<li>Plugin has been activated post-update. *</li>
<li>Config exists in the plugin settings.</li>
<li>API status checker reports OK.</li>
<li>/wp-content/tnc-toolbox-config/ folder is gone.</li>
</ol>
(* Change to main plugin file name may result in deactivation)
<h3>Verifying cP+WHM Logs</h3>
If you’d like to ensure actions are firing properly at a deeper level:
<ol>
<li>WHM > Tweak Settings > Logging > Enable cPanel API Log > On</li>
<li>WHM > Terminal > <code>tail -f /usr/local/cpanel/logs/api_log</code></li>
<li>WordPress > Update a Post/Page, or explicitly Purge</li>
<li>WHM > Terminal > You should see the action fire!</li>
<li>WHM > Terminal > Ctrl+C to close the tail</li>
</ol>
Note: To do this, you require <code>root</code> access to the Server.

Alternatives to TNC Toolbox: Web Performance

Top alternatives