Unfortunately, as many users can see, only Starburst and Overseer seem to be actively helping on the forum, and they do their best to support the community. I appreciate their efforts.
However, I am disappointed by the lack of communication from the CWP team. I currently maintain 20 active CWP PRO servers. Three of them are running AlmaLinux 8, while the rest are still on CentOS 7 because I do not yet consider the AlmaLinux 9 version ready for production use.
I would genuinely like to be proven wrong, but with solid technical arguments.
Starburst and Overseer, please do not take this personally. I have always tried to contribute constructively on this forum.
My concern is simple: the AlmaLinux 9 branch of CWP remained in BETA for more than a year. Now that it has been officially released and promoted as a supported platform, why does a fresh installation still deploy outdated packages and service versions? After such a long beta period, many of us expected a more modern, secure, and production-ready software stack by default.
I have deployed CWP solutions for multiple clients in addition to my own VPS infrastructure. The reality is that we cannot continue operating indefinitely with outdated components while new CVEs are published every few days and remain unresolved.
On AlmaLinux 8, I was forced to manually update Nginx, Apache, MariaDB, and Roundcube. This process generated several operational issues, which I eventually resolved using a combination of Starbursts forum posts and solutions from the AlphaGNU forum. While acceptable on a single server, this approach does not scale when managing dozens of production VPS instances and client environments.
In CWP, I have repeatedly faced inconsistencies in managing core stack components such as Nginx, Apache, MariaDB, PHP (including multiple versions and updates), Roundcube, and Varnish. Support for newer versions appears inconsistent across panel releases, and in practice installation or upgrade processes frequently lead to dependency conflicts, broken configurations, or service instability.
This creates a serious challenge in maintaining stable production environments across multiple servers.
What many of us are asking for is not another temporary patch, but a clear direction and active communication from the CWP development team. At the moment, the official administrators and support channels appear largely silent, and this creates uncertainty for users who rely on CWP in production environments.
I believe many long-term CWP PRO customers would appreciate greater transparency on these points.
This message does not come from someone testing CWP in a lab environment. It comes from a paying customer who manages 20 active CWP PRO servers and has deployed CWP solutions for multiple clients over the years. The intention is not criticism for its own sake, but a request for clarity, consistency, and more reliable long-term platform maintenance.
Topic: HTTP/2 Bomb Remote DoS Exploit Hits nginx, Apache, IIS, Envoy, and Cloudflare (Read 512 times)
