New in CWP Edge-LatestFree with every CWPpro licenceWebsites up to 300x faster

CWP now includes LSPHP, LSAPI-Cache and CWP Cage at no extra cost with all CWPpro licences. The LSAPI-Cache plugin is integrated into our WordPress and other script installers, and CWP Cage gives every user complete isolation. Available now in the CWP Edge-Latest version.

Get CWPpro ›

Recent posts

#1
CentOS-WebPanel GUI / Re: DNS zone editor UI problem
Last post by akinsayo - Today at 12:10:00 PM
That is interesting. I just tried 4 different browsers and it is the same.
Servers on LTS do not have the issue.
#2
CentOS-WebPanel Bugs / Re: Switch LTS to Edge automat...
Last post by Wonder - Today at 12:05:17 PM
Other potential improvements I see, which I haven't used, are:
CWP Add-ons -> TeamSpeak 3 Manager.
LSAPI PHP + Cache
Migration from another panel, Source Panel (these are the panels listed, I haven't tested them):
aaPanel, CyberPanel, DirectAdmin, HestiaCP, ISPConfig, Plesk, Virtualmin, Webuzo
Email: DMARC Reports
#3
Updates / Re: egde or lts
Last post by Wonder - Today at 12:04:03 PM
Quote from: universal4 on November 21, 2026, 09:54:42 AMLooks like the latest Iteration of 1.30.32 has the pcre2 fixed up as well as possible issues with ioncube loader issues.

If you try an update and it stays on 1.30.31 because it thinks the update already is set, try forcing the cron.daily to run and it should take that up to the latest point release on the LTS. (I saw that earlier also)
Sorry @universal4, in my previous post, I mistakenly replied in another language. I can no longer edit it, but I meant to say this:

In my case, on an Alma8 server with version 1.30.31, it didn't work that way. I tried everything I saw on the forum, and nothing worked. I found another solution, which I'll explain here:

https://forum.centos-webpanel.com/centos-webpanel-bugs/cwp-lts-php-8-3-37-pcre2-ioncube-issues/
#4
CentOS-WebPanel GUI / Re: DNS zone editor UI problem
Last post by Wonder - Today at 11:57:53 AM
Quote from: akinsayo on <strong>Today</strong> at 08:17:38 AMI am on Edge 2.0.26.
In account control panel for each domain, DNS zone editor, when 'Add Type Record' is clicked, the drop down is not visible. Also, existing records are pushed down the page and you need to scroll down to find it.
I'm not reproducing the problem; the list for adding DNS records appears correctly for me, and I can see all the existing ones.
#5
CentOS-WebPanel GUI / DNS zone editor UI problem
Last post by akinsayo - Today at 08:17:38 AM
I am on Edge 2.0.26.
In account control panel for each domain, DNS zone editor, when 'Add Type Record' is clicked, the drop down is not visible. Also, existing records are pushed down the page and you need to scroll down to find it.
#6
PHP / Re: 9 Critical PHP CVE's - Ple...
Last post by overseer - November 21, 2026, 11:30:04 PM
Wise advice!
#7
PHP / Re: 9 Critical PHP CVE's - Ple...
Last post by Netino - November 21, 2026, 09:23:24 PM
Packages were updated between yesterday and today, but on my server, the php-fpm services were not restarted—meaning they are still running the previous versions.

Try running commands such as:
journalctl -u php-fpm84.service --since "2026-11-10 08:00" --until "today"
If you see that the last restart occurred before the package update, restart your server immediately, as it is still running the old, vulnerable version.

Regards,
Netino
#8
Other / Re: URGENT – CWP update delive...
Last post by itoma - November 21, 2026, 04:00:58 PM
Thanks thefantas, that's an important data point: a freshly reinstalled server with admin ports geo-blocked still received it on the update click. Together with venty's server, that makes three cases on the same day, on EL8, EL9 and EL10, all within roughly two hours (14:20, 15:17 and 16:21 UTC), and all right after an update started from the panel.

In another thread, the CWP team now attributes this to a plaintext-HTTP step in the update chain that was tampered with in transit, and says it is fixed (HTTPS everywhere, signed packages, gpgcheck=1). However, on my server, updated today to CWP 1.30.27 LTS (EL8):

   •   /etc/yum.repos.d/cwp.repo still uses baseurl=http://repo.centos-webpanel.com/... with gpgcheck=0;
   •   no CWP signing key is imported (rpm -q gpg-pubkey shows only AlmaLinux, EPEL and MariaDB);
   •   /scripts/update_cwp (line 89) still recreates cwp.repo with an http:// baseurl.

So these protections do not seem to have reached existing LTS servers yet.

CWP team, could you please clarify:

   1.   which exact URL in the update chain was fetched over plain HTTP on 2026-11-08, and what it served according to your logs;
   2.   how three servers on different networks could be intercepted within two hours, if not upstream (DNS, your network or a CDN node);
   3.   when HTTPS repositories, gpgcheck=1 and the signing key will actually be deployed to existing servers, and where we can get the official key to import it ourselves.
#9
Updates / Re: egde or lts
Last post by Wonder - November 21, 2026, 12:55:49 PM
Quote from: universal4 on November 21, 2026, 09:54:42 AMLooks like the latest Iteration of 1.30.32 has the pcre2 fixed up as well as possible issues with ioncube loader issues.

If you try an update and it stays on 1.30.31 because it thinks the update already is set, try forcing the cron.daily to run and it should take that up to the latest point release on the LTS. (I saw that earlier also)
En mi caso, en un servidor alma8 con 1.30.31 no fue así, probé de todo lo que vi en el foro y no funcionó, tuve otro camino para poder solucionarlo, aquí lo expongo:
https://forum.centos-webpanel.com/centos-webpanel-bugs/cwp-lts-php-8-3-37-pcre2-ioncube-issues/

Quote from: universal4 on November 21, 2026, 08:53:34 AMAgreed, I am currently sticking with the LTS also, but I see the edge version 2.0.26 fixes the PCRE2 library mismatch which I experienced on a few of my servers during recent updates.

Considering building another one, possibly on alma10 and going with the edge updates to see how it goes.
I didn't experience this problem on the server where I have Edge.
Quote from: overseer on November 21, 2026, 03:15:05 AMFor the record, many of us fuddy duddy folks prefer the conservative LTS track.
I've always thought that too. I ventured to try a server on Edge, moved it to production (if something failed I had a "mirror" that I could recover quickly) and I haven't had the problems on Edge that I have had on LTS, like what's mentioned above.
#10
Updates / Re: Unable to update CWP 1.30....
Last post by Wonder - November 21, 2026, 12:49:18 PM
Quote from: uma on November 21, 2026, 10:25:32 AMHello,

OS: AlmaLinux release 8.10 (Cerulean Leopard)
Kernel Version: 4.18.0-553.180.1.el8_10.cwpsec.x86_64
CWP: Free version
Apache version: Apache/2.4.71
PHP version: 8.2.35
MySQL version: 10.3.39-MariaDB

Unable to update CWP version to latest stable:

[root@ ~]# sh /scripts/update_cwp

panel PHP cannot use pcre with /usr/local/lib/libpcre2-8.so.0 - rebuilding pcre2 with JIT
libtool: warning: relinking 'libpcre2-posix.la'
pcre2 rebuilt with JIT
panel PHP pcre still failing
diagnostics: /usr/local/lib/libpcre2-8.so /usr/local/lib/libpcre2-8.so.0 /usr/local/lib/libpcre2-8.so.0.10.4
  /usr/local/lib/libpcre2-8.so.0 -> /usr/local/lib/libpcre2-8.so.0.10.4; SELinux: Disabled; kernel: 4.18.0-553.180.1.el8_10.cwpsec.x86_64
panel PHP is unknown, code 1.30: running the 8.3 migration/recovery before the update
/scripts/update_cwp: line 34: /usr/local/cwp/php71/bin/php: No such file or directory

[root@ ~]#



request to guide further.



Hi,

I recently experienced a very similar issue on AlmaLinux 8.10 with CWP LTS, including exactly the same PCRE2 errors during the update.

In my case, the problem started after CWP automatically installed cwpphp 8.3.37-1.el8. Upgrading to cwpphp 8.3.37-2.el8 resolved the issue, and I was then able to update CWP to version 1.30.32 without errors.

I've documented the troubleshooting, comparisons and final solution in this thread:

https://forum.centos-webpanel.com/centos-webpanel-bugs/cwp-lts-php-8-3-37-pcre2-ioncube-issues/

However, your case is slightly different because `/usr/local/cwp/php71/bin/php` appears to be missing, whereas it was present on my server.

I'd recommend checking which cwpphp package is installed and whether the PHP executable exists before attempting the same fix:

rpm -q cwpphp
ls -l /usr/local/cwp/php71/bin/php

Hope this helps!