Emergency server help: get in touch

cPanel upcp Failed: Fix Upgrade Blocked Problems

How to read the cPanel update log, resolve the common causes of a failed upcp run (RPM conflicts, disk space, blocked tiers, EOL operating systems such as Rocky Linux or Ubuntu 22.04) and get the server back onto a supported, patched build.

Published Updated 8 min read

Short answer: If cPanel upcp failed, the update log names the blocker or error, so read it before changing anything: grep ' E ' /var/cpanel/updatelogs/last | head -40. The usual causes are an operating system the target version no longer supports (Rocky Linux from 134, Ubuntu 22.04 from 136, RHEL 9-family below 9.5 from 132), which needs a migration rather than a setting; broken third-party repositories or altered cPanel packages, fixed with dnf clean all and check_cpanel_pkgs --fix; and less than 5 GB free in /usr/local/cpanel. (Reviewed October 2026.)

Applies to cPanel & WHM 132, 134 and 136 (and later) on AlmaLinux 8/9/10, CloudLinux 8/9 and Ubuntu 24.04; legacy notes cover CentOS 7/CloudLinux 7 on version 110 (ELS), Rocky Linux 8/9 and Ubuntu 22.04

A cPanel server that has stopped updating is a server that is missing the 2026 root-escalation fixes, so an upcp failure is a security incident in waiting, not a cosmetic issue. The update script is verbose about why it stopped, but the reason is buried in a long log, and several of the 2026 causes are policy decisions (dropped operating systems, tier retirements) rather than bugs. This guide covers how to find the reason and what to do for each.

Find the failure in the log

Run the update in the foreground so you see it live, then inspect the log:

/scripts/upcp --force
less /var/cpanel/updatelogs/last
grep ' E ' /var/cpanel/updatelogs/last | head -40
grep -iE 'fatal|blocker|blocked' /var/cpanel/updatelogs/last | head -40

The first [FATAL] or blocker line is the cause. Everything after it is fallout. Also check WHM » Server Configuration » Update Preferences for the tier and WHM » cPanel » Upgrade to Latest Version, which shows blockers in the interface with a short explanation.

Confirm what you are on and what you are trying to reach:

whmapi1 version
cat /etc/cpupdate.conf
cat /etc/redhat-release 2>/dev/null || lsb_release -d

Unsupported operating system

This is the most common 2026 cause and there is no configuration fix; it needs a migration plan.

  • Rocky Linux 8 and 9: support ended with version 134. A Rocky server stays on 132 at most and receives no further updates, including security builds. The supported route is the in-place conversion to AlmaLinux using the deployment script, covered in migrating Rocky to AlmaLinux.
  • Ubuntu 22.04: last supported in 134. Version 136 and later block Ubuntu 22 and require 24.04. Move to 24.04 with cPanel’s ELevate tool, or rebuild.
  • CentOS 7, CloudLinux 7, AlmaLinux 8 below the required minor: the 110 tier is the last for EL7; with paid Extended Lifecycle Support it is covered through 2027 (cPanel’s documentation: until 1 January 2028), and it gets nothing after that. RHEL 9-family systems must be at 9.5 or later since 132.
  • AlmaLinux 8 or 9 wanting AlmaLinux 10 features: use ELevate, covered in our ELevate guide.

The log message in these cases mentions the OS name and says the target version does not support it. Do not try to edit /etc/redhat-release or fake the version; the update will half-apply and leave a broken server.

Tier blockers

Moving between versions has rules. You cannot go backwards: after an upgrade to a new major version, cPanel does not support a downgrade. When an update spans several major versions, upcp upgrades through each intermediate version itself and runs the compatibility checks before each one; if a step is blocked, the server stays on the last version that passed. For a server that is very far behind, cPanel recommends reaching an intermediate version first by setting it in /etc/cpupdate.conf, then returning to a named tier:

sed -i 's/^CPANEL=.*/CPANEL=11.134/' /etc/cpupdate.conf
/scripts/upcp
whmapi1 set_tier tier=release
/scripts/upcp --force

A blocker also appears when the target version needs something the server does not have, for example a supported MySQL version or RHEL 9.5 or later for 132; the blocker text names it. Separately, version 136 removed cPanel’s legacy Ruby on Rails and RubyGems interfaces (deprecated since version 66); move applications built with them to the method in cPanel’s How to Create Ruby Web Applications documentation before you upgrade.

Package and repository failures

When the log shows dnf or yum errors, the OS package layer is the problem rather than cPanel:

dnf clean all
dnf makecache
dnf check
rpm -Va --nofiles --nodigest 2>&1 | grep -v '^\.\.\.' | head

Typical findings are a third-party repository (Remi, a stale CloudLinux mirror, an old MariaDB repo) with a broken metadata URL, a partial transaction left by a crash (dnf history and dnf history redo help), or a package conflict between an EA4 PHP and a Remi PHP. Disable the offending repository and rerun upcp. If cpanel- packages themselves show as modified in rpm -V, run:

/scripts/check_cpanel_pkgs --fix

It reinstalls anything cPanel considers corrupt from its own mirror.

Disk, clock and package repair

upcp needs a few gigabytes free on /usr and /var and enough RAM to run the perl installer. Check df -h /usr /var /tmp and free -m. The other silent killer is the system clock: a drift of more than a few minutes causes TLS failures against the update mirrors that look like connectivity errors. chronyc tracking should show a small offset; fix with chronyc makestep. Also confirm that outbound HTTPS to httpupdate.cpanel.net is open in CSF’s TCP_OUT.

When the log is a mess of partially applied files, cPanel provides a resync that compares every installed file with the mirror and replaces differences:

/scripts/upcp --sync

If even that fails because the local cPanel perl or the update script itself is broken, do not rerun the installer over the live system: cPanel supports the installer only on a freshly installed operating system and provides no uninstaller. Collect the error from the update log and the cPanel error log, then open a ticket with cPanel Technical Support, or rebuild on a fresh OS and migrate the accounts:

grep ' E ' /var/cpanel/updatelogs/last | tail -20
less /usr/local/cpanel/logs/error_log

Take a full backup first. Our backup-verify script checks that every account has a recent archive that decompresses and lists cleanly, and with --deep that SQL dumps end properly. It does not restore an account, import a database or start a service, so before a major upgrade also restore one account to a test server: that is the only proof the backup will bring a site back.

A common pitfall: disabled auto-updates

Many servers that “cannot update” simply have updates turned off in Update Preferences from a migration years ago, and then hit multiple blockers at once because they are far behind. Set the daily updates back on:

whmapi1 set_cpanel_updates updates=daily
grep -E 'UPDATES|RPMUP' /etc/cpupdate.conf

UPDATES=daily and RPMUP=daily are what you want. Manual-only updates mean you are the security team, and 2026 has shown the vendor patches faster than most teams can schedule.

Undo or roll back

  • A major-version upgrade cannot be rolled back: cPanel does not support downgrading to a previous major version. Take a full backup or a hypervisor snapshot before you run upcp on a server that is several versions behind.
  • If you pinned a version with CPANEL=11.xxx in /etc/cpupdate.conf, return to your normal tier afterwards with whmapi1 set_tier tier=release (or stable/lts), otherwise the server stays on that version.
  • Re-enable any third-party repository you disabled (set enabled=1 in its file under /etc/yum.repos.d/) once the update has finished, if the software that needs it is still installed.
  • If daily updates do not suit the server, switch back with whmapi1 set_cpanel_updates updates=manual; keep security updates on.

Verify

After a successful run, whmapi1 version reports the target build, /var/cpanel/updatelogs/last ends with a completion line and no [FATAL], and the version banner in WHM matches. Check that all services restarted cleanly with /scripts/restartsrv_cpsrvd --check and systemctl --failed. Then compare the build against the CVE-to-build mapping to confirm you are past the September bulletins. Add a weekly check of /var/cpanel/updatelogs/last to your monitoring so the next failure surfaces within days, not months.

Official documentation (checked 9 October 2026): Upgrade Blockers (cPanel docs) · cPanel Deprecation Plan · Third-Party Software End of Life Policy (cPanel docs) · Extended Lifecycle Support OSes update (cPanel announcement) · The upcp Script (WHM documentation) · Finding the error in a cPanel & WHM update failure (cPanel Support) · The cPanel Update Configuration File – cpupdate.conf · WHM API 1: set_tier · WHM API 1: set_cpanel_updates · The check_cpanel_pkgs Script (cPanel docs) · Installation Guide – Install cPanel & WHM

Related guides: What changed in cPanel 138: Meridian, Ask AI, Nova, MCP and domain rename · Install ImageMagick and PHP Imagick for EA-PHP on AlmaLinux 8/9/10 (and CloudLinux CageFS) · Managing web log retention and Apache log cleanup on cPanel (v136+).

Frequently asked questions

Does a failed upcp run break the server or its accounts?

Usually not. upcp checks blockers before it changes files, and a failure at the blocker stage leaves the server exactly as it was. A failure mid-way through the file sync is rarer and is what /scripts/upcp --sync exists to repair.

How long does /scripts/upcp --force take?

A routine update finishes in ten to thirty minutes depending on how many builds behind the server is and the speed of the mirror. A multi-tier catch-up runs once per hop, and --sync can take an hour.

Can I skip cPanel versions, for example from 110 straight to 138?

Not by going backwards, and not past a version your operating system cannot run. When an update spans several major versions, upcp itself upgrades through each intermediate version and runs the compatibility checks before each one; if a step is blocked, the server stays on the last version that passed. For a server that is very far behind, pin an intermediate version in /etc/cpupdate.conf first, run upcp, then return to a named tier.

Maintenance record

This guide changes servers, data or security settings, so we re-check it against current versions on a fixed schedule. Take a backup or snapshot before you start.

Maintained by
srvScripts editorial team
Supported versions
cPanel & WHM 132, 134 and 136 (and later) on AlmaLinux 8/9/10, CloudLinux 8/9 and Ubuntu 24.04; legacy notes cover CentOS 7/CloudLinux 7 on version 110 (ELS), Rocky Linux 8/9 and Ubuntu 22.04
Last full review
Next review

Share this guide

Free website test

Is your website set up right?

Check SSL, security headers, redirects, robots.txt, sitemap, llms.txt and security.txt in one test. It takes about 30 seconds.