Recent Posts
1
Addons / Re: Change user password via API
« Last post by André Bastos on Today at 04:39:25 PM »I want to write API function for change user password.
I see php files are encrypted so I do not know how start with it.
Any help ?
Update the API details: IP, key, and username/password
Code: [Select]
API_IP=
API_KEY=
API_URL_ACCOUNT="https://${API_IP}:2304/v1/account"
API_URL_CHANGEPASS="https://${API_IP}:2304/v1/changepass"
USERNAME=
NEW_PASSWORD=
API_RESPONSE=$(curl -k -s -X POST "$API_URL_CHANGEPASS" \
-F "key=$API_KEY" \
-F "action=update" \
-F "user=$USERNAME" \
-F "pass=$NEW_PASSWORD")
if [ -z "$API_RESPONSE" ]; then
echo -e "erroR"
else
echo -e "$API_RESPONSE"
fi
2
Installation / Re: CWP Fresh install on Almalinux 9 Error root login
« Last post by Starburst on Today at 11:37:02 AM »Try this:
Change to:
Then change the root password using the passwd command
Something with just lower & upper case letters and Numbers.
(You can always change it later)
You might also have to clear you browser of cookies & cache.
Code: [Select]
nano /etc/login.defsChange to:
Quote
SHA_CRYPT_MAX_ROUNDS 5000
Then change the root password using the passwd command
Something with just lower & upper case letters and Numbers.
(You can always change it later)
You might also have to clear you browser of cookies & cache.
3
Softaculous / She's real, she's close, she's yours
« Last post by mjventas on Today at 04:10:19 AM »4
Updates / Re: CWP7: 0.9.8.1230
« Last post by jlout on July 13, 2026, 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.
5
Installation / Re: CWP Fresh install on Almalinux 9 Error root login
« Last post by overseer on July 13, 2026, 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.
6
Installation / Re: CWP Fresh install on Almalinux 9 Error root login
« Last post by uma on July 13, 2026, 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.
7
Backup / NEW Backup: Still in Perpetual Beta? Critical Issues Unresolved for Months (CWP7
« Last post by Xweb 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.
8
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 )
9
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
10
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.