Using Cache Manager in cPanel

This is a guide with steps on accessing and using the different functions of the cPanel plugin, Cache Manager.  This plugin is available on all hosting plans besides the Lite and Launch Business Shared plans.  Access to cPanel will be needed to complete these steps.  

Related Articles

Disable Caching on Website
Purge Website's NGINX Cache

Steps to Configure Caching

1. Log into the appropriate cPanel
2. Navigate to the Software section
3. Locate and click the Cache Manager icon
4. Once loaded, two different action tabs will show:
   1. Purge Cache - allows partial or full purging of a website's cache
      1. View the article on purging a website's NGINX cache
         TIP: For WordPress users not wanting to use Cache Manager to clear a website's cache after every update, the NGINX WordPress helper plugin can help easily automate caching based on defined triggers
   2. Options - can enable/disable caching, change default refresh time, add new bypass URLs, or configure advanced options
      1. Enable Caching: If you are making a high number of radical changes to the site, and you want to see changes immediately, you will want to disable caching. This will suspend caching while you are working on the site, so you can see changes without having to repeatedly flush the cache
      2. Default Refresh Time: The default refresh time tells the caching service how long it should wait before checking for updates to your website
      3. Bypass URL: The bypass URL setting tells the caching service which URLs should never be cached. These URLs will always be loaded directly from the server and never from the page cache. To add a new URL, click the + button. Conversely, to remove a URL use the X button.
      4. Advanced Options and their descriptions:
         1. Proxy Protocol
            • Allows the ability to select whether a website should force HTTP or HTTPS. To use the secure protocol, (https://), a valid SSL certificate must be installed on the domain.
              
         2. ModSecurity Response Cache Time
            • By default, ModSecurity (406) errors are not cached. If the website is receiving an influx of connections blocked by ModSec, then this option can mitigate excessive resource usage by caching the response for the specified amount of time.
         3. 404 Error Cache Time
            • Allows the ability to set how long the cache will wait before NGINX sends a request for content with a 404 error. A higher number helps mitigate excessive usage from bots crawling your website. A lower number helps clear out 404s for content served up by a third-party Content Delivery Network (CDN)
              
         4. Max requests per minute and Rate limit Path
            • These settings work in tandem to reduce the frequency of fulfilling specific requests. For instance, to mitigate excessive resource usage generated by WordPress’s xmlrpc.php script:
            • Enter the path to the xmlrpc.php file in the Ratelimit Path: field
            • Set the maximum number of requests per minute that will be allowed, in the Max requests per minute: field
         5. Enable gzip compression
            • The level of gzip compression determines how compressed the data is
              NOTE: The values range from one to nine (1-9), nine (9) being the most compressed.
            • This setting requires a delicate balance of compression with server resources and transfer speed with bandwidth.
              

              EXAMPLE: A value of nine (9) requires the most server resources for compression but the least bandwidth to transfer; whereas a value of one (1) requires the least amount of server resources for compression but the most bandwidth to transfer.

         6. Error Page
            • Allows the ability to set a custom error page for a 503 (Service Unavailable) or 504 (Gateway Timeout) error by entering the path to the custom error page file previously created, starting from the home directory of the domain.
              

              EXAMPLE: If the value error-page was entered, then these errors would be redirected to https://yourdomain.com/error-page

5. Select the Save Changes button