Author Topic: CWP 1.5 / cwpsrv-1.24.0-2 update: Are GUI modules -ModSec, Firewall, Yum, New Ba  (Read 13 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
Hello community,
I'm holding off on updating my production servers (AlmaLinux) to the latest 1.5 build (specifically around cwpsrv-1.24.0-2) due to widespread reports of GUI modules breaking.

Before I proceed, I wanted to ask if anyone has successfully updated in the last 48 hours and can confirm that the following issues are actually resolved:

1.ModSecurity Manager: Loads correctly and allows toggling rules/domains without blank pages.

2.Firewall (CSF): No longer shows a blank page or "module does not exist" errors.

3.Yum Manager: No longer stuck on "checking for updates" or returning 404 errors.

4.New Backup Module Email Reports: This is a chronic issue. Notifications are inconsistent. When they do arrive, they are vague: they don't specify if the backup was local or remote, they lack a clear success/failure status, and they often only confirm one account, leaving the status of other accounts completely unknown. Has this reporting been improved?

My current status: My backend is perfectly fine. Apache syntax is OK, services are running, and ModSecurity is actively blocking threats in the background. The issue is strictly the CWP Admin GUI failing to load these specific modules due to what seems to be a jQuery/script conflict introduced in the update.

I have Proxmox snapshots ready, but I want to avoid a rollback scenario if possible, as I have recent, specific security patches applied to WordPress installations that I don't want to lose and re-apply manually.

Has anyone seen a stable build number that definitively fixes these GUI rendering and reporting issues? Or should we still wait for an official patch?

Thanks in advance for your real-world feedback.