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 12, 2026, 08:08:10 PM »Dollars to Doughnuts -- I think this page says it all:
https://webuzo.com/pricing
Given the tiered pricing based on # of user accounts, I couldn't afford to do it on my servers -- except perhaps on one server that is essentially a dedicated server to one client. Effectively, Webuzo would be 10x-12x more expensive than CWP for me.
It is worth remembering that, despite the price, there is genuine, ongoing development work behind the scenes; Webuzo responds to most requests in under two hours, compared to 48–72 hours for CWP. Fixes are applied almost within the hour following official releases.
You shouldn't compare it to CWP; Webuzo has over 66 employees dedicated to keeping more than 15 different scripts up to date.
I will return to CWP once it becomes stable again.
2
Information / Re: CWP 1.8 is out, and has options for PHP 8.4 & 8.5
« on: August 12, 2026, 11:57:24 AM »I think it's fair for someone to suggest another panel given the list of needs and wants above.
It has never been in the DNA of CWP to provide that level of documentation and service and if that is hugely important to you there is only 1 panel you're ever going to get that from. CWP comes with some gold & some challenges, it has always required some admin skills to keep it honest but is also super easy on the bank balance.
@6Sense
That's pretty much where I ended up as well.
I moved to Webuzo Business Edition in February this year, and in roughly four months I've migrated my entire fleet over to it.
I also went with dedicated DNS servers in geographically separate locations. Yes, the additional DNS setup/licensing costs extra, but honestly, it was worth every penny.
And I have to say, I'm genuinely impressed with Webuzo.
The thing that surprised me most wasn't just the feature list. It's the overall experience of running it. The updates, documentation, current software stack, and the way everything fits together have made my day-to-day administration considerably easier.
And the support has been a huge part of that. Every time I've contacted support, I got a response. That's a pretty basic expectation when you're paying for a product, but after my previous experience, I really appreciate it.
CWP gave me a lot for the money, and I won't deny that. But after running production infrastructure on it for years, I eventually got tired of constantly having to fill gaps myself, work around things, or wait for the panel to catch up.
With Webuzo, I've spent the last four months doing the opposite: migrating everything and actually getting on with running the infrastructure.
I'm not saying Webuzo is perfect or that everyone should switch. But for my requirements, this has been a massive improvement.
The extra licensing cost including the separate DNS licenses is insignificant compared with the amount of admin time and headache I've saved.
Four months, entire fleet migrated, dedicated geographically distributed DNS, responsive support and I genuinely don't regret the decision.
This thing is amazing.
I’m also starting to migrate to Webuzo; I’m giving CWP another two weeks to fix the issues with the internal backup and restore system. If nothing is done by then, I’ll migrate everything to Webuzo.
3
Information / Re: CWP 1.8 is out, and has options for PHP 8.4 & 8.5
« on: August 12, 2026, 11:52:23 AM »@cgauthey
Sounds like you would be happier with another control panel then...
Show me 1 that does every one on your 2 posts.
But CWP does do things mentioned on your list.
You still have to be a sys admin to know how to work the admin panel and CLI to enable them.
Requests regarding backups and restores that fail to start due to a system file misconfiguration represent an absolute emergency that needed to be resolved; yet, two months after the issue was reported to José—and despite follow-ups involving a backup and control panel access—it still hasn't been fixed. Furthermore, SFTP and FTP services have been down for months, constantly returning error messages even though the login credentials are correct.
I'm sorry, but a backup system is the foundation of everything; restoring is not possible because the restore file points to:
I've currently performed a restore for the financet account, but it seems to be stuck on:
2026-06-22 09:56:45 UPDATE restore SET ST='20260622155645' WHERE ST='1'
2026-06-22 09:56:45 >>>>>>>>> [1,1,1,1,1,1,1,1,1,1,1,financet,2026-06-20_20-13-41,0,,1,1,1,1,1]
2026-06-22 09:56:45 Detecting files
See the logs; I don't know why it's not detecting and starting the account restore on June 20th.
There seems to be a problem.
4
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.**
5
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.**
6
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
7
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.
8
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.
9
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.
10
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!
11
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.
12
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?
13
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.
14
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.
15
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?
