Page tree
Skip to end of metadata
Go to start of metadata

This document is for a previous release of cPanel & WHM. To view our latest documentation, visit our Home page.

For cPanel & WHM 11.40

(Home >> Server Configuration >> Update Preferences)

Overview

This feature allows you to define how your server handles software updates and upgrades.

cPanel & WHM Updates

You can use this section of the interface to select a release tier. Your release tier setting controls when you upgrade to a new major version of cPanel & WHM.

You can also use this interface to select how you wish your server to handle updates within a major version. 

Release Tier

Select a cPanel & WHM tier that matches your requirements. For further explanation, read our Product Versions and the Release Process documentation.

Remember:

As of cPanel & WHM 11.34, after you upgrade to a new major version of cPanel & WHM, you will not be able to downgrade to a previous major version of cPanel & WHM.

  • For this reason, you cannot select a release tier that represents a downgrade.
  • appears next to the Description for tiers that represent a downgrade.

 

The cPanel & WHM release tiers are:

TierDescriptionPublication Frequency
LTSLong-Term Support. If you do not wish to upgrade cPanel & WHM, you can select a cPanel & WHM version for as long as cPanel supports it.Not applicable.
STABLEThis version has received considerable public exposure, testing, and verification.Published least frequently.
RELEASEThis version is feature-complete and well tested. It contains all intended features and functionality. New installations default to RELEASE.Published more frequently than STABLE.
CURRENTThis version is tested and verified, but it may not contain all of the proposed functionality of a release. This tier is similar to the "release candidate" tier used under other publication schemes.Published more frequently than RELEASE.
EDGE

This version only has rudimentary testing. The features are subject to further modification. This version usually lacks official public documentation. 

Warning:

Due to the dynamic nature of EDGE builds, you should only use EDGE to test for compatibility and functionality in a controlled environment. This tier is not recommended for production servers.

Published most frequently (up to several times per week).

 

Automatic upgrades to new major versions

Previously, cPanel & WHM upgraded to the next available major version as soon as a new version became available in each release tier. As of cPanel & WHM 11.40, to reduce support ticket influx, automatic upgrades to subsequent major versions of cPanel & WHM will not always take place immediately. In certain scenarios, cPanel & WHM will apply a zero-to-three-business-day delay before your automatic upgrade takes place.

cPanel & WHM will apply a delay if all of the following are true:

  1. You are on the RELEASE or STABLE tier.
  2. You do not run the upgrade interactively.
  3. Your current version is only one major version away from the target major version.
  4. You do not run the upgrade with the Force option.

The length of your delay is randomly selected. For example, if the new major version is detected on a Friday, the upgrade will not take place until the following Monday, Tuesday, or Wednesday.

When we release a major version, you may:

  • Use the Force option in the Upgrade to Latest Version feature to upgrade immediately.
  • Take no action, unless your release tier is set to LTS, to allow the automatic upgrade to occur as described above.
  • To prevent future automatic upgrades, change your selected release tier to LTS.

Warning:

Before an upgrade, take the time to ensure that the new version is compatible with any third party software or customizations to your system. We recommend that you stage the upgrade on a test system before you upgrade your production system.

 

Daily Updates

Choose whether you wish cPanel & WHM to update automatically:

  • Automatic — Select this option if you wish cPanel & WHM to automatically update through a cron job every night at midnight.
  • Manual Updates Only — Select this option if you wish to manually update cPanel & WHM.
    • Command line — Run /usr/local/cpanel/scripts/upcp when logged in as the root user.
    • WHM — Go to the Upgrade to Latest Version interface.
  • Never Update — Select this option if you do not wish cPanel & WHM to update.

Note:

The maintenance portion of /usr/local/cpanel/scripts/upcp will always run as part of the nightly cron job, regardless of the update settings.

 

Operating System Package Updates

This feature determines whether the nightly maintenance tasks will update the RPM packages from your operating system distribution. This is similar to the yum update command. 

  • Automatic — Select this setting to automatically update the operating system packages when the /usr/local/cpanel/scripts/upcp script runs.
  • Manual Updates Only — Select this setting if you wish to manually run the /usr/local/cpanel/scripts/upcp script to update operating system packages.
  • Never Update — Select this setting if you do not wish to update the operating system packages when the/usr/local/cpanel/scripts/upcp script runs. If you select this option, you will need to run the /usr/local/cpanel/scripts/rpmup2 script to update your operating system packages.

Note:

This setting has no effect on cPanel-provided RPMs.

Apache SpamAssassin® Rules Updates

This feature defines how you wish to update the Apache SpamAssassin rules.

  • Automatic — Select this setting to automatically update Apache SpamAssassin rules when /usr/local/cpanel/scripts/upcp runs.
  • Manual Updates Only — Select this setting if you wish to manually run the /usr/local/cpanel/scripts/upcp script to update Apache SpamAssassin rules.
  • Never Update — Select this setting if you do not wish to update Apache SpamAssassin rules when the /usr/local/cpanel/scripts/upcp script runs.

Note:

  • When the cPanel update script (/usr/local/cpanel/scripts/upcp) runs, it updates Apache SpamAssassin via the Apache SpamAssassin update script (/usr/local/cpanel/scripts/sa-update-wrapper).
  • For more information about Apache SpamAssassin rules, read the Apache SpamAssassin documentation.