Recent Posts
31
CentOS 8 Problems / Fresh Alma 8 Install CWPRO Cannot Upgrade or Install any php-fpm
« Last post by Reikor on July 31, 2026, 10:58:25 AM »I just installed a new cwpro activated pro and now i cannot install any phpfpm version.
Also PHP version Switcher doesnt work.
Also PHP version Switcher doesnt work.
32
CentOS 8 Problems / Re: Fresh install on AlmaLinux 8 does not install mod_security2
« Last post by Reikor on July 31, 2026, 10:52:17 AM »Same problem here, just installed a cwpro and no modsecurity.
Need some fix.
Need some fix.
33
CentOS-WebPanel Bugs / Re: Bug in new CWP Update: Yum Manager stuck on "Checking for updates..." due to 404
« Last post by sneakybear on July 31, 2026, 08:47:52 AM »Update: So after a fresh update to 1.6 the Yum Manager has now successfully loaded. But we are still having issues with the ModSecurity module, stuck on loading.
34
Updates / Re: Alma 9 / 1.3 Update
« Last post by zakrpa on July 31, 2026, 07:32:28 AM »My server now its working.
Just php select module is not working, it stays loading when you select manage options
Aby ideas??
did you try this and? fixed most of problems on my test server including php compile module.
Code: [Select]
# 1. Temporarily remove the immutable flag on the design directory
chattr -i /usr/local/cwpsrv/htdocs/admin/design
# 2. Create the missing directory path
mkdir -p /usr/local/cwpsrv/htdocs/admin/design/charts/sparklines
# 3. Symlink the existing plugin file to the expected path
ln -s /usr/local/cwpsrv/htdocs/admin/design/plugins/charts/sparkline/jquery.sparkline.js /usr/local/cwpsrv/htdocs/admin/design/charts/sparklines/jquery.sparkline.js
# 4. Re-enable immutable flag to protect the directory
chattr +i /usr/local/cwpsrv/htdocs/admin/design35
Updates / CWP 1.6 update from 1.4: ModSec, Firewall, Yum, New Ba
« Last post by NAZA on July 31, 2026, 06:06:21 AM »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.
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.
36
Updates / Re: CWP 1.5 / cwpsrv-1.24.0-2 update: Are GUI modules -ModSec, Firewall, Yum, New Ba
« Last post by NAZA on July 31, 2026, 06:04:34 AM »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!
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!
37
Updates / Re: Alma 9 / 1.3 Update
« Last post by luislegacwp23 on July 31, 2026, 05:22:39 AM »My server now its working.
Just php select module is not working, it stays loading when you select manage options
Aby ideas??
Just php select module is not working, it stays loading when you select manage options
Aby ideas??
38
CentOS-WebPanel Bugs / Re: Bug in new CWP Update: Yum Manager stuck on "Checking for updates..." due to 404
« Last post by audept on July 31, 2026, 01:58:39 AM » Still looping when trying to perform the cwp update 60 1.6.
Using update from the admin (2013) display as well as /scripts/update_cwp execution.
Hanging on update server packages in the ssh cli.
Passing on status...
Using update from the admin (2013) display as well as /scripts/update_cwp execution.
Hanging on update server packages in the ssh cli.
Passing on status...
39
CentOS 8 Problems / Fresh install on AlmaLinux 8 does not install mod_security2
« Last post by adrianofnatal on July 31, 2026, 12:34:41 AM »Hi!
Made a fresh install on AlmaLinux and cannot activate mod security.
The panel show that is installed but apache failed to start with error:
httpd: Syntax error on line 512 of /usr/local/apache/conf/httpd.conf: Syntax error on line 9 of /usr/local/apache/conf.d/mod_security.conf: Cannot load modules/mod_security2.so into server: /usr/local/apache/modules/mod_security2.so: cannot open shared object file: No such file or directory
The file mod_security2.so was not found in directory /usr/local/apache/modules.
Try to rebuild apache but no success.
How can I solve this problem?
Thanks!
Hi!
Made a fresh install on AlmaLinux and cannot activate mod security.
The panel show that is installed but apache failed to start with error:
httpd: Syntax error on line 512 of /usr/local/apache/conf/httpd.conf: Syntax error on line 9 of /usr/local/apache/conf.d/mod_security.conf: Cannot load modules/mod_security2.so into server: /usr/local/apache/modules/mod_security2.so: cannot open shared object file: No such file or directory
The file mod_security2.so was not found in directory /usr/local/apache/modules.
Try to rebuild apache but no success.
How can I solve this problem?
Thanks!
Hi!
40
CentOS-WebPanel Bugs / Re: Bug in new CWP Update: Yum Manager stuck on "Checking for updates..." due to 404
« Last post by Qvant15 on July 30, 2026, 11:20:55 PM »This helped solve the problem. After applying the suggested solution, the spinner disappeared and the JS 404 error no longer occurs. Copying the `sparkline` and `sparklines` folders to the correct directory fixed the issue.
Thank you for the detailed explanation.
Thank you for the detailed explanation.
