Webinoly provides powerful caching capabilities to significantly improve your site’s performance. This guide covers FastCGI cache, Redis object caching, and custom cache configurations.
FastCGI Cache
FastCGI cache is automatically configured when you create WordPress or PHP sites with caching enabled.
Enable Cache for a Site
sudo site example.com -cache=on
- Enables FastCGI caching for WordPress or PHP sites
- Creates optimized cache configurations
- Sets up cache bypass rules for logged-in users
Disable Cache
sudo site example.com -cache=off
Disabling cache will remove all cache-related configurations and may impact site performance.
Custom Cache Settings
For advanced users, you can customize cache behavior:
# Set custom cache validity period
sudo site example.com -cache-valid=[200,5m]
# Configure cache skip patterns
sudo site example.com -skip-cache="/admin|/cart|/checkout"
# Skip cache for specific cookies
sudo site example.com -skip-cookie-cache="user_session|shopping_cart"
Use -cache-valid to control how long different response codes are cached. Format: [status_code,time]
Query String Caching
Control how query strings affect caching:
# Enable query string caching
sudo site example.com -query-string-cache=on
# Disable query string caching (default)
sudo site example.com -query-string-cache=off
# Never cache specific query strings
sudo site example.com -query-string-never-cache="fbclid|gclid|utm_source"
Clear Cache
Webinoly provides commands to clear different cache types:
Clear All Caches
sudo webinoly -clear-cache=all
- FastCGI cache
- OpCache
- Redis cache
- Memcached
Clear Specific Cache Types
# Clear FastCGI cache only
sudo webinoly -clear-cache=fastcgi
# Clear Redis cache
sudo webinoly -clear-cache=redis
# Clear Memcached
sudo webinoly -clear-cache=memcached
# Clear OpCache
sudo webinoly -clear-cache=opcache
Clear Site-Specific Cache
# Clear cache for a specific site
sudo webinoly -clear-cache=example.com
# Clear cache for a subfolder
sudo webinoly -clear-cache=example.com -subfolder=/blog
Redis Object Caching
Redis provides persistent object caching for WordPress and PHP applications.
Install Redis
Redis is installed as part of the PHP stack:
Or install separately:
For WordPress sites, install a Redis object cache plugin (like Redis Object Cache) and configure wp-config.php:
define('WP_REDIS_HOST', 'localhost');
define('WP_REDIS_PORT', 6379);
Redis is particularly effective for sites with complex database queries or high traffic.
Monitor Redis
Check Redis status and statistics:
# Connect to Redis CLI
redis-cli
# Get cache statistics
redis-cli INFO stats
# Monitor real-time commands
redis-cli MONITOR
Memcached
Memcached is an alternative in-memory caching system.
Install Memcached
Install a Memcached plugin and add to wp-config.php:
$memcached_servers = array(
'default' => array('localhost:11211')
);
Cache Configuration Files
Webinoly cache configurations are stored in:
- FastCGI Config:
/etc/nginx/conf.d/fastcgi.conf
- Custom Cache:
/etc/nginx/conf.d/webinoly.conf
- Site Cache:
/etc/nginx/apps.d/[domain]-[type]cache.conf
Default Cache Settings
FastCGI Cache Validity:
- 200 responses: 7 days
- 301/302 redirects: 7 days
- Inactive: 30 days
- Max size: 256MB (adjusts based on RAM)
Cache Path: /run/nginx-cache/
Proxy Cache
For reverse proxy configurations:
# Create reverse proxy with caching
sudo site example.com -proxy=http://backend:8080
# The cache is automatically configured for proxy responses
Always test cache configurations thoroughly, especially skip rules, to ensure logged-in users and dynamic content work correctly.
Best Practices
- Start Conservative: Begin with default cache settings and optimize based on monitoring
- Exclude Dynamic Pages: Always exclude checkout, cart, and user account pages from cache
- Monitor Cache Hit Rates: Check
/var/log/nginx/access.log for cache status
- Clear After Updates: Clear cache after deploying code changes or WordPress updates
- Use Redis for Objects: Combine FastCGI page cache with Redis object cache for best results
Troubleshooting
Cache Not Working
-
Check cache directory permissions:
-
Verify cache configuration:
-
Check cache headers:
curl -I https://example.com
Stale Content
If seeing old content:
# Clear specific site cache
sudo webinoly -clear-cache=example.com
# Or manually remove cache files
sudo rm -rf /run/nginx-cache/example_com*
# Check cache hit ratio in access logs
sudo grep 'X-Cache' /var/log/nginx/example.com.access.log | wc -l
# View FastCGI cache statistics
sudo du -sh /run/nginx-cache/*