Updated: 9 November 2026 · Applies to: cPanel and WHM 134 (LTS) to 138, root SSH access; commands and settings from the cPanel documentation (not testable without a cPanel licence)

To update cPanel and WHM from the command line, log in to the server as root over SSH and run /usr/local/cpanel/scripts/upcp. It installs the newest build of the release tier your server follows. Check the installed version first and afterwards with /usr/local/cpanel/cpanel -V.

/usr/local/cpanel/cpanel -V
/usr/local/cpanel/scripts/upcp

Both commands come from cPanel’s documentation. /scripts/upcp is the same script under its short path.

Check the cPanel version from the command line

According to cPanel, any of these shows the installed version:

  • /usr/local/cpanel/cpanel -V prints the version and build.
  • whmapi1 version returns the version through the WHM API, in the version field (cPanel’s own example value is 11.88.0.9999: the major version follows the 11. prefix).
  • In WHM, the version number is shown in the top navigation bar. Clicking it opens Upgrade to Latest Version.

What is the latest cPanel and WHM version?

Major versions have even numbers. At the time of writing, cPanel’s release table lists:

  • 138: the newest version (released around July 2026).
  • 136: released around April 2026.
  • 134 (LTS): the long-term support version, supported until about June 2027.
  • 110 (LTS): the older LTS version, end of life around December 2026.

Which of these your server gets depends on its release tier, not on how often you run upcp. Our article cPanel upgrade: how to update cPanel and WHM to the latest version lists the operating system limits that block some upgrades.

Update cPanel step by step

  1. Take a backup, or at least make sure your latest backup is complete. cPanel recommends testing major upgrades on a staging server first.
  2. Log in as root:
    ssh root@your-server-ip
  3. Note the current version:
    /usr/local/cpanel/cpanel -V
  4. Start the update in the background, so a dropped SSH connection does not interrupt it:
    /usr/local/cpanel/scripts/upcp --bg
  5. Follow the log. According to cPanel, background runs write to /var/cpanel/updatelogs/update.TIMESTAMP, where TIMESTAMP is a Unix time:
    ls -t /var/cpanel/updatelogs/ | head -3
    tail -f /var/cpanel/updatelogs/update.TIMESTAMP
  6. When it finishes, check the version again with /usr/local/cpanel/cpanel -V.

If the update stops with a licence error, refresh the licence with the cPanel licence update command (cpkeyclt) and see cPanel licence update failed for the usual causes.

upcp options

According to cPanel, upcp accepts these options (each also works without the two dashes):

  • --bg: run in the background and log to /var/cpanel/updatelogs.
  • --cron: update using the settings in /etc/cpupdate.conf.
  • --force: reinstall all files even if the server is up to date. It overrides your update preferences and moves the server to the latest version.
  • --sync: repair the files of the installed version without downloading a newer one. You cannot combine it with --force.
  • --security: apply only critical security updates (normally run hourly by cron).
  • --log=/path/to/file: write the log to another file.

Release tiers and /etc/cpupdate.conf

The tier decides which version upcp installs. According to cPanel:

  • LTS: one version a year gets long-term support (security and critical fixes only).
  • STABLE: widely tested, published less often than RELEASE.
  • RELEASE: feature-complete and tested. New installations use this tier. Automatic upgrades to a new major version wait a random delay of several business days.
  • CURRENT: the release candidate tier.
  • EDGE: only basic testing; for test servers, not production.

You change the tier in WHM under Server Configuration > Update Preferences, or in /etc/cpupdate.conf. cPanel documents this example file:

CPANEL=release
RPMUP=daily
SARULESUP=daily
SECURITY_UPDATES=hourly
STAGING_DIR=/usr/local/cpanel
UPDATES=daily
  • CPANEL: the tier (lts, stable, release, current, edge) or a fixed version number such as 134.
  • UPDATES: daily (automatic), manual (only when you run upcp) or never, which cPanel does not recommend.
  • RPMUP and SARULESUP: operating system packages and SpamAssassin rules (daily, manual or never).
  • SECURITY_UPDATES: hourly or never.

After editing the file, run /usr/local/cpanel/scripts/upcp to move to the newest build of the new tier. Important: according to cPanel, after you upgrade to a new major version you cannot downgrade to a previous one. Choosing LTS on a server that already runs a newer version does not take it back.

Reinstall WHM or repair a broken cPanel

For damaged or missing cPanel files, reinstall the current files first:

/usr/local/cpanel/scripts/upcp --sync

If that does not help, --force reinstalls everything, but remember it also upgrades to the latest version of your tier:

/usr/local/cpanel/scripts/upcp --force

The same option exists in WHM: cPanel > Upgrade to Latest Version, tick the force checkbox and click Click to Upgrade.

A complete reinstall is different. According to cPanel there is no uninstaller: to remove cPanel and WHM you must reformat the server, and cPanel installs only on a freshly installed operating system. So a “clean” reinstall means backing up the accounts, reinstalling the OS, installing cPanel and restoring the accounts.

Prefer not to handle cPanel updates yourself? With managed cPanel VPS hosting we take care of updates, security and monitoring, and our cPanel server management covers your own servers.

Official documentation: the upcp script, the cpupdate.conf file, product versions and the release process.

Related services

KVM VPS hosting

NVMe SSD and full root access, with Free Basic Managed Support.

Unmanaged dedicated servers

full root access and free IPMI KVM, with Free Basic Managed Support.

Managed dedicated servers

our engineers look after the server for you, from $135 a month.

Was this answer helpful?

Still stuck? Open a ticket