Theme
Cache settings
NitHost layers three caches. Toggle them per site and purge when content changes.
Who can use this page? Site access with cache controls (typically write/manage — site owners).
Site Actions → Cache Settings
Cache layers
| Layer | Technology | What it does |
|---|---|---|
| FastCGI page cache | Nginx | Caches full HTML responses — skips PHP for hits |
| Object cache | Redis | App-level cache (WordPress, Laravel, …) |
| Legacy cache | Memcached | For apps that expect Memcached |
FastCGI
- Auto-bypasses logged-in users, POST requests, and WooCommerce cart/checkout paths
- One-click Purge Cache clears the site’s cached pages
- Pair with WordPress-friendly headers where enabled
Redis object cache
- Redis DB 0 is reserved for the panel; sites get DB 1–14 automatically
- WordPress: NitHost can install/repair the Redis companion plugin (WordPress Tools → Repair Redis)
Memcached
- Availability and capacity depend on your hosting service
- Enable only if the application requires it
Purge cache
From Cache Settings or the site card quick action:
- Open Cache Settings
- Click Purge Cache (or the per-layer purge if offered)
- Confirm toast — next uncached request rebuilds the cache
Purge after:
- Theme/plugin updates
- Deploying new code
- Bulk content edits
- Restoring a backup
Recommendations
| Site type | Suggested starting point |
|---|---|
| WordPress public | FastCGI + Redis on |
| Logged-in-heavy app | FastCGI careful/bypass; Redis on |
| APIs (Node/Python) | FastCGI off unless reverse-proxied static |
| Legacy Magento-era | Memcached if required |
If pages look stale, purge the site’s page cache from the panel. If the problem remains, check the application cache and contact NitHost support; do not flush a shared cache database.