On 10 November 2026 CloudLinux started a gradual rollout of a new cloudlinux-release package that adds TuxCare Extended Lifecycle Support (ELS) repositories for alt-PHP (Hardened PHP), alt-Python, alt-Node.js, and alt-Ruby. Once the repos are on, alt-* updates and CVE fixes come from TuxCare through yum, dnf, or apt as normal.
On most licensed servers this needs no work. It does need attention if you run a local mirror, filter outbound traffic, pin rhn-client-tools, or have servers with lapsed or broken registration, because an ELS repo returning 403 now stops the whole update run.
What the update installs
cloudlinux-release pulls in els-php-release, els-python-release, els-nodejs-release, and els-ruby-release, and updates rhn-client-tools where it is too old to fetch the ELS token. Minimum versions:
| Release | cloudlinux-release | rhn-client-tools |
|---|---|---|
| CloudLinux 7 | 7.9-2.18 | 2.0.2-57 |
| CloudLinux 7 Hybrid | 7.9-2.19 | 2.0.2-57 |
| CloudLinux 8 | 8.10-17 | 3.0.5 |
| CloudLinux 9 | 9.8-4 | 3.0.5 |
| CloudLinux 10 | 10-6 | 3.0.5 |
| CloudLinux for Ubuntu 22.04 | 0.1-13 | 3.0.5 |
For now every alt-* build is published to both TuxCare ELS and CloudLinux's own repos. CloudLinux says ELS will later become the only source, announced in advance and with no date yet. After that, a server with the ELS repos off stops getting alt-* fixes, including the backports that keep legacy Hardened PHP versions safe. There is no opt-out from that switch.
Check a server
dnf repolist | grep -E 'php-els|alt-python|alt-nodejs|alt-ruby'
grep -l 'cloudlinux-release: switched off' /etc/yum.repos.d/*.repo
The first command lists the ELS repos that are enabled. The second prints nothing when all of them are on. Repos the package left disabled carry a comment starting # cloudlinux-release: switched off. On Ubuntu, grep /etc/apt/sources.list.d/*.list instead.
If repos are switched off on a registered server, the token usually hasn't arrived yet. Fetch it now:
rhn_check
What breaks updates
- Lapsed license or broken registration with an old token. The ELS repos return 403 Forbidden. On CloudLinux 7 to 10 that aborts the entire
yum updateordnf update. On Ubuntu,apt-get updateexits non-zero and anything chained after it doesn't run. Runrhn_checkif registration is valid; otherwise fix the CLN registration or renew the CloudLinux license. Servers that were never registered simply keep the repos off. - Outbound filtering. Allow HTTPS to
repo.alt.tuxcare.comandrollout.alt.tuxcare.com. Add them alongside the hosts in outbound firewall ports for license checks. - Excludes and version locks. An
exclude=line,dnf versionlock, orapt-mark holdonrhn-client-toolsblocks the update. Remove it first. Don't excludealt-common-releaseoralt-php-els-metaeither. - Ubuntu held packages.
apt-get upgradeholds the newcloudlinux-releaseback. Install it explicitly, and avoidapt full-upgrade, which may offer to removealt-phpXX-fpmpackages:
apt install rhn-client-tools cloudlinux-release
On RPM systems, dnf update cloudlinux-release (or yum on CloudLinux 7) pulls the new package without waiting for the rollout.
Does the CloudLinux TuxCare ELS repository cost extra?+
Why does dnf update fail with 403 Forbidden on CloudLinux?+
Can I disable the TuxCare ELS repositories on CloudLinux?+
Which hosts do CloudLinux ELS updates need through the firewall?+
Next steps
- Review which PHP versions customers actually use in CloudLinux PHP Selector before the ELS-only switch lands.
- Check the earlier CloudLinux package signing key switch landed on mirrored and pinned servers too.
- Patch the November alt-nodejs security release once the repos are confirmed on.