CWP 1.5 / cwpsrv-1.24.0-2 update: Are GUI modules -ModSec, Firewall, Yum, New Ba

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.

Hello xWeb,

I have two production servers running under AlmaLinux (EL9 environment). I took the risk and updated them straight to CWPpro version 1.6 to verify if the critical frontend bugs introduced in the previous cwpsrv-1.24.0-2 build were finally addressed.

After running deep diagnostics both via web and terminal commands, here are the real-world results point by point:

1. ModSecurity Manager (STILL BROKEN)
Even though the backend engine is up and running perfectly on the Apache/Nginx environment (actively intercepting real-time exploits as verified in modsec_audit.log), the CWP GUI framework is completely broken. It stays trapped in an infinite loop showing the "Starting module" spinner indefinitely.

2. Firewall Manager (PARTIALLY SOLVED / INTERFACE CONFLICT)
The old navigation paths from the left sidebar are experiencing severe issues and mismatches:
* Menu > CSF Firewall (csf) | No changes (remains legacy).
* Menu > Firewall Manager (firewallv2) | Displays the new interface. It is safe to assume this modern UI will replace the older version.
* Menu > Mod Security (mod_security) | The interface does not load. Furthermore, a severe JavaScript/jQuery conflict exists within this section: once loaded, it completely freezes the interactivity of the left navigation menu, forcing you to reload the main Dashboard page to recover control of the panel.
* Dashboard > Firewall Shield Icon (firewall) | Launches the traditional "Firewall Manager" interface. This classic UI seems to be deprecated and currently being replaced by the new firewallv2.

3. Yum Manager (FIXED)
This module is finally working flawlessly. It no longer gets stuck on "checking for updates" nor returns 404 errors. It properly syncs with the OS package manager in the background and displays the green "All packages are up to date!" badge accurately, mirroring terminal updates.

4. New Backup Module Email Reports (STILL BROKEN)
Your complaint regarding the email alert logs is 100% accurate. Checking the backend log files (/var/log/cwp/cwp_backup.log), CWP only prints a raw execution timestamp line (e.g., Thu Jul 30 03:48:11 -03 2026). It completely lacks any granular details regarding local/remote delivery, individual account success status, or secondary domain metrics. This makes the email notifications completely vague.

5. Final Verdict / Recommendation
If you heavily rely on a working ModSecurity GUI or pristine backup report insights, do not update your production environment yet. Stay on your current stable version and wait for a cleaner release. While the underlying backend services (CSF, Apache, and ModSec rules) remain completely solid and secure, the frontend template engine in CWP 1.6 still carries multiple unresolved script overlaps.

Hope this field feedback helps the community make an informed decision!

Thanks for the update, NAZA. I've turned off auto-updates in the meantime. Lately, we've been having continuous issues with every upgrade. Let's see if the upcoming patches resolve them. The dev team confirmed these are known issues and are being fixed. We really need a hotfix as soon as possible, as time is critical for us.