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.
1
Information / Re: CWP 1.8 is out, and has options for PHP 8.4 & 8.5
« on: August 11, 2026, 01:04:56 PM »
## And there is another much more critical issue: backup and restore
It is impossible to seriously discuss a control panel designed for professional hosting without discussing **backup and restore**.
And on this subject, the situation is particularly concerning.
CWP's backup and restore system has been experiencing issues for months, and these problems have been reported repeatedly by users.
The problem is not simply that a bug exists.
**Bugs happen.**
What is concerning is when an issue affects such a critical feature as backup and restore, is reported repeatedly, and yet it appears that the underlying problem is never truly reviewed and reworked in depth.
A backup that works is important.
But a backup where **the restore process does not work reliably is not a real backup solution.**
When an administrator discovers that an account, database or files cannot be properly restored after months of reported issues, that becomes extremely concerning.
Backup and restore is not a secondary feature.
It is a **fundamental security and business continuity function** for any hosting environment.
At this point, what may be needed is not simply another series of small bug fixes.
The backup and restore architecture may need to be **properly reviewed and reworked**, with genuine restoration testing and a serious review of the issues repeatedly reported by the community.
Because ultimately, a hosting provider cannot afford to discover when disaster actually happens:
> **"The backup exists, but the restore doesn't work as expected."**
This is exactly where trust in a control panel is won or lost.
And this is why the community is asking for more than just a list of new features.
**We need the fundamental features to be reliable before continuously adding new ones.**
PHP 8.4 and 8.5 are important.
New technologies are important.
But **reliable backups, reliable restoration and overall system stability are even more important.**
It is impossible to seriously discuss a control panel designed for professional hosting without discussing **backup and restore**.
And on this subject, the situation is particularly concerning.
CWP's backup and restore system has been experiencing issues for months, and these problems have been reported repeatedly by users.
The problem is not simply that a bug exists.
**Bugs happen.**
What is concerning is when an issue affects such a critical feature as backup and restore, is reported repeatedly, and yet it appears that the underlying problem is never truly reviewed and reworked in depth.
A backup that works is important.
But a backup where **the restore process does not work reliably is not a real backup solution.**
When an administrator discovers that an account, database or files cannot be properly restored after months of reported issues, that becomes extremely concerning.
Backup and restore is not a secondary feature.
It is a **fundamental security and business continuity function** for any hosting environment.
At this point, what may be needed is not simply another series of small bug fixes.
The backup and restore architecture may need to be **properly reviewed and reworked**, with genuine restoration testing and a serious review of the issues repeatedly reported by the community.
Because ultimately, a hosting provider cannot afford to discover when disaster actually happens:
> **"The backup exists, but the restore doesn't work as expected."**
This is exactly where trust in a control panel is won or lost.
And this is why the community is asking for more than just a list of new features.
**We need the fundamental features to be reliable before continuously adding new ones.**
PHP 8.4 and 8.5 are important.
New technologies are important.
But **reliable backups, reliable restoration and overall system stability are even more important.**
2
Information / Re: CWP 1.8 is out, and has options for PHP 8.4 & 8.5
« on: August 11, 2026, 01:00:04 PM »
# CWP 1.8: Finally PHP 8.4 and 8.5… but where is CWP really going?
Let's be honest: **seeing PHP 8.4 and PHP 8.5 finally becoming available in CWP 1.8 is good news.**
But is this really a major step forward in 2026?
PHP 8.4 was released in **November 2024**.
PHP 8.5 was released in **November 2025**.
We are now in **August 2026**.
That means CWP is roughly **21 months behind PHP 8.4 and 9 months behind PHP 8.5**.
This is not an unfair criticism. It is simply a fact.
And that fact should make the CWP community ask some serious questions.
---
## The problem is no longer just PHP
For a long time, a certain amount of delay could be considered acceptable.
But today, the gap seems to affect much more of the CWP ecosystem.
Administrators are waiting for answers regarding:
* new PHP versions;
* modern operating systems;
* modern web technologies;
* newer Apache and Nginx versions;
* HTTP/2 and HTTP/3;
* modern security technologies;
* virtualization technologies;
* performance improvements;
* backup solutions;
* integration with modern security products;
* and, most importantly, CWP's overall strategy.
The problem is that **we don't really know where CWP is going.**
And that may be the biggest problem of all.
---
# Where is the roadmap?
This is the question many administrators are asking.
**What is CWP's official roadmap for the next 12, 24 or 36 months?**
Which technologies are priorities?
Which operating systems will be supported?
When can we expect major releases?
Which features are actually being developed?
What has been abandoned?
What is simply delayed?
Today, getting clear answers to these questions is far too difficult.
And for administrators running production infrastructure, **uncertainty is a problem.**
We cannot build professional hosting infrastructure based on the hope that a feature will eventually arrive.
---
# The changelog needs to change
A changelog is one of the most important communication tools a development team has.
Yet CWP's changelog too often fails to provide a clear picture of the actual evolution of the product.
An administrator should be able to open the changelog and immediately understand:
**"This is what was developed. This is what is coming. This is what is planned. This is what has been fixed."**
That is not an unreasonable request.
It is basic communication for software that is used in production environments.
---
# Competition is moving forward
While CWP continues at its current pace, **other control panels are continuing to evolve.**
Modern technologies are released rapidly.
PHP versions move forward.
Linux distributions evolve.
Security requirements become increasingly demanding.
Hosting providers have to keep up.
And when a control panel falls too far behind, administrators naturally start looking elsewhere.
Not necessarily because competitors are better at everything.
Sometimes simply because they provide a stronger impression of **active development and a clear direction.**
---
# CWP still has something extremely valuable
And this is exactly why this discussion matters.
**CWP has a community.**
There are thousands of administrators who know the platform extremely well, have been using it for years, and would actually prefer to continue using it.
But that community needs to know that CWP has **a vision for the future.**
We are not asking for every feature to be released tomorrow.
We are asking for something much simpler:
### Give us a direction.
Tell us what is coming.
Tell us what is being developed.
Tell us what is delayed.
Tell us what is not planned.
And most importantly, **communicate regularly.**
---
# PHP 8.4 and 8.5 should be a beginning, not a destination
To be clear:
**Congratulations on CWP 1.8 and the addition of PHP 8.4 / 8.5.**
This is a positive step.
But it should not be considered the end of the problem.
It should be **the beginning of a new development cycle for CWP.**
A cycle with:
* more regular releases;
* a properly maintained changelog;
* a public roadmap;
* better communication;
* faster adoption of current technologies;
* a clear strategy for modern operating systems;
* and a long-term vision.
---
# The real question
So the question is not:
**"Does CWP 1.8 finally support PHP 8.4 and 8.5?"**
The real question is:
## "Will CWP remain technologically relevant over the next 3, 5 or 10 years?"
Because a hosting control panel cannot simply catch up with technologies months after they are released.
It needs to be able to **anticipate them.**
CWP still has a place in the hosting industry.
CWP still has a community.
CWP still has many loyal users.
But that loyalty should never be taken for granted.
**We want to continue using CWP.**
But for that to happen, we need to see that CWP genuinely wants to keep moving forward.
### PHP 8.4 and 8.5 are welcome.
**Now show us what comes next.**
Let's be honest: **seeing PHP 8.4 and PHP 8.5 finally becoming available in CWP 1.8 is good news.**
But is this really a major step forward in 2026?
PHP 8.4 was released in **November 2024**.
PHP 8.5 was released in **November 2025**.
We are now in **August 2026**.
That means CWP is roughly **21 months behind PHP 8.4 and 9 months behind PHP 8.5**.
This is not an unfair criticism. It is simply a fact.
And that fact should make the CWP community ask some serious questions.
---
## The problem is no longer just PHP
For a long time, a certain amount of delay could be considered acceptable.
But today, the gap seems to affect much more of the CWP ecosystem.
Administrators are waiting for answers regarding:
* new PHP versions;
* modern operating systems;
* modern web technologies;
* newer Apache and Nginx versions;
* HTTP/2 and HTTP/3;
* modern security technologies;
* virtualization technologies;
* performance improvements;
* backup solutions;
* integration with modern security products;
* and, most importantly, CWP's overall strategy.
The problem is that **we don't really know where CWP is going.**
And that may be the biggest problem of all.
---
# Where is the roadmap?
This is the question many administrators are asking.
**What is CWP's official roadmap for the next 12, 24 or 36 months?**
Which technologies are priorities?
Which operating systems will be supported?
When can we expect major releases?
Which features are actually being developed?
What has been abandoned?
What is simply delayed?
Today, getting clear answers to these questions is far too difficult.
And for administrators running production infrastructure, **uncertainty is a problem.**
We cannot build professional hosting infrastructure based on the hope that a feature will eventually arrive.
---
# The changelog needs to change
A changelog is one of the most important communication tools a development team has.
Yet CWP's changelog too often fails to provide a clear picture of the actual evolution of the product.
An administrator should be able to open the changelog and immediately understand:
**"This is what was developed. This is what is coming. This is what is planned. This is what has been fixed."**
That is not an unreasonable request.
It is basic communication for software that is used in production environments.
---
# Competition is moving forward
While CWP continues at its current pace, **other control panels are continuing to evolve.**
Modern technologies are released rapidly.
PHP versions move forward.
Linux distributions evolve.
Security requirements become increasingly demanding.
Hosting providers have to keep up.
And when a control panel falls too far behind, administrators naturally start looking elsewhere.
Not necessarily because competitors are better at everything.
Sometimes simply because they provide a stronger impression of **active development and a clear direction.**
---
# CWP still has something extremely valuable
And this is exactly why this discussion matters.
**CWP has a community.**
There are thousands of administrators who know the platform extremely well, have been using it for years, and would actually prefer to continue using it.
But that community needs to know that CWP has **a vision for the future.**
We are not asking for every feature to be released tomorrow.
We are asking for something much simpler:
### Give us a direction.
Tell us what is coming.
Tell us what is being developed.
Tell us what is delayed.
Tell us what is not planned.
And most importantly, **communicate regularly.**
---
# PHP 8.4 and 8.5 should be a beginning, not a destination
To be clear:
**Congratulations on CWP 1.8 and the addition of PHP 8.4 / 8.5.**
This is a positive step.
But it should not be considered the end of the problem.
It should be **the beginning of a new development cycle for CWP.**
A cycle with:
* more regular releases;
* a properly maintained changelog;
* a public roadmap;
* better communication;
* faster adoption of current technologies;
* a clear strategy for modern operating systems;
* and a long-term vision.
---
# The real question
So the question is not:
**"Does CWP 1.8 finally support PHP 8.4 and 8.5?"**
The real question is:
## "Will CWP remain technologically relevant over the next 3, 5 or 10 years?"
Because a hosting control panel cannot simply catch up with technologies months after they are released.
It needs to be able to **anticipate them.**
CWP still has a place in the hosting industry.
CWP still has a community.
CWP still has many loyal users.
But that loyalty should never be taken for granted.
**We want to continue using CWP.**
But for that to happen, we need to see that CWP genuinely wants to keep moving forward.
### PHP 8.4 and 8.5 are welcome.
**Now show us what comes next.**
3
Information / Re: CWP: What is the future of the project? Is it still the right choice?
« on: August 02, 2026, 07:47:29 PM »
Please, it is very important to fix the backup system, which has been preventing any account restoration for weeks.
The system remains stuck at 2026-07-28 07:09:17 >>>>>>>>> [1,1,1,1,1,1,1,1,1,grizzy,2026-07-17_16-32-49,0,,1,1,1,1,1]
2026-07-28 07:09:17 Detecting files
2026-07-31 03:28:47 UPDATE restore SET ST='20260731092847' WHERE ST='1'
2026-07-31 03:28:47 >>>>>>>>> [1,1,1,1,1,1,1,1,1,grizzy,2026-07-25_23-40-04,0,,1,1,1,1,1]
2026-07-31 03:28:47 Detecting files
We keep getting the message
Something went wrong
Login Failed: Warning: Permanently added xxxxxxxxxxxxxxxxxxx' (ECDSA) to the list of known hosts. Permission denied, please try again. Received disconnect from xx.xxx.xxx.xx port xx:x: too many authentication failures Disconnected from xx.xxx.xxx.xx port xx:x
The system remains stuck at 2026-07-28 07:09:17 >>>>>>>>> [1,1,1,1,1,1,1,1,1,grizzy,2026-07-17_16-32-49,0,,1,1,1,1,1]
2026-07-28 07:09:17 Detecting files
2026-07-31 03:28:47 UPDATE restore SET ST='20260731092847' WHERE ST='1'
2026-07-31 03:28:47 >>>>>>>>> [1,1,1,1,1,1,1,1,1,grizzy,2026-07-25_23-40-04,0,,1,1,1,1,1]
2026-07-31 03:28:47 Detecting files
We keep getting the message
Something went wrong
Login Failed: Warning: Permanently added xxxxxxxxxxxxxxxxxxx' (ECDSA) to the list of known hosts. Permission denied, please try again. Received disconnect from xx.xxx.xxx.xx port xx:x: too many authentication failures Disconnected from xx.xxx.xxx.xx port xx:x
4
Updates / 1.07 update
« on: August 02, 2026, 07:38:32 PM »
Hello, version 1.07 fixes numerous bugs—notably regarding ModSecurity, which now opens correctly again—and allows for the installation of PHP updates that previously failed.
The fille manager has also been updated to a cleaner version.
The fille manager has also been updated to a cleaner version.
5
Updates / Re: The version stays at 1.6
« on: August 02, 2026, 07:36:44 PM »No, version 1.07 exists;
it fixes ModSecurity, among other things, and has breathed new life into the FTP manager.
6
CentOS-WebPanel Bugs / Re: Bug in new CWP Update: Yum Manager stuck on "Checking for updates..." due to 404
« on: July 30, 2026, 09:34:30 PM »
Hello, the firewall is working; you need to use firewallv2. They’ve revamped the presentation—it looks great and is much better.
7
I can build it / Re: Want to hire a sysadmin
« on: July 29, 2026, 06:40:26 AM »
I use 24server management for my server; they respond in just a few minutes and fix things and do everything for you. https://24x7servermanagement.com/centos-server-management/
The best!
The best!
8
CentOS-WebPanel Bugs / Re: Bug in new CWP Update: Yum Manager stuck on "Checking for updates..." due to 404
« on: July 29, 2026, 06:28:09 AM »
I contacted José on Telegram; I think he should see the message and step in quickly.
9
Updates / Re: cwp service failed
« on: July 28, 2026, 11:14:35 AM »I'm getting the error: "The module firewallv2 does not exist."
How do I reactivate it? Do I need to restart the server?
10
Information / Re: CWP: What is the future of the project? Is it still the right choice?
« on: July 28, 2026, 08:14:46 AM »Please update to the latest version 1.2
I can't update to the latest version; it's not working.
11
Information / Re: CWP: What is the future of the project? Is it still the right choice?
« on: July 27, 2026, 08:10:23 PM »Please update to the latest version 1.2
However, the changelog still shows the version as CWP7: 0.9.8.1244.
See screenshot.
12
Information / Re: CWP: What is the future of the project? Is it still the right choice?
« on: July 27, 2026, 05:42:00 PM »
Great on the other hand we encounter a problem with the restoration a bug in the base file here is the return
We are experiencing a problem with the new local backup restore feature on our server.
The backup files are present on the server and appear to be complete and intact. However, the restore process does not start correctly.
Whenever we attempt to restore an account, the process consistently gets stuck at the "Detecting files" stage and makes no further progress.
The restore log repeatedly shows the following information:
2026-07-07 14:14:06 UPDATE restore SET ST='20260707201406' WHERE ST='1'
2026-07-07 14:14:06 >>>>>>>>> [1,1,1,1,1,1,1,1,1,grizzy,2026-06-27_17-15-04,0,,1,1,1,1,1]
2026-07-07 14:14:06 Detecting files
We have verified that the backup directory exists and that all backup archives are available.
Based on our investigation, it appears that the restore utility is generating an incorrect path and attempting to locate a non-existent backup archive, even though the backup data is available at the correct location.
Could you please check if this is a known issue with this new local backup restore feature?
We are experiencing a problem with the new local backup restore feature on our server.
The backup files are present on the server and appear to be complete and intact. However, the restore process does not start correctly.
Whenever we attempt to restore an account, the process consistently gets stuck at the "Detecting files" stage and makes no further progress.
The restore log repeatedly shows the following information:
2026-07-07 14:14:06 UPDATE restore SET ST='20260707201406' WHERE ST='1'
2026-07-07 14:14:06 >>>>>>>>> [1,1,1,1,1,1,1,1,1,grizzy,2026-06-27_17-15-04,0,,1,1,1,1,1]
2026-07-07 14:14:06 Detecting files
We have verified that the backup directory exists and that all backup archives are available.
Based on our investigation, it appears that the restore utility is generating an incorrect path and attempting to locate a non-existent backup archive, even though the backup data is available at the correct location.
Could you please check if this is a known issue with this new local backup restore feature?
13
Information / Re: CWP: What is the future of the project? Is it still the right choice?
« on: July 27, 2026, 05:08:01 PM »
It’s great to hear back from José; it’s nice to see he took the time to reply and that we now know more about what’s coming next.
And what about PHP versions 8.4, 8.5, and 8.6? Are those a priority too? The current versions will be obsolete soon.
as a loyal CWP user, I would like to have access to the various beta versions.
And what about PHP versions 8.4, 8.5, and 8.6? Are those a priority too? The current versions will be obsolete soon.
as a loyal CWP user, I would like to have access to the various beta versions.
14
Updates / CWP7 Version 1.2
« on: July 27, 2026, 11:34:22 AM »
The numbering has undergone a major change—is this the start of a new era?
Version 1.2 (released 27/07/2026)
Admin Panel
FIXED ADMIN UPDATED
– Improved security for login and session
– Improved security on file system functions
– Improved security for API
– New script for cleaning server logs /scripts/clean_logs
– New script for checking disk quota status /scripts/quota_check_status
Version 1.2 (released 27/07/2026)
Admin Panel
FIXED ADMIN UPDATED
– Improved security for login and session
– Improved security on file system functions
– Improved security for API
– New script for cleaning server logs /scripts/clean_logs
– New script for checking disk quota status /scripts/quota_check_status
15
Information / CWP: What is the future of the project? Is it still the right choice?
« on: July 27, 2026, 08:42:17 AM »Hello everyone,
I have been using CWP Pro for several years, and overall it has served me well. However, over the past year I have become increasingly concerned about the future of the project, and I would really like to hear the opinions of other users.
As a system administrator, I need a control panel that is actively maintained, secure, and able to keep pace with modern hosting requirements. Unfortunately, I have the feeling that CWP is falling further behind compared to other control panels.
Some of my main concerns are:
New PHP versions seem to take a long time before becoming available.
Some updates appear to fix issues but also introduce new bugs or regressions.
The backup and restore system has caused me several problems. In my opinion, backups are one of the most critical features of any hosting panel, and reliability is absolutely essential.
Development seems slower than it used to be, and new features are released less frequently.
Communication regarding the project's roadmap and future plans is quite limited.
Technical support has also become a concern for me. Although I pay for a support plan, I have experienced response times of 5 to 10 days for some tickets. For production servers, such delays can be difficult to accept when an issue requires prompt attention.
This leads me to a simple question:
What is the long-term vision for CWP?
Many competing panels such as Webuzo, DirectAdmin, and Plesk seem to be evolving much faster, with quicker PHP support, frequent updates, and more modern backup solutions.
I am not trying to criticize CWP or start an argument. I genuinely want to understand whether other administrators share the same concerns or if my experience is unusual.
I would really appreciate hearing your thoughts:
Are you still confident in CWP's future?
Do you trust it for production environments?
Have you experienced issues with backups or restore operations?
How has your experience with technical support been?
Are you satisfied with the current development pace?
Are you planning to stay with CWP, or are you considering moving to another control panel?
Personally, I am at an important decision point. I am preparing to deploy a new production server and must decide whether to continue investing in the CWP ecosystem or migrate to another platform.
I sincerely hope CWP continues to grow and improve because it has many strengths. However, I believe the project needs to demonstrate a stronger development roadmap, faster adoption of new technologies, more reliable backup and restore features, and more responsive technical support if it wants to remain competitive in today's hosting market.
I look forward to reading your experiences and opinions.
Thank you.
