The error message "Kernel update is prohibited" during CloudLinux installation typically indicates that there are restrictions in place that prevent the installation or update of the kernel on your system. This restriction is often enforced by the hosting provider or system administrator to maintain stability and compatibility.

If you encounter this error, here are steps you can take to address it:

1. Contact Your Hosting Provider or System Administrator:

   If you're seeing this error, it's likely that there are server-level restrictions in place. Reach out to your hosting provider or system administrator to inquire about the policy regarding kernel updates.

2. Check with CloudLinux Support:

   If you're installing CloudLinux on your own server and you encounter this error, consider reaching out to CloudLinux support. They may have specific recommendations or workarounds for your situation.

3. Understand the Policy:

   If there are restrictions in place, it's important to understand the reasoning behind them. Certain hosting providers or organizations have policies in place to ensure the stability and security of their servers.

4. Consider Alternative Solutions:

   If you're unable to update the kernel due to restrictions, consider exploring alternative solutions or discussing with your hosting provider to find an appropriate workaround.

5. Discuss Options with Hosting Provider:

   If you require a specific kernel version or need to update the kernel for a specific reason, discuss your requirements with your hosting provider. They may be able to provide guidance or offer alternative solutions.

6. Review Documentation and Policies:

   Check any documentation or policies provided by your hosting provider or CloudLinux for specific information regarding kernel updates and restrictions.

7. Ensure Compliance:

   If there are restrictions in place, ensure that you comply with the policies set by your hosting provider or system administrator. Attempting to bypass these restrictions may lead to further issues.

Remember, it's crucial to work closely with your hosting provider or system administrator to address this issue, as they have a deep understanding of the specific configurations and policies in place on your server.