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.
181
Installation / Re: The encoded file /usr/local/cwpsrv/htdocs/admin/index.php has expired
« on: November 17, 2025, 10:13:07 PM »
Did you try the latest EL7 just to recover your install? CWP is CWP (but the installers for EL7 and EL8 are a bit different):
Code: [Select]
wget static.cdn-cwp.com/files/cwp/el7/cwp-el7-0.9.8.1218.zip
182
Installation / Re: The encoded file /usr/local/cwpsrv/htdocs/admin/index.php has expired
« on: November 17, 2025, 06:30:46 PM »
Did you change the version number to the latest one (0.9.8.1218)? And use the EL8 version, not the old CentOS 7 version?
183
CSF Firewall / Re: 100's of suspicious emails an hour
« on: November 16, 2025, 09:18:31 PM »
Are you on AlmaLinux 8 or 9? If AlmaLinux 8, you could install cgroups for resource limits.
184
CentOS-WebPanel GUI / Re: PHP version for control panel
« on: November 16, 2025, 02:24:12 PM »
Yes, that's the unfortunate reality. CWP's internal PHP version is locked to 7.2.30 -- but this is only for their internal services (ports 2030, 2031, 2083, 2087, 2095, 2096). It would be better if they could get onto 7.4 for internal use or best if they could get onto a supported 8.x branch. https://endoflife.date/php But I suppose their goal is to have a static, predictable PHP version that performs identically across systems. Hard to know for sure without code review that isn't possible with IonCube encoded PHP files.
You can set the system-wide PHP version, including the CLI as Cyberspace described.
You can set the system-wide PHP version, including the CLI as Cyberspace described.
185
CentOS-WebPanel Bugs / Re: [CRITICAL] Multiple CWP Servers Infected – Arbitrary PHP Code Execution via Publ
« on: November 13, 2025, 05:18:25 PM »
Yes, the latter files are from other PHP injection attacks with web shells. I've observed those over the years on various servers and panels -- not specific to CWP or the currently discussed CVE (which is patched).
186
CentOS 9 Problems / Re: EL9 recent update casusing boot issue
« on: November 13, 2025, 01:19:55 PM »
You can't go wrong with AlmaLinux 8 -- there's a reason it's the recommended OS for CWP and has a clear path forward.
https://control-webpanel.com/installation-instructions#step2
(But note you should ignore the Minimal/Boot recommendation -- you should start with the DVD installation, just don't add any software profiles such as LAMP or MariaDB when you install -- keep it clean & basic.)
https://control-webpanel.com/installation-instructions#step2
(But note you should ignore the Minimal/Boot recommendation -- you should start with the DVD installation, just don't add any software profiles such as LAMP or MariaDB when you install -- keep it clean & basic.)
188
Updates / Re: ..no dir...
« on: November 07, 2025, 09:39:49 PM »
I would think you could just do:
On my system, I have three different dir versions in /lib/modules, but the newer versions of the dirs's weak-updates subdirs just contain symlinks that point to the contents of the oldest dir's weak-updates dir.
Code: [Select]
mkdir -p /lib/modules/5.14.0-570.55.1.el9_6.x86_64/weak-updates/and be done with fretting about the warning.On my system, I have three different dir versions in /lib/modules, but the newer versions of the dirs's weak-updates subdirs just contain symlinks that point to the contents of the oldest dir's weak-updates dir.
189
Information / Re: I can't access my post history in this forum...
« on: November 07, 2025, 11:58:37 AM »
Seems like a few features are blocked, probably for security reasons. You can't look at user profiles anymore, either -- which can be helpful to see post counts and history (and to check if the new user may be an AI bot...)
190
How to / Re: How to upgrade nginx to the latest version
« on: November 05, 2025, 02:40:48 PM »
Sandeep's AlphaGNU forum is a good place for references like this. This is for Nginx 1.24 with TLS 1.3 support:
https://www.alphagnu.com/topic/47-how-to-enable-tls-13-in-cwp-nginx-reverse-proxy/
But this comment has details for getting brotli compression working and Nginx 1.28:
https://www.alphagnu.com/topic/10-enable-brotli-compression-on-nginx-cwp-and-on-linux-os-for-official-nginx/#comment-12
I do have one dedicated server that runs Nginx (others I manage run Apache), so I am about to make this leap myself (take a deep breath, plunge!)...
https://www.alphagnu.com/topic/47-how-to-enable-tls-13-in-cwp-nginx-reverse-proxy/
But this comment has details for getting brotli compression working and Nginx 1.28:
https://www.alphagnu.com/topic/10-enable-brotli-compression-on-nginx-cwp-and-on-linux-os-for-official-nginx/#comment-12
I do have one dedicated server that runs Nginx (others I manage run Apache), so I am about to make this leap myself (take a deep breath, plunge!)...
191
CentOS-WebPanel Bugs / Re: Can't update linux OS because of mysql-common
« on: November 04, 2025, 05:23:14 PM »
What OS did you install? It's best to start with a clean AlmaLinux DVD install (not minimal and not with any options such as the LAMP profile). System-provided http (Apache) will interfere with CWP's installer script and also you don't want competing MySQL versions that interfere with the recommended MariaDB install, nor a PHP provided by another means than what CWP is offering.
192
Installation / Re: Problems installing CWP 8 with MariaDB
« on: November 03, 2025, 10:05:05 PM »
Do both -- stop the old server's mail, run another rysnc run, then switch DNS, perhaps even one more rsync run (5 min or less). But if the mail service is stopped, it shouldn't be taking in any new mail. Mail will just sit in other servers' outgoing mail queues until your new server becomes available at the DNS address they are looking for.
193
Installation / Re: Best solution for migrate active server from Centos 7 to another distro
« on: November 03, 2025, 03:46:58 PM »
Funny, I thought that was an AI bot posting about AI. But maybe it was just a shill trying to "organically" advertise. Too bad you can't look at user profiles anymore here to see how many posts or how long ago the account was registered...
194
Installation / Re: Best solution for migrate active server from Centos 7 to another distro
« on: November 03, 2025, 11:56:38 AM »
You could try to ELevate the system, but Sandeep (a CWP dev) recommends against it (it can introduce inexplicable oddities). The best course is to install a fresh AlmaLinux 8 system and use CWP Migration to move all accounts, sites, and e-mails over to the new server. If you are very knowledgeable, you could try to manually migrate to AlmaLinux 8 or 9:
You should be able to manually migrate, no problem. I just had to manually migrate my last CentOS 7 server to AlmaLinux 8 because I was continually encountering a bug with CWP Migration (even though it's worked just fine for me for other servers). You dump all DB to a single SQL file, on the new server create the user accounts you are replicating, load the DB SQL on the new server and rsync in all your files -- /home and /var/vmail. (Also move any conf you want to carry over -- CSF firewall, Roundcube, nginx vhosts, DNS zone files, etc.).
https://wiki.centos-webpanel.com/how-to-manually-import-emails
But the postfix DB, particularly the mailbox table has all the end user PW hashes stored. So recreating that DB on the new server will get you all the user PW you need. No need to recreate any mail user accounts or aliases. Also bring over the roundcube DB for a seamless mail experience. Just make sure their /var/vmail IMAP storage is in place and all the references will point appropriately. Voila!
195
Installation / Re: Problems installing CWP 8 with MariaDB
« on: November 02, 2025, 02:25:03 PM »
The goal would be to have 2 concurrently running systems -- your live AL8 system and your newly migrated AL9 system. Then you just change the DNS to point to the new server to complete the migration. In my case, I had 2 VMs on the same host machine, IPs separated by only a couple of digits. I brought up the new system, tested it as best I could, then shut down the main production VM and changed the IP on the replacement VM. It was a seamless transition (1 min downtime), with only some housekeeping to tend to after the switch -- that didn't affect the clients at all. This way, if things go south you can always revert back to the previous VM with only ~1 min downtime.
(Even if you go the DNS route, with Cloudflare you are only talking about >5 min downtime, switching DNS back & forth.)
(Even if you go the DNS route, with Cloudflare you are only talking about >5 min downtime, switching DNS back & forth.)
