CWP 1.6 update from 1.4: ModSec, Firewall, Yum, New Ba

Hello community,

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.

Hi All,

I have some additional issues that I came across with this latest update...  Is anyone else seeing these?

1) CWP-CWP migration stopped working.... Now only the packages are listed but no user accounts.

2) Newbackups: Full backup over ssh to remote server fails due to tmp directory filling up.  The lock file mechanism does not clear out the directory as it creates the compressed files and so the server runs out of space.

The backup issues started in June with the major problems experienced at that time...

Anyone experiencing these?

Thanks

there are a few other things i can see on mine, maybe someone can confirm.

- Security Center also still has the spinning circle
- unable to create new subdomains, maybe i am dumb, but no chance what subdomain or path i enter, since the update i always get invalid subdomain. (maybe it has to do with the new file manager, maybe there is some check or something)

Can anyone confirm this, is it just me?

And just to mention, this not just started with 1.6, this all started with 1.4

Hello community,

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:

.....

Thanks for the Update.