New in CWP Edge-LatestFree with every CWPpro licenceWebsites up to 300x faster

CWP now includes LSPHP, LSAPI-Cache and CWP Cage at no extra cost with all CWPpro licences. The LSAPI-Cache plugin is integrated into our WordPress and other script installers, and CWP Cage gives every user complete isolation. Available now in the CWP Edge-Latest version.

Get CWPpro ›

CWP Secure Kernel – Questions About Automatic Installation and Reboot on CWPpro

Started by Dex, November 18, 2026, 06:50:11 PM

Previous topic - Next topic

Dex

Hello CWP Team,

First of all, I would like to sincerely thank the entire CWP development team for the impressive number of updates and improvements released recently.

I truly appreciate the time, dedication, and hard work you are putting into improving the platform, fixing issues, and strengthening server security.

As a long-time CWP user, I am very pleased to see the continuous development of the panel. Your efforts are greatly appreciated.

I would also like to ask for some clarification regarding the recent Secure Kernel changes introduced in CWP 1.30.22.

**My server configuration:**

- Operating system: CentOS 7
- Control panel: CWPpro
- Current running kernel: `3.10.0-1160.119.1.el7.x86_64`
- Default boot kernel: `3.10.0-1160.119.1.el7.cwpsec.x86_64`

I currently have a CWPpro license, but I do not have a Managed, Business, or Enterprise subscription, and I have not enabled the CWP Secure Kernel service.

After the recent updates, I received the following warning:

**Secure Kernel reinstalled**

"A distro kernel update had removed the CWP Secure Kernel from this server (installonly rotation). CWP reinstalled it (3.10.0-1160.119.1.el7.cwpsec.x86_64) and set it as the boot kernel; reboot to restore Secure Kernel protection."

When I open the Secure Kernel section in the CWP administration panel, I see the following message:

"CWP Secure Kernel is not active on this server."

The panel also indicates that this feature is available for Managed, Business, and Enterprise plans.

I checked the current kernel and boot configuration using:

`uname -r`

Result:

`3.10.0-1160.119.1.el7.x86_64`

And:

`grubby --default-kernel`

Result:

`/boot/vmlinuz-3.10.0-1160.119.1.el7.cwpsec.x86_64`

Therefore, my server is currently running the standard CentOS kernel, but the CWP Secure Kernel has automatically been configured as the default kernel for the next reboot.

**I would appreciate clarification on a few points:**

1. Is it normal and intentional for CWP 1.30.22 to automatically install the Secure Kernel and configure it as the default boot kernel, even on CWPpro servers without an active Secure Kernel subscription?

2. If I reboot my server, will it safely boot with the new CWP Secure Kernel despite the feature not being activated or included in my subscription?

3. When the Secure Kernel service is inactive, does the new kernel behave like the standard CentOS kernel, without enforcing additional security restrictions?

4. Could booting with this kernel potentially affect existing services such as Apache, Nginx, PHP-FPM, MariaDB, SSH, CSF firewall, or other server components?

5. Should users without a Secure Kernel subscription leave the automatically configured boot kernel unchanged, or is it preferable to continue using the standard CentOS kernel?

6. Is a reboot actually recommended for CWPpro users who do not subscribe to the Secure Kernel service?

My server is currently running normally, and I have not experienced any issues.

I have not rebooted it since this change, as I prefer to understand the expected behavior before making any decision that could affect a production server.

I fully understand that the purpose of these updates is to improve security and reliability. I simply want to make sure that everything will continue working correctly after the next reboot.

Any clarification from the development team would be greatly appreciated, and I believe it could also help other CWPpro users who may have noticed the same behavior.

Once again, thank you very much for your outstanding work, your continued dedication, and all the improvements you are bringing to CWP.

Keep up the excellent work!

Best regards,

6Sense

It rebooted on my server without an issue. Secure Kernel did not have it's rules loaded (had to click update to install them).

There's also a safe mode you can select that logs only if you want to be cautious
6Sense - Web Design, Development & Web Hosting

Dex

Thank you very much for your reply and for sharing your experience. I really appreciate it.

I'm glad to hear that your server rebooted successfully without any issues.

However, my situation is slightly different.

I am using CWPpro, but I do not have an active subscription to the CWP Secure Kernel service .

In fact, when I open the Secure Kernel section in my administration panel, it clearly states:

"CWP Secure Kernel is not active on this server."

My concern is that the recent CWP update automatically installed the Secure Kernel and configured it as the default boot kernel, even though I do not use this service.

I simply wanted to understand whether rebooting into this new kernel is completely safe for servers like mine, where Secure Kernel protection is not activated and no subscription is available.

May I also ask whether you have an active Secure Kernel subscription on your server?

I prefer to clarify this point before rebooting my production server, especially since everything is currently working perfectly.

Thank you again for taking the time to help. Your feedback is greatly appreciated!


Quote from: 6Sense on November 18, 2026, 08:48:38 PMIt rebooted on my server without an issue. Secure Kernel did not have it's rules loaded (had to click update to install them).

There's also a safe mode you can select that logs only if you want to be cautious


6Sense

Hi Mate,

I only have CWP Pro also without the support subscription. It looks like we all get Secure Kernel now at no extra cost. Enjoy!
6Sense - Web Design, Development & Web Hosting

Dex

Thank you very much, mate, for sharing your experience and providing this useful information. I really appreciate your help.

Let's wait for some clarification from the CWP developers or forum administrators regarding these recent changes.

Thanks again, and all the best!

Dex

Hello CWP Team,

First of all, thank you for fixing the Secure Kernel issue so quickly in the latest update. I really appreciate your work and your attention to this problem.

After updating my server, I received the notification confirming that the Secure Kernel boot default had been reverted to the original stock kernel.

I also verified this through SSH:

**Running kernel:**
`3.10.0-1160.119.1.el7.x86_64`

**Default boot kernel:**
`3.10.0-1160.119.1.el7.x86_64`

Both match, and Secure Kernel is now shown as inactive. Everything appears to be working normally.

However, I noticed something unexpected during the update.

My server was previously running **CWPpro 1.30.x (LTS)**. When I clicked the usual update button, expecting the latest LTS fixes, the panel was upgraded to **CWPpro 2.0.18 (Edge)** instead.

I did not intentionally select the Edge channel.

I would appreciate some clarification on the following points:

1. **Is the automatic switch from LTS to Edge expected, or could this be a bug?**

2. **Is it recommended to keep Edge 2.0.18 on a production CentOS 7 server, or would it be better to stay on the LTS channel?**

3. **If I should return to LTS, what is the safest supported procedure?** I would prefer to avoid any unnecessary package changes, database modifications or server reboots.


4. **The "Update CWP Version" button still appears active**, although the CWP Update page confirms:

  - Installed version: 2.0.18
  - Latest version: 2.0.18 — Up to date

  Is this normal, or could it be an update notification issue?

My server is currently working normally, and I would like to keep it stable, particularly because I have an existing MariaDB package issue from a previous upgrade attempt.

Thank you again for your help and for resolving the Secure Kernel issue.

Best regards.

6Sense

Hmm interesting, I'm on CWP 1.30.24 with secure kernel active (4.18.0-553.180.1.el8_10.cwpsec.x86_64) I think...
6Sense - Web Design, Development & Web Hosting

Dex

Hi Mate,

I'm glad to see that Secure Kernel is active on your server. That's reassuring!

It also looks like we're running different server environments. Your kernel appears to be based on EL8, while my server is still running CentOS 7 with kernel 3.10.0-1160.119.1.el7.x86_64. This might explain some of the differences we're seeing.

On my side, something unexpected happened after the latest CWP update. My panel switched from the 1.30.23 LTS series to **CWPpro 2.0.18 Edge**, even though I never manually selected the Edge channel.

Just to clarify, I did **not reboot my server** to activate Secure Kernel. I simply clicked the update button in the CWP panel, as I normally do. After the update, I noticed that my panel had switched to the Edge version.

I'm wondering whether this might be related to the update process, although I'm not sure.

Fortunately, everything is working fine so far, and I must admit that the new interface feels noticeably faster and smoother.

I'm just waiting for clarification from the CWP developers about this unexpected switch.

Thanks again for sharing your experience!

Maz-V


6Sense

Mmm but I think I have have an issue too. I suspect my servers kernel version is not correct for CWPpro version: 1.30.24 as there are 2 newer versions that I assume are 1.30.23 & 1.30.24. They appear to be the non secure kernel versions but are not selected after a reboot or 3.

[root@srv ~]# uname -r
4.18.0-553.180.1.el8_10.cwpsec.x86_64
[root@srv ~]# grubby --default-kernel
/boot/vmlinuz-4.18.0-553.180.1.el8_10.cwpsec.x86_64
[root@srv ~]# rpm -q kernel-core
kernel-core-4.18.0-553.184.2.el8_10.x86_64
kernel-core-4.18.0-553.186.1.el8_10.x86_64
kernel-core-4.18.0-553.180.1.el8_10.cwpsec.x86_64
[root@srv ~]# cat /etc/almalinux-release
AlmaLinux release 8.10 (Cerulean Leopard)
6Sense - Web Design, Development & Web Hosting

Dex

Since you mentioned earlier that you only have CWPpro without a Secure Kernel subscription, your situation might be related to the recent CWP bug.

According to the 1.30.24 changelog, Secure Kernel could be installed and selected as the default boot kernel on servers that never had it. The latest update was supposed to restore the original kernel as the boot default without removing any installed kernels.

However, your results still show the Secure Kernel as both the running and default kernel, even after several reboots.

I would strongly recommend contacting CWP support to confirm whether the fix was correctly applied to your server before making any manual kernel changes.

In my case, the fix successfully restored my original kernel without requiring a reboot.

I also contacted support about my unexpected switch from LTS to Edge 2.0.18. They confirmed that it was a planned rollout, fully supported on CentOS 7, and that no action was needed.

Their support has been excellent, so I definitely recommend asking them to check your situation.

Hope this helps, Mate!

anandmys

Quote from: 6Sense on November 18, 2026, 10:06:27 PMHi Mate,

I only have CWP Pro also without the support subscription. It looks like we all get Secure Kernel now at no extra cost. Enjoy!

CWP Secure Kernel is not active on this server
This server does not run the CWP Secure Kernel, so there are no rules to manage.

The Secure Kernel is installed by CWP support for Managed, Business and Enterprise plans. Contact support if your plan includes it.