Recent Posts
1
Updates / Re: CWP7: 0.9.8.1230
« Last post by jlout on Today at 10:20:26 PM »A solution that worked for me is to start the backup manually and as soon as the /home/tmp_bak/.backup_temp/.cwp_backup_marker file is created run "chattr +i .cwp_backup_marker" so that the file cannot be deleted.
This way the backup process will try to delete the .backup_temp folder as well as the marker file without success and then continue with the next account in line.
*(if, for some reason, you wish to delete the file you're going to have to run "chatt -i .cwp_backup_marker" and then rm it)
** this process could probably work without needing to run the backup process manually and then wait until the marker file is created, you could also run "touch /home/tmp_bak/.backup_temp/.cwp_backup_marker" and manually create the marker file. I followed the manually backup process so that i could have more control while testing if this works.
This way the backup process will try to delete the .backup_temp folder as well as the marker file without success and then continue with the next account in line.
*(if, for some reason, you wish to delete the file you're going to have to run "chatt -i .cwp_backup_marker" and then rm it)
** this process could probably work without needing to run the backup process manually and then wait until the marker file is created, you could also run "touch /home/tmp_bak/.backup_temp/.cwp_backup_marker" and manually create the marker file. I followed the manually backup process so that i could have more control while testing if this works.
2
Installation / Re: CWP Fresh install on Almalinux 9 Error root login
« Last post by overseer on Today at 02:14:59 PM »Is your data center image based on the full/DVD installer, or the minimal install? You need a full install, not minimal.
3
Installation / Re: CWP Fresh install on Almalinux 9 Error root login
« Last post by uma on Today at 01:59:39 PM »OS: AL9
/etc/login.defs already commented
#SHA_CRYPT_MAX_ROUNDS 10000
sshd config already have PermitRootLogin yes and PasswordAuthentication yes
but still I am not able to login at CWP and getting error *Login failed*
I installed AL9 from datacenter image. other server installed AL8 from data center image working fine.
any help highly appreciated. CWP and its community is amazing.
Thank you.
4
Backup / NEW Backup: Still in Perpetual Beta? Critical Issues Unresolved for Months (CWP7
« Last post by Xweb on Today at 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.
5
Other / Re: New CVEs in Linux Kernel: CVE-2026-53359, CVE-2026-46242, CVE-2026-43499
« Last post by cyberspace on July 12, 2026, 09:20:22 PM »CWP Secure Kernel is a regular linux kernel with a security addon. The security addon is Tomoyo:
https://tomoyo.sourceforge.net/
The linux kernel doesn't include the security addon Tomoyo by default. The kernel must be recompiled with the Tomoyo enabled. That is why the security enhancements don't start when you boot the server using the update kernel.
However, I think CWP Secure Kernel should protect your from such vulnerabilities. It should not allow to run suspicious executable files/binaries, etc. Anyway, it is better to get confirmation from CWP Secure Kernel developers or check the Tomoyo rules if you understand Tomoyo )
https://tomoyo.sourceforge.net/
The linux kernel doesn't include the security addon Tomoyo by default. The kernel must be recompiled with the Tomoyo enabled. That is why the security enhancements don't start when you boot the server using the update kernel.
However, I think CWP Secure Kernel should protect your from such vulnerabilities. It should not allow to run suspicious executable files/binaries, etc. Anyway, it is better to get confirmation from CWP Secure Kernel developers or check the Tomoyo rules if you understand Tomoyo )
6
Other / Re: New CVEs in Linux Kernel: CVE-2026-53359, CVE-2026-46242, CVE-2026-43499
« Last post by cgauthey on July 12, 2026, 01:54:38 PM »Distro Name: AlmaLinux release 8.10 (Cerulean Leopard)
Kernel Version: 4.18.0-553.92.1.el8_10.x86_64
Platform: x86_64
Kernel Version: 4.18.0-553.92.1.el8_10.x86_64
Platform: x86_64
7
Other / Re: New CVEs in Linux Kernel: CVE-2026-53359, CVE-2026-46242, CVE-2026-43499
« Last post by cyberspace on July 12, 2026, 10:09:48 AM »What version of OS do you use ? Alamlinux 8/9, something else ?
Run:
Run:
Code: [Select]
uname -rwhen the server is booted with secure kernel and show output.8
Other / Re: New CVEs in Linux Kernel: CVE-2026-53359, CVE-2026-46242, CVE-2026-43499
« Last post by cgauthey on July 11, 2026, 06:21:45 PM »In my case, when I update the server, it prevents startup with the CWP secure kernel.
9
Updates / Re: CWP7: 0.9.8.1230
« Last post by jlout on July 11, 2026, 08:12:22 AM »0.9.8.1244 and the problem persists.
The log clearly shows that when it begins the backup process, while reaching the end of the first one in order it will successfully move and delete the tar.gz but it will also delete the marker file inside /home/tmp_bak/.backup_temp (the default temp folder, yours may differ) which gives the following message:
"SAFE_CLEANUP_DIR: BLOCKED - no marker file in /home/tmp_bak/.backup_temp, refusing to delete."
It should be really simple to fix but i cannot see/edit the backup_cron because i believe it is encrypted.
Either way, please fix this problem. I have been watching the backup because it fills up my disk space and i have to babysit it while the backup takes place.
Thank you
The log clearly shows that when it begins the backup process, while reaching the end of the first one in order it will successfully move and delete the tar.gz but it will also delete the marker file inside /home/tmp_bak/.backup_temp (the default temp folder, yours may differ) which gives the following message:
"SAFE_CLEANUP_DIR: BLOCKED - no marker file in /home/tmp_bak/.backup_temp, refusing to delete."
It should be really simple to fix but i cannot see/edit the backup_cron because i believe it is encrypted.
Either way, please fix this problem. I have been watching the backup because it fills up my disk space and i have to babysit it while the backup takes place.
Thank you
10
Updates / Re: CWP7: 0.9.8.1243
« Last post by Reikor on July 10, 2026, 04:14:17 PM »Dev Team Member went Rogue and start Hacking CWPro servers, thats why the updates.
nop, only new hackers with AI are now attacking...but we solve them.
ok so its way worse... i get it. ill let you work, just keep in mind to drop some changelogs so we are aware of changes because some of them are messing with our works, i have to nullified your script to keep my servers working.
Also it would be good if you let us know if they are accesing trough 2087, 2083 or just simple ssh or how so we can firewall the entire server.
