Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Updates / CWP 1.7 – What has actually been fixed? Community feedback
« on: August 06, 2026, 09:44:28 PM »
Now that we've reached CWP 1.7, I'd like to understand the current state of the platform and compare experiences with other administrators.
After the silent transition from 0.9.8.12.44 to the new 1.x series, I experienced several issues that mainly affected the new UI. Looking through the forum, it seems I was not the only one.
These are the issues I have personally encountered:
- YUM Manager inaccessible or stuck.
- ModSecurity management not working from the UI.
- Firewall management issues.
- PHP Selector not working correctly.
- New Backup module (still marked as Beta) with poor email reporting:
- notifications often don't specify whether the backup was local or remote;
- there is no clear summary of which accounts completed successfully and which failed;
- overall reporting is not sufficient for production environments.
- SSL certificate generation/management issues.
- Occasional problems with Roundcube.
The good news is that, on my servers, the backend itself has remained functional. Most operations continue to work correctly from the command line, which suggests that many of the regressions are related to the new UI rather than the underlying services.
What concerns me most is not a single bug, but the impact these updates had on production environments. A control panel used to manage production servers should prioritize stability and reliability. Releasing updates that introduce regressions into core administrative functions creates unnecessary operational risks, especially for administrators managing multiple servers.
Now that several updates have already been released and we're at version 1.7, I'd like to hear from other users.
- Which issues have actually been resolved?
- Which problems are you still experiencing?
- Is 1.7 stable enough for daily production use?
- Have you found any new regressions that haven't yet been discussed?
- Has the new Backup module become reliable, or are there still significant limitations?
I'm not interested in starting a complaint thread. My goal is to build an accurate picture of the current state of CWP 1.7 so that administrators can make informed decisions and developers can better understand which areas still need attention.
I appreciate any feedback from those running CWP in real production environments.
After the silent transition from 0.9.8.12.44 to the new 1.x series, I experienced several issues that mainly affected the new UI. Looking through the forum, it seems I was not the only one.
These are the issues I have personally encountered:
- YUM Manager inaccessible or stuck.
- ModSecurity management not working from the UI.
- Firewall management issues.
- PHP Selector not working correctly.
- New Backup module (still marked as Beta) with poor email reporting:
- notifications often don't specify whether the backup was local or remote;
- there is no clear summary of which accounts completed successfully and which failed;
- overall reporting is not sufficient for production environments.
- SSL certificate generation/management issues.
- Occasional problems with Roundcube.
The good news is that, on my servers, the backend itself has remained functional. Most operations continue to work correctly from the command line, which suggests that many of the regressions are related to the new UI rather than the underlying services.
What concerns me most is not a single bug, but the impact these updates had on production environments. A control panel used to manage production servers should prioritize stability and reliability. Releasing updates that introduce regressions into core administrative functions creates unnecessary operational risks, especially for administrators managing multiple servers.
Now that several updates have already been released and we're at version 1.7, I'd like to hear from other users.
- Which issues have actually been resolved?
- Which problems are you still experiencing?
- Is 1.7 stable enough for daily production use?
- Have you found any new regressions that haven't yet been discussed?
- Has the new Backup module become reliable, or are there still significant limitations?
I'm not interested in starting a complaint thread. My goal is to build an accurate picture of the current state of CWP 1.7 so that administrators can make informed decisions and developers can better understand which areas still need attention.
I appreciate any feedback from those running CWP in real production environments.
2
Updates / CWP 1.5 / cwpsrv-1.24.0-2 update: Are GUI modules -ModSec, Firewall, Yum, New Ba
« on: July 30, 2026, 10:05:52 PM »
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.
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.
3
Backup / NEW Backup: Still in Perpetual Beta? Critical Issues Unresolved for Months (CWP7
« on: July 13, 2026, 12:26:05 PM »
Hello everyone,
I am a CWP7 Pro user, and I would like to publicly raise an issue that I now consider unacceptable.
For months, I have been reporting problems with the NEW Backup module through the official ticket system, but I have received little to no meaningful response. My support tickets often remain unanswered for more than 15 days, which is simply not the level of support I expect from a Pro service.
The main issue is that the NEW Backup module does not send backup notification emails reliably. On the rare occasions when an email is actually sent, it does not indicate whether it refers to a local backup or a remote backup, nor does it specify which backup jobs completed successfully and which failed.
A backup system should not send a generic "backup completed" email. It should provide a detailed report that clearly identifies the backup type, destination, and the success or failure of every backup task. This is not an optional feature—it is a fundamental requirement for any professional backup solution.
Unfortunately, this is not an isolated incident. In the past, we have already experienced situations where software updates broke the backup module completely, making backups impossible to perform. These issues were caused by the software itself, not by server administrators.
At this point, I respectfully ask the development team to treat these problems as a high priority instead of leaving the NEW Backup module in what increasingly feels like a permanent beta state.
I am posting this here because the official support channel has not provided acceptable response times or meaningful updates regarding these issues. I sincerely hope this post receives the attention it deserves and that the development team can provide concrete information about when these long-standing problems will finally be resolved.
Thank you for taking the time to read this, and I would also appreciate hearing from other CWP users who may have experienced similar issues.
Best regards to everyone in the forum.
I am a CWP7 Pro user, and I would like to publicly raise an issue that I now consider unacceptable.
For months, I have been reporting problems with the NEW Backup module through the official ticket system, but I have received little to no meaningful response. My support tickets often remain unanswered for more than 15 days, which is simply not the level of support I expect from a Pro service.
The main issue is that the NEW Backup module does not send backup notification emails reliably. On the rare occasions when an email is actually sent, it does not indicate whether it refers to a local backup or a remote backup, nor does it specify which backup jobs completed successfully and which failed.
A backup system should not send a generic "backup completed" email. It should provide a detailed report that clearly identifies the backup type, destination, and the success or failure of every backup task. This is not an optional feature—it is a fundamental requirement for any professional backup solution.
Unfortunately, this is not an isolated incident. In the past, we have already experienced situations where software updates broke the backup module completely, making backups impossible to perform. These issues were caused by the software itself, not by server administrators.
At this point, I respectfully ask the development team to treat these problems as a high priority instead of leaving the NEW Backup module in what increasingly feels like a permanent beta state.
I am posting this here because the official support channel has not provided acceptable response times or meaningful updates regarding these issues. I sincerely hope this post receives the attention it deserves and that the development team can provide concrete information about when these long-standing problems will finally be resolved.
Thank you for taking the time to read this, and I would also appreciate hearing from other CWP users who may have experienced similar issues.
Best regards to everyone in the forum.
4
Backup / Critical Backup Bug After Latest Update (new backup)
« on: June 13, 2026, 10:28:05 PM »
Since the latest backup update, local backups are broken.
Backup archives are created in the temporary directory but never moved to the final backup location.
The system reports "Backup Finished" even though the process is incomplete and files remain in the temp folder.
Email notifications are also unreliable and often contain no useful information about successful or failed accounts.
This is affecting production servers and leaving systems without reliable automated backups for days.
Multiple support tickets have received no response.
Please escalate this issue to the developers urgently.
Backup archives are created in the temporary directory but never moved to the final backup location.
The system reports "Backup Finished" even though the process is incomplete and files remain in the temp folder.
Email notifications are also unreliable and often contain no useful information about successful or failed accounts.
This is affecting production servers and leaving systems without reliable automated backups for days.
Multiple support tickets have received no response.
Please escalate this issue to the developers urgently.
Pages: [1]
