When you upgrade to a newer version of cPanel & WHM or install cPanel & WHM on a new server, cPanel & WHM checks your system for compatibility with the version of cPanel & WHM that you wish to install.
The cPanel & WHM installation and upgrade processes require at least 3 GB of additional disk space for staging purposes.
Blockers are conditions that do not allow the cPanel & WHM update process (
upcp) to install a particular version.
If you run an update that includes multiple major version upgrades of cPanel & WHM, the cPanel & WHM update process (
upcp) will upgrade your server to each intermediate version. The update process performs compatibility checks for each intermediate version prior to the upgrade to that version.
For example, after a system administrator runs an update on a server that runs cPanel & WHM version 70, and the target version is cPanel & WHM version 76, the cPanel & WHM update process (
upcp) performs the following actions:
The cPanel & WHM update and installation process performs two types of checks:
If cPanel & WHM encounters a compatibility issue that blocks the installation or upgrade process, the following events happen:
After you upgrade to a new major version of cPanel & WHM, you cannot downgrade to a previous major version.
Before you upgrade the version of cPanel & WHM on a server, we strongly recommend that you restore cPanel & WHM's management of all FTP targets on your server. If the FTP RPM's target is set to
For more information on how to restore cPanel & WHM management of all FTP targets on your server, read our How to Set or Unset RPM Management documentation.
When you run an upgrade of cPanel & WHM to any version, the update process performs the following standard checks:
You cannot upgrade cPanel & WHM if any of the following conditions are true:
/usr/local/cpanel/cpkeycltscript. If the problem persists, contact our support staff.
Your server's license is no longer eligible for updates.
If you experience difficulties with your license, contact our customer service department.
To ensure that the system can write files to critical directories, the cPanel & WHM update process will fail if the following directories file systems exist in a read-only state:
/etc /var /var/lib/rpm /var/cpanel /usr/local /usr/local/cpanel /usr/local/bin /usr/bin /tmp /var/tmp
As of cPanel & WHM version 11.36, the update process verifies the integrity of the RPM database. To verify the integrity of the RPM database, the update process installs and uninstalls a test RPM. The update process attempts to repair the problem, but if it cannot repair the RPM database, the upgrade attempt fails.
The following table includes the installation requirements and upgrade blockers for each version of cPanel & WHM:
If a blocker for the version of cPanel & WHM to which you wish to upgrade is present on your system when you start the cPanel & WHM update process, the update process will fail.
|cPanel & WHM version||Upgrade requirements|
Interchange is enabled.
|11.50||New installations on CentOS 7 servers require at least 1 GB of RAM, and are only available for 64-bit systems.||None|
|58||Only available for 64-bit systems.|
|Apache (httpd) 2.2.11 or older|
|62||MySQL® version 5.5 and later.||MySQL version 5.1 and earlier.|
cPanel & WHM automatically attempts to run the
/usr/local/cpanel/scripts/gensysinfo script to generate this file during the upgrade procedure. If you encounter this error, perform the following steps:
Correct any file permission problems or similar issues that prevent the
root user's write privileges.
If the problem persists, contact our support staff .
As of cPanel & WHM version 11.36, to ensure that a partial upgrade does not break your current installation, the cPanel & WHM update process downloads new files to a staging directory inside the
To ensure that there is enough disk space available for the new files, the cPanel update process checks for a minimum of 1.6GB of available disk space in the
/usr/local/cpanel/ directory before an upgrade, update, or new installation can begin. After the cPanel & WHM update process downloads the files and completes the compatibility checks, the update process replaces the prior version of each file with the new version.
cPanel & WHM checks for the amount of available disk space in the
To update to cPanel & WHM version 11.36, the following cPanel package updates must be set to Automatic or Inherit:
You cannot upgrade to cPanel & WHM version 11.36 if you set the
EXIMUP key's value to
never in the
To upgrade from cPanel & WHM version 11.34 and earlier, perform the following steps:
To upgrade from a cPanel & WHM version 11.36 release prior to 11.36.07, perform the following steps:
Run the following command:
/usr/local/cpanel/scripts/update_local_rpm_versions --edit target_settings.exim unmanaged
If you set the
EXIMUP key's value to
inherit in the
/etc/cpupdate.conf file, you may receive an error that informs you that the
EXIMUP key's value is set to
never. To resolve this issue, perform the following steps:
CPANELkey's value to
CPANEL key's value to your desired support tier (for example,
RELEASE) in the
For more information about support tiers, read our Product Versions and the Release Process documentation.
If a user owns the
whmxfer database, you must delete the database.
You must remove the Microsoft FrontPage Extensions RPM entirely from your system. In cPanel & WHM version 11.44, you can remove FrontPage in WHM's Uninstall FrontPage Extensions interface (WHM >> Home >> Front Page >> Uninstall FrontPage Extensions).
If you have set the
cpanel-php53 RPM target to
installed in the rpm.versions system, the system will block an upgrade to cPanel & WHM version 11.46.
To uninstall the
cpanel-php53 target, run the following commands:
/scripts/update_local_rpm_versions --del target_settings.cpanel-php53 uninstalled /scripts/check_cpanel_rpms --fix
For more information, read our How to Set or Unset RPM Management documentation.
New installations on CentOS 7 servers require a minimum of 1 GB of RAM, and are only available for 64-bit systems.
cPanel & WHM version 58 is only available for 64-bit systems. You cannot install or upgrade to cPanel & WHM version 58 on a 32-bit system.
If your server runs the CentOS, RHEL, or CloudLinux operating systems, it must run version 6 or later. You cannot install or upgrade to cPanel & WHM version 58 on a server that runs CentOS 5, RHEL 5, or CloudLinux version 5.
perl514RPM target is set to
perl514 RPM target's state is
unmanaged in any
.versions file in the
/var/cpanel/rpm.versions.d/ directory, the upgrade to cPanel & WHM version 58 will fail.
/var/cpanel/rpm.versions.d/local.versionsfile, use the
*.versionsfile, update the file in your preferred text editor, and then run the
cPanel & WHM version 62 requires that your server runs MySQL version 5.1 or earlier. You must upgrade to at least MySQL version 5.5 before you can upgrade your cPanel & WHM server. You can upgrade your MySQL version in WHM's MySQL or MariaDB Upgrade interface (WHM >> Home >> Software >> MariaDB/MySQL Upgrade ).
After the upgrade to cPanel & WHM version 66 finishes, WHM users in an active session must refresh their browser windows. Until they do, they may see additional frames within the WHM interface on each page load.
If LiteSpeed exists on your server, you must upgrade to LiteSpeed version 5.2.1 build 2 or later before you upgrade to cPanel & WHM version 68. Otherwise, websites will not provide the entire certificate chain and browsers may display an SSL error. For more information about how to upgrade LiteSpeed, read LiteSpeed's cPanel Plugin documentation. View the
/usr/local/lsws/autoupdate/build file to verify your LiteSpeed version information.
If your server does not contain the