Updated: 10 November 2026 · Applies to: CloudLinux OS 8, 9 and 10, key-based and IP-based licences (commands from CloudLinux documentation; not testable without a licence)
To check a CloudLinux licence, run /usr/bin/cldetect --check-license as root: it prints OK when the licence is valid. To register the server with a new or renewed key, run rhnreg_ks --activationkey=YOUR-KEY --force. For an IP-based licence (the usual kind when the licence comes from a reseller or panel provider), run clnreg_ks --force instead. All commands below are taken from CloudLinux's own documentation.
1. Check the current licence
Log in over SSH as root and run:
/usr/bin/cldetect --check-license
According to CloudLinux, this returns OK if the licence is not older than three days, and an error message otherwise. So the check also fails when the server has not refreshed its licence data from CloudLinux Network (CLN) for more than three days, even with a paid licence.
For scripts and monitoring, the quiet form returns only an exit code, 0 for a valid licence and 1 otherwise:
/usr/bin/cldetect -q; echo $?
To see which CloudLinux edition and control panel the server reports, CloudLinux documents:
/usr/bin/cldetect --detect-edition /usr/bin/cldetect --detect-cp
You can also log in to your CloudLinux Network account (cln.cloudlinux.com) to see your keys, the servers registered with each one and the licensed IP addresses.
2. Update a key-based licence
Use this when you renewed with a new key, moved from a trial to a paid key, or changed edition. A CloudLinux activation key looks like 12314-d34463a182fede4f4d7e140f1841bcf2.
- Make sure the registration tools are installed:
yum install rhn-setup
- Re-register the server with the new key. The
--forceoption replaces the existing registration:/usr/sbin/rhnreg_ks --activationkey=YOUR-NEW-KEY --force
When the new key is for a different licence type or edition, CloudLinux asks for confirmation; add--migrate-silentlyto skip that prompt. - Update the local licence data and check it again:
/usr/bin/cldetect --update-license /usr/bin/cldetect --check-license
3. Update an IP-based licence
An IP-based licence is tied to the server's public IP address, not to a key. CloudLinux says to confirm first that the server's public IP is the one licensed, then run:
yum install rhn-setup /usr/sbin/clnreg_ks --force
Then run /usr/bin/cldetect --check-license again. If you moved the server to a new IP address, the licence must be moved to that IP by whoever issued it (CloudLinux, your reseller or your provider) before clnreg_ks can succeed.
4. If the check still fails
- Wrong key or IP: CloudLinux advises checking the intended edition, that the activation key is valid, or that the public IP is licensed.
- Network or certificate errors: fix the cause the message names (for example DNS, a firewall blocking outgoing HTTPS, or a wrong server clock) rather than trying the key again and again. CloudLinux says this too.
- Token errors: CloudLinux's diagnostics suggest running
rhn_checkto fetch a new licence token. For the "specified activation token can not be found" message, see CloudLinux error: specified activation token can not be found on the server. - Converting a server: registering an existing CloudLinux OS server is different from converting AlmaLinux or Rocky Linux with
cldeploy. For conversion errors see CloudLinux Conversion: the retry_no_cache yum Error and Converting With cldeploy.
Moving or removing a server
According to CloudLinux, when you retire or reinstall a server you should remove it from your CLN account so the licence is freed for the next server. To move CloudLinux settings such as LVE limits to a new server, see How to migrate all CloudLinux settings to another server.
Related articles
If your CloudLinux licence came with a Ucartz server and the check fails, open a support ticket with the output of cldetect --check-license and the server's IP address.
Official documentation: CloudLinux OS installation and licence registration, CloudLinux command-line tools (cldetect).