Recent Posts
31
Information / Re: CWP 1.8 is out, and has options for PHP 8.4 & 8.5
« Last post by cgauthey 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.**
32
Information / CWP 1.8 is out, and has options for PHP 8.4 & 8.5
« Last post by Starburst on August 11, 2026, 08:50:48 AM »CWP 1.8 is out, and has options for PHP 8.4 & 8.5
I have not tried building 8.4 or 8.5 thru the CWP GUI, but it looks like it's on my to do list today.
I have not tried building 8.4 or 8.5 thru the CWP GUI, but it looks like it's on my to do list today.
33
CentOS-WebPanel GUI / Re: Firewall manager IP Access Control column table oversized
« Last post by Starburst on August 11, 2026, 08:49:44 AM »CSF, if you are running 15.10 has it's own GUI, look at the bottom of the left menu to find it.
34
CentOS-WebPanel GUI / Re: Firewall manager IP Access Control column table oversized
« Last post by overseer on August 11, 2026, 03:08:56 AM »A lot of the admin UI feels like it's designed for a higher resolution screen. On a smaller travel laptop I have to move the browser window off the left side of the screen and expand it horizontally to be able to access the important controls off to the far right (no horizontal scrollbar to access them).
35
CentOS-WebPanel GUI / Firewall manager IP Access Control column table oversized
« Last post by adrianofnatal on August 11, 2026, 12:47:06 AM »Hi!
In Firewall Manager, column IP Access Control, table Temporary Blocks (LFD), the delete button is overflowed, out of table borders with no horizontal scroll.
In Firewall Manager, column IP Access Control, table Temporary Blocks (LFD), the delete button is overflowed, out of table borders with no horizontal scroll.
36
Updates / Re: CWP 1.7 – What has actually been fixed? Community feedback
« Last post by Xweb on August 10, 2026, 11:37:24 AM »I think there is another aspect worth adding to this discussion, because my experience with CWP support over the last few months has made me even more concerned about the current situation.
After the changes that affected the UI on a significant number of servers, I expected at least a proper technical explanation from CWP. When an update affects core administrative functions on production systems, users need to know what actually happened, what was changed, what is still affected, and whether there are any recommended workarounds.
Instead, after opening support tickets and asking very specific questions, the answers have essentially been: please be patient, everything will be fixed in the next update.
But that does not actually answer the questions.
I have also contacted the development/support team by email at least three times regarding technical issues. These were not complaints or emotional messages; they were specific technical questions that, in my opinion, should have been relatively straightforward for the development team to address. I never received a meaningful response.
This is becoming more concerning than the individual bugs themselves.
Bugs can happen. Regressions can happen, especially when introducing a major UI or architectural change. What matters is how a company handles them afterwards.
If a production control panel breaks part of its administrative interface, I would expect at least:
* a clear explanation of what caused the problem;
* proper technical documentation;
* a list of known affected components;
* a clear indication of what has actually been fixed;
* information about remaining known issues;
* and, most importantly, some indication of whether a given release is considered safe for production.
Instead, users are increasingly being asked to simply wait for the next update without being given enough information to make an informed decision.
For me, this is directly connected to the question I raised in my original post:
**Can I safely update my production servers?**
At the moment, the answer is still unclear.
And this is particularly frustrating because I have been using CWP for many years. I did not choose CWP because I wanted a managed service. I chose it because it gave me a practical way to manage my own servers while retaining control over the underlying system.
I would genuinely prefer to see CWP recover from this situation rather than migrate to another panel. After so many years, migrating multiple production servers is not something I would do simply because of a few bugs.
But there is a point where the lack of communication becomes a technical risk in itself.
If I cannot get a clear answer about what an update changes, what has been tested, which issues are known, and whether the release is safe for production, then eventually I have to consider whether continuing to run CWP is the responsible choice.
So I would actually like to ask the CWP team something very simple:
**What is the current official position regarding CWP 1.x stability?**
Is CWP 1.7 considered production-ready for existing installations?
If so, which of the major UI regressions reported by users have actually been fixed, and where is the technical documentation describing those fixes?
And if it is not yet considered fully stable, why isn't this being communicated clearly to administrators before they update production servers?
I think these are reasonable questions, and answering them openly would probably do much more to restore confidence in CWP than simply telling users to wait for the next update.
I still hope CWP gets back to the level of stability and reliability that made many of us choose it in the first place. But at this point, we need more than promises about the next update. We need information.
And I want to be clear about one final point: **if this transparency, communication, and technical documentation do not improve, then migration will eventually become a concrete necessity rather than simply an option.**
I would genuinely prefer not to go down that road after using CWP for so many years. But running production servers requires a reasonable level of confidence in the platform and in the ability to understand and manage changes safely.
If that confidence cannot be restored through clear answers and concrete technical information, then we will have to seriously consider migrating our servers to another solution.
After the changes that affected the UI on a significant number of servers, I expected at least a proper technical explanation from CWP. When an update affects core administrative functions on production systems, users need to know what actually happened, what was changed, what is still affected, and whether there are any recommended workarounds.
Instead, after opening support tickets and asking very specific questions, the answers have essentially been: please be patient, everything will be fixed in the next update.
But that does not actually answer the questions.
I have also contacted the development/support team by email at least three times regarding technical issues. These were not complaints or emotional messages; they were specific technical questions that, in my opinion, should have been relatively straightforward for the development team to address. I never received a meaningful response.
This is becoming more concerning than the individual bugs themselves.
Bugs can happen. Regressions can happen, especially when introducing a major UI or architectural change. What matters is how a company handles them afterwards.
If a production control panel breaks part of its administrative interface, I would expect at least:
* a clear explanation of what caused the problem;
* proper technical documentation;
* a list of known affected components;
* a clear indication of what has actually been fixed;
* information about remaining known issues;
* and, most importantly, some indication of whether a given release is considered safe for production.
Instead, users are increasingly being asked to simply wait for the next update without being given enough information to make an informed decision.
For me, this is directly connected to the question I raised in my original post:
**Can I safely update my production servers?**
At the moment, the answer is still unclear.
And this is particularly frustrating because I have been using CWP for many years. I did not choose CWP because I wanted a managed service. I chose it because it gave me a practical way to manage my own servers while retaining control over the underlying system.
I would genuinely prefer to see CWP recover from this situation rather than migrate to another panel. After so many years, migrating multiple production servers is not something I would do simply because of a few bugs.
But there is a point where the lack of communication becomes a technical risk in itself.
If I cannot get a clear answer about what an update changes, what has been tested, which issues are known, and whether the release is safe for production, then eventually I have to consider whether continuing to run CWP is the responsible choice.
So I would actually like to ask the CWP team something very simple:
**What is the current official position regarding CWP 1.x stability?**
Is CWP 1.7 considered production-ready for existing installations?
If so, which of the major UI regressions reported by users have actually been fixed, and where is the technical documentation describing those fixes?
And if it is not yet considered fully stable, why isn't this being communicated clearly to administrators before they update production servers?
I think these are reasonable questions, and answering them openly would probably do much more to restore confidence in CWP than simply telling users to wait for the next update.
I still hope CWP gets back to the level of stability and reliability that made many of us choose it in the first place. But at this point, we need more than promises about the next update. We need information.
And I want to be clear about one final point: **if this transparency, communication, and technical documentation do not improve, then migration will eventually become a concrete necessity rather than simply an option.**
I would genuinely prefer not to go down that road after using CWP for so many years. But running production servers requires a reasonable level of confidence in the platform and in the ability to understand and manage changes safely.
If that confidence cannot be restored through clear answers and concrete technical information, then we will have to seriously consider migrating our servers to another solution.
37
Updates / Re: CWP 1.7 – What has actually been fixed? Community feedback
« Last post by ghoste on August 10, 2026, 08:09:45 AM »Let's look at it another way: who is CWP today as a company?
If we look at this forum, many of the pillars who used to provide active, hands-on support are no longer here; they’ve completely given up (like Sandeep B.). The administrators and management remain completely silent—offering no real communication aside from the occasional, generic sh /update_cwp. Today, the entire community relies almost exclusively on Starburst and overseer to get any real, consistent support. A software panel cannot survive on the goodwill of two community members alone.
I’ve raised this question before: are there severe financial constraints holding you back? If the current business model is unsustainable, please raise the license fee. Instead of $11, double or triple the price, but use those resources to hire dedicated support staff and active developers. We are willing to pay for a premium, reliable product, but we need to see action.
We’ve now moved to the new CWP 1.X version, but has anything actually evolved regarding the core installation process? Can the installer finally come with all core packages, repositories, and services fully up to date, using the latest secure stable versions right out of the box? Why do we still encounter outdated components, broken PHP-FPM configurations, or deprecated scripts during fresh setups? How much longer must your loyal user base wait for a truly stable, production-ready release?
Furthermore, who is actually managing the official website and documentation? Why is there zero transparency or a public roadmap regarding the changes and bug fixes being made to CWP? How many active employees does the company currently have? Is this control panel project still stable, secure, and viable for the future, especially with the shifting landscape of modern Linux distributions?
There are plenty of rising alternatives out there—KeyHelp, HestiaCP, Panelica, DirectAdmin, etc.—and many of them are moving fast. I honestly don't want to abandon CWP because I’ve been loyal to it, I know its architecture inside out, and I’ve used it for so many years. But ultimately, I might be forced to migrate all my servers, because the current lack of development, support, and transparency makes it feel like the situation has completely overwhelmed your team.
If we look at this forum, many of the pillars who used to provide active, hands-on support are no longer here; they’ve completely given up (like Sandeep B.). The administrators and management remain completely silent—offering no real communication aside from the occasional, generic sh /update_cwp. Today, the entire community relies almost exclusively on Starburst and overseer to get any real, consistent support. A software panel cannot survive on the goodwill of two community members alone.
I’ve raised this question before: are there severe financial constraints holding you back? If the current business model is unsustainable, please raise the license fee. Instead of $11, double or triple the price, but use those resources to hire dedicated support staff and active developers. We are willing to pay for a premium, reliable product, but we need to see action.
We’ve now moved to the new CWP 1.X version, but has anything actually evolved regarding the core installation process? Can the installer finally come with all core packages, repositories, and services fully up to date, using the latest secure stable versions right out of the box? Why do we still encounter outdated components, broken PHP-FPM configurations, or deprecated scripts during fresh setups? How much longer must your loyal user base wait for a truly stable, production-ready release?
Furthermore, who is actually managing the official website and documentation? Why is there zero transparency or a public roadmap regarding the changes and bug fixes being made to CWP? How many active employees does the company currently have? Is this control panel project still stable, secure, and viable for the future, especially with the shifting landscape of modern Linux distributions?
There are plenty of rising alternatives out there—KeyHelp, HestiaCP, Panelica, DirectAdmin, etc.—and many of them are moving fast. I honestly don't want to abandon CWP because I’ve been loyal to it, I know its architecture inside out, and I’ve used it for so many years. But ultimately, I might be forced to migrate all my servers, because the current lack of development, support, and transparency makes it feel like the situation has completely overwhelmed your team.
38
Backup / backup not generated
« Last post by anandmys on August 10, 2026, 07:02:56 AM »running AL8
MySQL version: 10.11.18-MariaDB
cwp 1.7
As a user, I tried generating a mysql backup by visiting Account backups
I get the message "backup succesfully generated" in green
But dont see the download option for the backup generated
MySQL version: 10.11.18-MariaDB
cwp 1.7
As a user, I tried generating a mysql backup by visiting Account backups
I get the message "backup succesfully generated" in green
But dont see the download option for the backup generated
39
Updates / Re: CWP 1.7 – What has actually been fixed? Community feedback
« Last post by Xweb on August 09, 2026, 08:45:34 PM »At this point, I think we also need to be realistic about the situation.
If these issues are not properly resolved and the CWP panel does not return to a stable and reliable state, I don't see many alternatives other than migrating to another control panel.
I have been using CWP because it was a practical and relatively stable solution for managing my servers. I would prefer to stay with CWP, but I also need to be able to trust the management interface on production systems.
The underlying services may still be running, but if the UI cannot be trusted for everyday administration, sooner or later migration becomes the only realistic option.
I hope the CWP team understands that this is not about refusing to accept bugs in a new release. The concern is that the current situation has been going on for too long, with multiple regressions being reported and very little communication about when they will be fixed.
I would much rather see CWP get these issues properly resolved and return to the level of stability we had before than have to migrate to another solution.
But if the panel cannot become reliable again, then unfortunately migration will be the logical next step.
If these issues are not properly resolved and the CWP panel does not return to a stable and reliable state, I don't see many alternatives other than migrating to another control panel.
I have been using CWP because it was a practical and relatively stable solution for managing my servers. I would prefer to stay with CWP, but I also need to be able to trust the management interface on production systems.
The underlying services may still be running, but if the UI cannot be trusted for everyday administration, sooner or later migration becomes the only realistic option.
I hope the CWP team understands that this is not about refusing to accept bugs in a new release. The concern is that the current situation has been going on for too long, with multiple regressions being reported and very little communication about when they will be fixed.
I would much rather see CWP get these issues properly resolved and return to the level of stability we had before than have to migrate to another solution.
But if the panel cannot become reliable again, then unfortunately migration will be the logical next step.
40
Updates / Re: CWP 1.7 – What has actually been fixed? Community feedback
« Last post by interweb on August 09, 2026, 07:09:48 PM »The firewall module has fewer features, and I don't think it's working properly when editing the files directly
/etc/csf/csf.tempban
The changes aren't reflected in the module, and they also reduced the ban duration to just 30 days in the module
I'm thinking about using HESTIA CP; now that it has AI, it's much easier and faster to manage.
/etc/csf/csf.tempban
The changes aren't reflected in the module, and they also reduced the ban duration to just 30 days in the module
I'm thinking about using HESTIA CP; now that it has AI, it's much easier and faster to manage.
