We do support Round the Clock 24 x 7 x 365 (+91) 883 012 3924

How to Install KernelCare on cPanel WHM server

How to Install KernelCare on cPanel WHM server

The downtime that reboots cause is a disruption for customers and nuisance for admins.
This can be easily avoided with KernelCare.
KernelCare ensures that you never miss security patches and your kernels are always up-to-date.

KernelCare is compatible with 64-bit versions
CentOS/RHEL 6.x and 7.x
CloudLinux 6.x and 7.x
Virtuozzo/PCS/OpenVZ 2.6.32
Debian 8 and 9
Proxmox VE 4
Virt-SIG/Xen4CentOS 6 and 7
Ubuntu 14.04, 15.04 and 16.04


To install KernelCare, you need to login with root user on your cPanel server.


Check for compatible kernels.
Before you purchase and install KernelCare, make certain that your system possesses a compatible kernel.
To do this, read the the KernelCare documentation.

Choose and run your preferred command.

You can choose between two different SSH commands to begin the KernelCare installation process.
To begin the KernelCare installation process, run one of the following commands:


Register the license key.

You can skip this step if you purchased a KernelCare license from the cPanel Store.
KernelCare licenses use IP-based licensing, which you don’t need to register.

The KernelCare license key deploys and registers your server. To register your key, run the following command:

/usr/bin/kcarectl --register $kc_key


Check for applied patches.

After you register KernelCare, you will need to check for applied patches.
This ensures that the automated kernel security updates ran properly on your server.
To check for applied patches, run the following command:

/usr/bin/kcarectl --info


Manually check for patch updates.

KernelCare will automatically check for new patches every four hours.
If you want to check for new patches yourself, run the following command:

/usr/bin/kcarectl --update


If you need any further assistance please do contact our support department at [email protected]


Leave a Reply

Your email address will not be published. Required fields are marked *