CWP 1.7 – What has actually been fixed? Community feedback

Now that we've reached CWP 1.7, I'd like to understand the current state of the platform and compare experiences with other administrators.

After the silent transition from 0.9.8.12.44 to the new 1.x series, I experienced several issues that mainly affected the new UI. Looking through the forum, it seems I was not the only one.

These are the issues I have personally encountered:

- YUM Manager inaccessible or stuck.
- ModSecurity management not working from the UI.
- Firewall management issues.
- PHP Selector not working correctly.
- New Backup module (still marked as Beta) with poor email reporting:
    - notifications often don't specify whether the backup was local or remote;
    - there is no clear summary of which accounts completed successfully and which failed;
    - overall reporting is not sufficient for production environments.
- SSL certificate generation/management issues.
- Occasional problems with Roundcube.

The good news is that, on my servers, the backend itself has remained functional. Most operations continue to work correctly from the command line, which suggests that many of the regressions are related to the new UI rather than the underlying services.

What concerns me most is not a single bug, but the impact these updates had on production environments. A control panel used to manage production servers should prioritize stability and reliability. Releasing updates that introduce regressions into core administrative functions creates unnecessary operational risks, especially for administrators managing multiple servers.

Now that several updates have already been released and we're at version 1.7, I'd like to hear from other users.

- Which issues have actually been resolved?
- Which problems are you still experiencing?
- Is 1.7 stable enough for daily production use?
- Have you found any new regressions that haven't yet been discussed?
- Has the new Backup module become reliable, or are there still significant limitations?

I'm not interested in starting a complaint thread. My goal is to build an accurate picture of the current state of CWP 1.7 so that administrators can make informed decisions and developers can better understand which areas still need attention.

I appreciate any feedback from those running CWP in real production environments.

Nothing was Fixed, we dont know what are they trying to do, but the only thing i know they are breaking everything not even the text edit from filebrowser is functioning right. There are some new views but they are so confusing they seems to be done by a drug adict.

I dont think cwpro have much life in it they not fixing, they are breking, not even backups works now.

Thanks for sharing your experience. This is exactly the kind of feedback I was hoping to get with this thread.

For me, the main issue is not whether a particular bug can eventually be fixed. The bigger problem is that, as a CWP user, I need to be able to trust the software I install on a production server.

I don't want a managed service, and I'm not asking CWP to manage my server for me. I chose a control panel because I want to administer the server myself, with a reliable UI and predictable behavior.

If something breaks, I can use the CLI and fix it myself. That's not the point. If I have to increasingly bypass the panel and work directly from the command line because I cannot trust what the next CWP update might change, then I have to seriously question what value the panel is providing.

The biggest problem right now is that I simply don't have enough information to make a safe decision about updating.

It is difficult to understand:

* which problems have actually been fixed;
* which problems are still known;
* which fixes may have introduced regressions;
* what has been tested before release;
* and whether an update is considered safe for production.

The changelog alone doesn't give me enough confidence to answer a very simple question:

**“Can I safely update my production server now?”**

At the moment, I don't know the answer to that question — and that is precisely what prevents me from updating.

I've already disabled silent updates on my production servers because I need to be the one deciding when an update is applied, after making sure my data is protected and the release is safe enough for my environment.

I don't expect CWP to be perfect. Bugs happen.

What I do expect is transparency, predictable updates, and enough technical information to make an informed decision as a system administrator.

If I install CWP, I want a control panel I can trust — not a managed service, and not a system where I have to guess whether the next update will break something.

I've already made up my mind; I'm not going back to that CWP panel. It's useless, and the support team treats people like idiots.
I've already started migrating my accounts

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.

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.

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.