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.
16
Information / Re: Modernizing CWP: Drop EOL, Support AL9, AL10 & Rocky
« on: March 20, 2026, 12:54:34 PM »
My intention in posting this request to the developers was to gather community support by encouraging everyone affected to respond and post here. I hoped that, if the number of replies increased to a significant level, it might give the developers more incentive to implement it sooner—similar to a petition. I did not intend to undermine your efforts which I acknowledge and support.
17
Information / Modernizing CWP: Drop EOL, Support AL9, AL10 & Rocky
« on: March 20, 2026, 09:30:14 AM »
Hello,
I would like to propose that the CWP project and its developers consider discontinuing support for end-of-life (EOL) operating systems such as CentOS 7.
At the same time, I encourage the team to prioritize development efforts on modern, actively maintained platforms like AlmaLinux 9 (AL9), AlmaLinux 10 (AL10), and Rocky Linux. Ensuring full support for these operating systems as soon as possible—well before AL9 reaches end of life—should be a key priority.
Focusing on current platforms will improve security, stability, and long-term sustainability for both developers and users.
If others in the community share this perspective, I invite you to comment and help signal to the developers your views on the future direction and foundational priorities of CWP.
Thanks.
I would like to propose that the CWP project and its developers consider discontinuing support for end-of-life (EOL) operating systems such as CentOS 7.
At the same time, I encourage the team to prioritize development efforts on modern, actively maintained platforms like AlmaLinux 9 (AL9), AlmaLinux 10 (AL10), and Rocky Linux. Ensuring full support for these operating systems as soon as possible—well before AL9 reaches end of life—should be a key priority.
Focusing on current platforms will improve security, stability, and long-term sustainability for both developers and users.
If others in the community share this perspective, I invite you to comment and help signal to the developers your views on the future direction and foundational priorities of CWP.
Thanks.
18
Information / Nominate Advisors and or Developers
« on: March 20, 2026, 09:14:39 AM »
Hello,
Both Starburst and overseer (and others) have demonstrated strong expertise in CWP and have been instrumental in helping me resolve several technical issues. I’m genuinely grateful for their support and contributions.
I would highly recommend that the CWP developers consider involving them more closely—both in shaping the strategic direction of the platform and potentially contributing to its development. Their deep understanding of the system and its technical challenges would be a valuable asset.
Ultimately, developers should make a conscious effort to listen to the users of their products. User feedback is essential for continuous improvement and long-term success.
You would both have my vote as CWP advisors or developers .
Thanks.
Both Starburst and overseer (and others) have demonstrated strong expertise in CWP and have been instrumental in helping me resolve several technical issues. I’m genuinely grateful for their support and contributions.
I would highly recommend that the CWP developers consider involving them more closely—both in shaping the strategic direction of the platform and potentially contributing to its development. Their deep understanding of the system and its technical challenges would be a valuable asset.
Ultimately, developers should make a conscious effort to listen to the users of their products. User feedback is essential for continuous improvement and long-term success.
You would both have my vote as CWP advisors or developers .
Thanks.
19
Information / Re: Past Due Changelogs
« on: March 18, 2026, 08:26:07 AM »
Yes its great news that change logs are being published once again. Long may it continue.
However you need to analyse the dates of the updates which I assume are accurate.
In 2023 there were regular monthly updates, sometimes two per month.
In 2024 there were only two updates.
In 2025 there were only two updates.
And in 2026 we have the first update.
What happened to regular monthly updates to fix and enhance CWP especially on AlmaLinux 9.x and 10.x ? Please discontinue support on EOL operating systems and focus on the new.
Thanks
However you need to analyse the dates of the updates which I assume are accurate.
In 2023 there were regular monthly updates, sometimes two per month.
In 2024 there were only two updates.
In 2025 there were only two updates.
And in 2026 we have the first update.
What happened to regular monthly updates to fix and enhance CWP especially on AlmaLinux 9.x and 10.x ? Please discontinue support on EOL operating systems and focus on the new.
Thanks
20
Addons / Does CWP on Alma Linux 9.x have Python Pre-Installed - How to Upgrade
« on: March 17, 2026, 09:52:50 AM »
Hello,
I have CWP installed on Alma Linux 9.x
When I run python3 --version in an account ssh it says I have python 3.9x installed.
I'm no python expert but how to you upgrade python to v3.11 or later on a cwp server so that it will run in a ssh user account ?
Thanks.
I have CWP installed on Alma Linux 9.x
When I run python3 --version in an account ssh it says I have python 3.9x installed.
I'm no python expert but how to you upgrade python to v3.11 or later on a cwp server so that it will run in a ssh user account ?
Thanks.
21
Other / Re: Goodbye CWP — I’m done for good
« on: February 25, 2026, 12:50:29 PM »
What an irony 😄 — someone suggested that the CWP forum should be hosted on Cloudflare instead of running on CWP itself… and yet it still keeps going down from time to time.
You’d think the CWP developers, of all people, would have PHP tuned rock-solid so the forum stays up consistently if php resources were the issue.
Also, the change logs still aren’t being updated. Without clear change logs, it’s really hard for users to confirm — or properly audit — what’s being changed, whether from a functionality or a security standpoint. A bit more transparency here would go a long way to stop users abandoning the project in the short term.
You’d think the CWP developers, of all people, would have PHP tuned rock-solid so the forum stays up consistently if php resources were the issue.
Also, the change logs still aren’t being updated. Without clear change logs, it’s really hard for users to confirm — or properly audit — what’s being changed, whether from a functionality or a security standpoint. A bit more transparency here would go a long way to stop users abandoning the project in the short term.
22
PHP Selector / Re: Support for PHP 8.4
« on: February 10, 2026, 11:41:23 AM »
Hello,
When will the change logs be updated. Still showing 13/11/2024 ?
Thanks
When will the change logs be updated. Still showing 13/11/2024 ?
Thanks
23
Updates / Re: Is CWP dead? Looking for alternatives
« on: January 13, 2026, 01:58:37 PM »
A Community Perspective on CWP: What’s Working and What Could Improve
I’ve been using CWP (Control Web Panel) for some time now and I want to start by saying that I genuinely like the CWP feature set. It offers a lot of functionality at a very competitive price point and for many users it remains a solid alternative in the server control panel space.
That said, like many others in the community, I believe there are a few areas where CWP could improve—particularly around communication and transparency.
Better Visibility Into Changes and Updates
One of the biggest improvements I’d like to see is a consistently updated changelog after each release. Having a clear, detailed record of what has changed would help users understand new features, bug fixes, and potential impacts on their systems. It also builds trust when users can easily review what’s been modified.
Along similar lines, it would be great to see core services such as Apache, Nginx, MariaDB and other major components updated in a timely manner, especially when older versions become obsolete or reach end-of-life. Staying current is important not just for features, but for security and long-term stability.
Stronger Communication With the Community
Another recurring pain point is communication. When the forum goes down, for example, it would be extremely helpful to see official forum announcements explaining why, even if it’s just a brief status update.
More broadly, I think many users would appreciate regular announcements from the CWP development team about:
* What they are currently working on
* Known issues or outages
* Problems encountered during development
* Estimated timelines where possible
This doesn’t need to be overly detailed—just enough to keep the community informed and reassured.
Avoiding Community “Ghosting”
CWP is a product supported by a paying user base. When users are actively making payments that help keep the product alive, it’s discouraging to feel like the community is being ghosted during periods of silence. Even short updates can go a long way toward maintaining goodwill and confidence in the platform.
A Simple Ask From the Community
Ultimately, I don’t think these requests are unreasonable. Most people in the CWP community who enjoy using the product aren’t asking for perfection—we’re just asking for a bit more visibility into what’s going on behind the scenes.
Clear communication, timely updates, and basic transparency would strengthen the relationship between the development team and the community, and help ensure CWP continues to grow and improve with user trust intact.
CWP has strong potential, and with better communication, it could be even better.
I’ve been using CWP (Control Web Panel) for some time now and I want to start by saying that I genuinely like the CWP feature set. It offers a lot of functionality at a very competitive price point and for many users it remains a solid alternative in the server control panel space.
That said, like many others in the community, I believe there are a few areas where CWP could improve—particularly around communication and transparency.
Better Visibility Into Changes and Updates
One of the biggest improvements I’d like to see is a consistently updated changelog after each release. Having a clear, detailed record of what has changed would help users understand new features, bug fixes, and potential impacts on their systems. It also builds trust when users can easily review what’s been modified.
Along similar lines, it would be great to see core services such as Apache, Nginx, MariaDB and other major components updated in a timely manner, especially when older versions become obsolete or reach end-of-life. Staying current is important not just for features, but for security and long-term stability.
Stronger Communication With the Community
Another recurring pain point is communication. When the forum goes down, for example, it would be extremely helpful to see official forum announcements explaining why, even if it’s just a brief status update.
More broadly, I think many users would appreciate regular announcements from the CWP development team about:
* What they are currently working on
* Known issues or outages
* Problems encountered during development
* Estimated timelines where possible
This doesn’t need to be overly detailed—just enough to keep the community informed and reassured.
Avoiding Community “Ghosting”
CWP is a product supported by a paying user base. When users are actively making payments that help keep the product alive, it’s discouraging to feel like the community is being ghosted during periods of silence. Even short updates can go a long way toward maintaining goodwill and confidence in the platform.
A Simple Ask From the Community
Ultimately, I don’t think these requests are unreasonable. Most people in the CWP community who enjoy using the product aren’t asking for perfection—we’re just asking for a bit more visibility into what’s going on behind the scenes.
Clear communication, timely updates, and basic transparency would strengthen the relationship between the development team and the community, and help ensure CWP continues to grow and improve with user trust intact.
CWP has strong potential, and with better communication, it could be even better.
24
Addons / Is Nextcloud Compatible with CWP on AlmaLinux 9.x and MariaDB 11.4.x?
« on: December 06, 2025, 11:44:29 AM »
Hello,
I’m looking to find out whether Nextcloud is fully compatible with CWP running on AlmaLinux 9.x using MariaDB 11.4.x. Before setting up a new instance, I want to make sure there are no major issues with installation, database support, or general functionality.
Has anyone tested this setup or is currently running Nextcloud with these versions?
Any feedback or tips would be greatly appreciated.
Thanks
I’m looking to find out whether Nextcloud is fully compatible with CWP running on AlmaLinux 9.x using MariaDB 11.4.x. Before setting up a new instance, I want to make sure there are no major issues with installation, database support, or general functionality.
Has anyone tested this setup or is currently running Nextcloud with these versions?
Any feedback or tips would be greatly appreciated.
Thanks
25
Information / Re: CWP centos7 to CWP Almalinux 9 Migration Planned
« on: December 02, 2025, 11:49:58 AM »
It seems unreasonable to hold back the evolution of CWP just to maintain support for an end-of-life CentOS 7, especially when many in the community are ready to move forward with AL9 and AL10.
Why not simply branch CWP—one branch for CentOS 7 and 8, and another dedicated to AL9 and AL10, with all new features developed for the modern branch? This approach would allow continued legacy support while enabling progress for users on newer platforms.
It would also be helpful if the developers provided a clear public statement on the forum explaining why CWP development appears to have stalled to accommodate an EOL operating system. Transparency on this issue would go a long way toward easing community concerns. Updating the change log would also be beneficial.
Thanks
Why not simply branch CWP—one branch for CentOS 7 and 8, and another dedicated to AL9 and AL10, with all new features developed for the modern branch? This approach would allow continued legacy support while enabling progress for users on newer platforms.
It would also be helpful if the developers provided a clear public statement on the forum explaining why CWP development appears to have stalled to accommodate an EOL operating system. Transparency on this issue would go a long way toward easing community concerns. Updating the change log would also be beneficial.
Thanks
26
Updates / Re: AL 9.6, I have info about 240 updates
« on: November 30, 2025, 10:41:02 AM »
Hello,
I’ve been following the ongoing discussion about CWP’s lack of support for AlmaLinux 9.x, 10.x, and the newer MariaDB releases. This has affected me as well, especially since many open-source projects now require MariaDB 10.x or 11.x at minimum. Without support for these versions, CWP becomes increasingly limiting for modern deployments.
What are the technical reasons preventing CWP from supporting AlmaLinux 9.x/10.x and the newer MariaDB versions?
Also, why have the developers not provided an official statement or roadmap on the forum regarding these issues?
On a related note, CyberPanel looks like an interesting alternative — has anyone here tried it?
Thanks
I’ve been following the ongoing discussion about CWP’s lack of support for AlmaLinux 9.x, 10.x, and the newer MariaDB releases. This has affected me as well, especially since many open-source projects now require MariaDB 10.x or 11.x at minimum. Without support for these versions, CWP becomes increasingly limiting for modern deployments.
What are the technical reasons preventing CWP from supporting AlmaLinux 9.x/10.x and the newer MariaDB versions?
Also, why have the developers not provided an official statement or roadmap on the forum regarding these issues?
On a related note, CyberPanel looks like an interesting alternative — has anyone here tried it?
Thanks
27
Addons / Starting Symfony Development on CWP – Composer Questions
« on: November 29, 2025, 04:01:24 PM »
Hello,
I wanted to share a bit of my experience and get some advice from anyone here who has worked with Symfony or Composer inside a CWP hosting environment.
Over the past few months, I’ve successfully installed several open-source PHP projects on a CWP hosting account without using Composer — even projects that normally rely heavily on Symfony components. While it worked, it obviously isn’t the ideal way to manage Symfony-based applications, so I’m now looking to begin proper Symfony development directly inside a CWP user account.
That brings me to a few questions I’m hoping someone with more CWP + Symfony experience might be able to clarify:
1. Is Composer fully compatible with CWP?
Symfony depends heavily on Composer, so before I jump in, I want to confirm whether Composer runs smoothly within a CWP-managed hosting setup.
2. What’s the correct way to install Composer on CWP?
Should Composer be installed from root SSH for system-wide access, or is it better (or safer) to install it under an individual CWP user account via user-level SSH? I’m not sure what the recommended or most stable approach is.
3. Once installed, can Composer be used to deploy open-source applications into a CWP account?
For example, if I want to install a Symfony skeleton or another Composer-based project directly into a user’s `/home/ACCOUNT/` directory, is this supported without breaking anything inside the panel or causing permission issues?
I’d really appreciate any guidance from users who have already gone down this road. Symfony development is much easier when everything is done the right way from the start, so any tips from the community would be extremely valuable.
Thanks
I wanted to share a bit of my experience and get some advice from anyone here who has worked with Symfony or Composer inside a CWP hosting environment.
Over the past few months, I’ve successfully installed several open-source PHP projects on a CWP hosting account without using Composer — even projects that normally rely heavily on Symfony components. While it worked, it obviously isn’t the ideal way to manage Symfony-based applications, so I’m now looking to begin proper Symfony development directly inside a CWP user account.
That brings me to a few questions I’m hoping someone with more CWP + Symfony experience might be able to clarify:
1. Is Composer fully compatible with CWP?
Symfony depends heavily on Composer, so before I jump in, I want to confirm whether Composer runs smoothly within a CWP-managed hosting setup.
2. What’s the correct way to install Composer on CWP?
Should Composer be installed from root SSH for system-wide access, or is it better (or safer) to install it under an individual CWP user account via user-level SSH? I’m not sure what the recommended or most stable approach is.
3. Once installed, can Composer be used to deploy open-source applications into a CWP account?
For example, if I want to install a Symfony skeleton or another Composer-based project directly into a user’s `/home/ACCOUNT/` directory, is this supported without breaking anything inside the panel or causing permission issues?
I’d really appreciate any guidance from users who have already gone down this road. Symfony development is much easier when everything is done the right way from the start, so any tips from the community would be extremely valuable.
Thanks
28
Dovecot / Can I Route Only Bounce-Back Emails to a Different Mailbox
« on: November 03, 2025, 07:16:54 AM »
Hi everyone,
I’m trying to figure out if there's a way in CWP Email to route only bounce-back emails to a separate mailbox without using the catch-all option.
What I want to do:
* Mailbox A → send and receives all normal incoming emails
* Mailbox B → receives only bounce-back / deliverable messages that were originally sent from Mailbox A
Basically, I want one mailbox for regular mail and another one dedicated strictly to bounce messages for the first mailbox only.
Has anyone done this in CWP, or know if this is even possible?
Thanks
I’m trying to figure out if there's a way in CWP Email to route only bounce-back emails to a separate mailbox without using the catch-all option.
What I want to do:
* Mailbox A → send and receives all normal incoming emails
* Mailbox B → receives only bounce-back / deliverable messages that were originally sent from Mailbox A
Basically, I want one mailbox for regular mail and another one dedicated strictly to bounce messages for the first mailbox only.
Has anyone done this in CWP, or know if this is even possible?
Thanks
29
MySQL / Re: Mariadb 10.5.x Support has Expired - How to Upgrade Manually ?
« on: September 10, 2025, 09:08:36 AM »
The output from mariadb --version is
mariadb from 11.4.8-MariaDB, client 15.2 for Linux (x86_64) using EditLine wrapper
Therefore the CWP dashboard, bottom left is reporting the client version 15.2 and not the mariadb version 11.4.8
Is that a bug or is it by design ?
Thanks.
mariadb from 11.4.8-MariaDB, client 15.2 for Linux (x86_64) using EditLine wrapper
Therefore the CWP dashboard, bottom left is reporting the client version 15.2 and not the mariadb version 11.4.8
Is that a bug or is it by design ?
Thanks.
30
MySQL / Re: Mariadb 10.5.x Support has Expired - How to Upgrade Manually ?
« on: September 10, 2025, 06:43:59 AM »
The web apps I'm running recommended mariadb 11.4 over 10.11 so I decided to go with 11.4.
I followed the instructions step by step and it installed fine - no observable errors so far.
All websites appear to be running normally but noticeably faster on the same hardware which is a bonus.
The only thing I have observed is that on the CWP dashboard the database is now reporting 15.2 and not 11.4. Whereas it was reporting 10.5.x before the upgrade. Do you observe the same thing on your servers ?
However the web apps correctly identify mariadb 11.4 and they appear to be working normally.
Thanks to everyone for your help.
I followed the instructions step by step and it installed fine - no observable errors so far.
All websites appear to be running normally but noticeably faster on the same hardware which is a bonus.
The only thing I have observed is that on the CWP dashboard the database is now reporting 15.2 and not 11.4. Whereas it was reporting 10.5.x before the upgrade. Do you observe the same thing on your servers ?
However the web apps correctly identify mariadb 11.4 and they appear to be working normally.
Thanks to everyone for your help.
