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
MySQL / MariaDB Password Reset Script Doesn't Work
« on: October 26, 2025, 10:11:03 PM »
I know this script worked perfectly before.
I've recently done several installations of CWP 8 (for various tests), and after installing CWP 8 without restarting, if we run the password reset script, it works. However, if we restart CWP 8 after installing it, it no longer works, and from what I can see, we lose access to CWP administration (and therefore, the MariaDB service is inoperative).
I've tested it with both the stock and upgraded versions of MariaDB.
I understand that, over time and with updates, the script has become "outdated."
This is the code that appears when we run it:
Code: [Select]
/scripts/mysql_pwd_resetI've recently done several installations of CWP 8 (for various tests), and after installing CWP 8 without restarting, if we run the password reset script, it works. However, if we restart CWP 8 after installing it, it no longer works, and from what I can see, we lose access to CWP administration (and therefore, the MariaDB service is inoperative).
I've tested it with both the stock and upgraded versions of MariaDB.
I understand that, over time and with updates, the script has become "outdated."
This is the code that appears when we run it:
Code: [Select]
[root@server ~]# /scripts/mysql_pwd_reset
Enter the new root password (at least 8 chars).
Or leave it empty if you would like to generate it.
Or press CTRL+C to abort and do not touch it
Enter MySQL root password (NO special characters): testpass9876
Shutting down any mysql processes...
/scripts/mysql_pwd_reset: line 14: [: -eq: unary operator expected
Redirecting to /bin/systemctl stop mariadb.service
/scripts/mysql_pwd_reset: line 26: [: -eq: unary operator expected
Redirecting to /bin/systemctl start mariadb.service
Resetting password... hold on
--------------
UPDATE mysql.user SET Password=PASSWORD('testpass9876'),Authentication_string=PASSWORD('testpass9876') WHERE user='root'
--------------
ERROR 1348 (HY000) at line 1: Column 'Password' is not updatable
Cleaning up...
/scripts/mysql_pwd_reset: line 14: [: -eq: unary operator expected
Redirecting to /bin/systemctl stop mariadb.service
Password reset has been completed
New MySQL root password: testpass9876
Remember to store this password safely!
/scripts/mysql_pwd_reset: line 26: [: -eq: unary operator expected
Redirecting to /bin/systemctl start mariadb.service
[root@server ~]#
17
Installation / Re: Problems installing CWP 8 with MariaDB
« on: October 26, 2025, 09:41:24 PM »There's isn't a mariadb repo right after the CWP installation anymore, since the version they are installing is past EOL.Yes, that's what I've seen. A fresh CWP installation doesn't have a MariaDB repository.
Regarding these instructions:
Quote
You also don't need to disable the whole cwp.repo, you can just add this form the above, so MariaDB won't try to install from it.I could swear I tried it, I could swear I tried it and it didn't work, but now I'm doubting it. I did a lot of testing to be able to post here with confidence. And this point, I think I tried it and it didn't work, but I can't be 100% sure, maybe 90% sure. Since I have a test server now, I can test it and be sure.
You add this to cwp.repo below enabled=1Code: [Select]exclude=mariadb*
Then follow the upgrade instructions from AlphaGNU.
Quote
All of our servers run AL9 with CWP.Indeed, I don't need PHP below 7.4 on two out of three sites, and I'm using AL8 on all of them.
If you don't need PHP below 7.4 or site migration (problem with 2 different security algorithms) AL9 would be better.
And if you want, do the basic AL9 image, and I can login and get everything installed for you. (no cost)
You would just need to PM me your login info.
But... if I have the problem you mentioned, I need a migration. I can migrate the website and the database manually, but not the email accounts. I can rsync the email accounts, but, above all, I have a server with many email accounts and the password. I can't ask them to reset it (the password for the email accounts). That would have to be migrated. And it's one of the two issues you mentioned, the migration, which is why it's so important to me, because of the email accounts.
Regarding the basic AL9 image, you can't imagine how much I appreciate it. I installed AL9 from scratch, but unlike AL8, I've noticed that iptables must be installed to activate CSF, and that makes me think maybe more things are needed. It would be helpful to know what those things are. I'll contact you.
Let's see if CWP 9 evolves further and isn't still in Beta...
Thank you sincerely.
18
Installation / Re: Problems installing CWP 8 with MariaDB
« on: October 26, 2025, 12:17:50 PM »
Yes, I reinstalled yesterday and the same thing happened again, the same problem and errors at the same point or points, so I deduced that the installer + Almalinux 8 had changed something (I mean the installer: https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-install-tutorials/updated-cwp-installer-script-for-almalinux-8-with-mariadb-10-6/ )
So, indeed, I used the stock CWP installer (from CWP web) and then updated MariaDB following the instructions here:
https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/
But as I mentioned, there is one point that is not viable, it gives the error I indicated In the first post, at this point:
You must disable the MariaDB repo. The instructions would be:
This is the only viable way I found to update MariaDB. I performed several installations (on the same server for testing) so I can provide accurate instructions here.
By the way, sorry for being off-topic, you say you've moved to AL9 using CWP9. I currently have a server for testing, and I've tested it. To install CSF, I have to install iptables (iptables doesn't come installed by default, although it's not a major problem), but... is CWP9 fully operational?
It still has the problem of not being able to migrate accounts from CWP8 to CWP9, and that's important to me. I would migrate some to AL/CWP9, but if I can't do the migration, I can't. AL9 is only viable for fresh installations, but for existing ones, if the account can't be migrated, CWP -> CWP Migration is important to me.
Thanks
So, indeed, I used the stock CWP installer (from CWP web) and then updated MariaDB following the instructions here:
https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/
But as I mentioned, there is one point that is not viable, it gives the error I indicated In the first post, at this point:
Code: [Select]
yum clean all
yum install MariaDB-server MariaDB-client MariaDB-devel MariaDB-shared net-snmp perl-DBD-MySQL -y
yum update -yJust beforeCode: [Select]
yum install MariaDB.... etc....We need to disable the CWP repo. If you don't disable the CWP repo, the MariaDB update won't happen.You must disable the MariaDB repo. The instructions would be:
Code: [Select]
yum clean all
nano /etc/yum.repos.d/cwp.repo
Set enabled=0
Save changes, and then:
yum install MariaDB-server MariaDB-client MariaDB-devel MariaDB-shared net-snmp perl-DBD-MySQL -y
Then, very important:
nano /etc/yum.repos.d/cwp.repo
Set enabled=1
Save changes
yum update -y The following steps are as described in the manual.This is the only viable way I found to update MariaDB. I performed several installations (on the same server for testing) so I can provide accurate instructions here.
By the way, sorry for being off-topic, you say you've moved to AL9 using CWP9. I currently have a server for testing, and I've tested it. To install CSF, I have to install iptables (iptables doesn't come installed by default, although it's not a major problem), but... is CWP9 fully operational?
It still has the problem of not being able to migrate accounts from CWP8 to CWP9, and that's important to me. I would migrate some to AL/CWP9, but if I can't do the migration, I can't. AL9 is only viable for fresh installations, but for existing ones, if the account can't be migrated, CWP -> CWP Migration is important to me.
Thanks
19
Installation / Re: Problems installing CWP 8 with MariaDB
« on: October 25, 2025, 11:57:05 AM »What is failing is cwp-http and cwp-suphp, not only MariaDB.
The tow cwp- files are what's causing the installer to crash, which means for some reason that server isn't talking to the cwp server.
Is this server behind a NAT?
Any firewalls that may be blocking?
Nothing, no NAT, no firewall, nothing, it's a clean install of AlmaLinux 8.
The "official" CWP installer works, but your updater is failing. I don't know why... but it's very, very strange.....
I'll try again later. Maybe I didn't let AlmaLinux update enough time after installing it, and it happened when I was doing something... that's the only thing I can think of, but even so... it's very strange to me...
20
Installation / Re: Problems installing CWP 8 with MariaDB
« on: October 25, 2025, 04:49:06 AM »Your running some commands not in the KB.No, I don't run any commands, I simply install AlmaLinux, and the next step is to install CWP...
Quote
I see a conflict wit the CWP repo, where it's trying to load from.Exactly, that's what I think happens... (I'm referring to updating MariaDB using the CWP installer from the "official" CWP repo).
Quote
You add this to cwp.repo below enabled=1For me, that's not possible. As I mentioned, I do a clean install of AlmaLinux, and the next step is to install CWP using your updated installer. I can't modify any repo because it's not installed; it doesn't install CWP.Code: [Select]exclude=mariadb*
The error you posted, shows the httpd installation failed.
Our updated script only updated MariaDB to install 10.6.
Updated: But I've tried what you say below, just before restarting after installing CWP, and the result is the same error: it doesn't allow it.
For me, the only solution is to disable the CWP repo at the MariaDB update point, and then re-enable it.
Quote
Do you mean using the instructions above to update MariaDB (https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/#comment-25)?QuoteLast metadata expiration check: 0:01:52 ago on Fri 24 Oct 2025 09:58:48 PM CEST.
No match for argument: cwp-httpd
Error: Unable to find a match: cwp-httpd
Last metadata expiration check: 0:01:56 ago on Fri 24 Oct 2025 09:58:48 PM CEST.
No match for argument: cwp-suphp
Error: Unable to find a match: cwp-suphp
Compiler requires 512 MB RAM + SWAP
Installation FAILED at httpd
Try to just use the CWP install script, and before you reboot complete the MariaDB 10.11 update.
Quote
Note, the OS should be a base install, Without LAMP installed.Correct, I don't have LAMP installed; it's a clean AlmaLinux installation.
PS: Sorry my poor english
21
Installation / Re: Problems installing CWP 8 with MariaDB
« on: October 24, 2025, 08:45:33 PM »
As they say around here, a promise is a promise.
I performed a clean install of AlmaLinux 8 on a server and tried the @Starburst installer:
https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-install-tutorials/updated-cwp-installer-script-for-almalinux-8-with-mariadb-10-6/
It didn't work.
The server had Almalinux 8 installed and updated; nothing else was installed.
I started the CWP installation and was already seeing some errors. At one point, it stopped. I'll paste the last few lines:
So, for now, a clean install, from what I can see or from my experience, should be done through the CWP installer. We followed the instructions to update MariaDB, but right when we installed MariaDB 10.11 (or 10.6, whichever version you prefer), we deactivated the CWP repo, installed MariaDB, and after it was installed, we reactivated the CWP repo.
By the way, thanks @Starburst for your work here...
I performed a clean install of AlmaLinux 8 on a server and tried the @Starburst installer:
https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-install-tutorials/updated-cwp-installer-script-for-almalinux-8-with-mariadb-10-6/
It didn't work.
The server had Almalinux 8 installed and updated; nothing else was installed.
I started the CWP installation and was already seeing some errors. At one point, it stopped. I'll paste the last few lines:
Code: [Select]
Transaction Summary
==============================================================================================================================================================================================
Install 2 Packages
Total download size: 954 k
Installed size: 2.9 M
Downloading Packages:
(1/2): gpm-libs-1.20.7-17.el8.x86_64.rpm 451 kB/s | 38 kB 00:00
(2/2): elinks-0.12-0.58.pre6.el8.x86_64.rpm 3.3 MB/s | 916 kB 00:00
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 1.0 MB/s | 954 kB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : gpm-libs-1.20.7-17.el8.x86_64 1/2
Running scriptlet: gpm-libs-1.20.7-17.el8.x86_64 1/2
Installing : elinks-0.12-0.58.pre6.el8.x86_64 2/2
Running scriptlet: elinks-0.12-0.58.pre6.el8.x86_64 2/2
Verifying : gpm-libs-1.20.7-17.el8.x86_64 1/2
Verifying : elinks-0.12-0.58.pre6.el8.x86_64 2/2
Installed:
elinks-0.12-0.58.pre6.el8.x86_64 gpm-libs-1.20.7-17.el8.x86_64
Complete!
Last metadata expiration check: 0:01:48 ago on Fri 24 Oct 2025 09:58:48 PM CEST.
Dependencies resolved.
Nothing to do.
Complete!
PREPARING THE SERVER
##########################
Failed to stop firewalld.service: Unit firewalld.service not loaded.
Failed to disable unit: Unit file firewalld.service does not exist.
#############################################
Please wait... installing web server files...
#############################################
Last metadata expiration check: 0:01:52 ago on Fri 24 Oct 2025 09:58:48 PM CEST.
No match for argument: cwp-httpd
Error: Unable to find a match: cwp-httpd
Last metadata expiration check: 0:01:56 ago on Fri 24 Oct 2025 09:58:48 PM CEST.
No match for argument: cwp-suphp
Error: Unable to find a match: cwp-suphp
Compiler requires 512 MB RAM + SWAP
Installation FAILED at httpd
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 899 100 899 0 0 4181 0 --:--:-- --:--:-- --:--:-- 4181
sh: line 46: /usr/local/bin/php: No such file or directory
grep: /etc/init.d/httpd: No such file or directory
Received
Please contact CWP support about this issue and include the last few lines from the error:
http://centos-webpanel.com/contact
[root@server src]# So, for now, a clean install, from what I can see or from my experience, should be done through the CWP installer. We followed the instructions to update MariaDB, but right when we installed MariaDB 10.11 (or 10.6, whichever version you prefer), we deactivated the CWP repo, installed MariaDB, and after it was installed, we reactivated the CWP repo.
By the way, thanks @Starburst for your work here...
22
Installation / Re: Problems installing CWP 8 with MariaDB
« on: October 24, 2025, 04:59:16 PM »
Hello,
Yes, it is indeed a genuine EL8 distribution, AlmaLinux8 in question.
I've installed a server, installed AlmaLinux 8 from scratch, and installed CWP from the official CWP repo (I'll do it later from the one mentioned by Startburst, but I wanted to note that we're using the official CWP repo and instructions).
After installing CWP and running a yum update, we have this:
https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/#comment-25
disabling cwp repo:
And the rest of the steps are perfect.
By the way, I've used both the one indicated in the URL and the one @starburst mentioned as repos with the same result; the problem isn't the mariadb repository.
Then, in a few hours, I'll run the same tests using the CWP installer created by @starburst and post them here.
Yes, it is indeed a genuine EL8 distribution, AlmaLinux8 in question.
I've installed a server, installed AlmaLinux 8 from scratch, and installed CWP from the official CWP repo (I'll do it later from the one mentioned by Startburst, but I wanted to note that we're using the official CWP repo and instructions).
After installing CWP and running a yum update, we have this:
Code: [Select]
[root@server ~]# yum update
CentOS Web Panel repo for Linux 8 - x86_64 3.0 MB/s | 330 kB 00:00
AlmaLinux 8 - BaseOS 16 MB/s | 44 MB 00:02
AlmaLinux 8 - AppStream 3.1 MB/s | 21 MB 00:06
AlmaLinux 8 - Extras 34 kB/s | 14 kB 00:00
AlmaLinux 8 - PowerTools 7.1 MB/s | 5.0 MB 00:00
AlmaLinux 8 - PowerTools Source 357 kB/s | 142 kB 00:00
AlmaLinux 8 - PowerTools debuginfo 1.6 MB/s | 854 kB 00:00
Extra Packages for Enterprise Linux 8 - x86_64 7.1 MB/s | 14 MB 00:01
Error:
Problem 1: package MariaDB-shared-10.5.29-1.el8.x86_64 from cwp requires MariaDB-common, but none of the providers can be installed
- cannot install the best update candidate for package mariadb-connector-c-3.1.11-2.el8_3.x86_64
- package MariaDB-common-10.5.29-1.el8.x86_64 from cwp is filtered out by modular filtering
Problem 2: package MariaDB-shared-10.5.29-1.el8.x86_64 from cwp requires MariaDB-common, but none of the providers can be installed
- cannot install the best update candidate for package mariadb-connector-c-config-3.1.11-2.el8_3.noarch
- package MariaDB-common-10.5.29-1.el8.x86_64 from cwp is filtered out by modular filtering
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
[root@server ~]#
I followed the instructions at this URL step by step as shown below.https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/#comment-25
Code: [Select]
[root@server ~]# cp /etc/my.cnf /etc/my.cnf.bak
[root@server ~]# systemctl stop mariadb mysql mysqld
[root@server ~]# systemctl disable mariadb
Removed /etc/systemd/system/multi-user.target.wants/mariadb.service.
Removed /etc/systemd/system/mysql.service.
Removed /etc/systemd/system/mysqld.service.
[root@server ~]# rpm -e --nodeps $(rpm -qa | grep -i mariadb)
[root@server ~]# rpm -e --nodeps mysql-common mysql-libs mysql-devel
error: package mysql-common is not installed
error: package mysql-libs is not installed
error: package mysql-devel is not installed
[root@server ~]# rpm --nodeps -ev MariaDB-server
error: package MariaDB-server is not installed
[root@server ~]# dnf module disable mariadb -y
Last metadata expiration check: 0:04:12 ago on Fri 24 Oct 2025 06:27:29 PM CEST.
Dependencies resolved.
==============================================================================================================================================================================================
Package Architecture Version Repository Size
==============================================================================================================================================================================================
Disabling modules:
mariadb
Transaction Summary
==============================================================================================================================================================================================
Complete!
[root@server ~]# rpm -e --nodeps mariadb-server
error: package mariadb-server is not installed
[root@server ~]# nano /etc/yum.repos.d/mariadb.repo
[root@server ~]# yum clean all
62 files removed
[root@server ~]# yum install MariaDB-server MariaDB-client MariaDB-devel MariaDB-shared net-snmp perl-DBD-MySQL -y
CentOS Web Panel repo for Linux 8 - x86_64 3.1 MB/s | 330 kB 00:00
AlmaLinux 8 - BaseOS 15 MB/s | 44 MB 00:02
AlmaLinux 8 - AppStream 15 MB/s | 21 MB 00:01
AlmaLinux 8 - Extras 34 kB/s | 14 kB 00:00
AlmaLinux 8 - PowerTools 7.6 MB/s | 5.0 MB 00:00
AlmaLinux 8 - PowerTools Source 334 kB/s | 142 kB 00:00
AlmaLinux 8 - PowerTools debuginfo 1.8 MB/s | 854 kB 00:00
Extra Packages for Enterprise Linux 8 - x86_64 7.9 MB/s | 14 MB 00:01
MariaDB 1.6 MB/s | 634 kB 00:00
Package perl-DBD-MySQL-4.046-3.module_el8.6.0+2827+49d66dc3.x86_64 is already installed.
Error:
Problem: package MariaDB-server-10.11.14-1.el8.x86_64 from mariadb requires MariaDB-client >= 10.6.1, but none of the providers can be installed
- cannot install both MariaDB-client-10.11.11-1.el8.x86_64 from mariadb and MariaDB-client-10.5.29-1.el8.x86_64 from cwp
- cannot install both MariaDB-client-10.11.13-1.el8.x86_64 from mariadb and MariaDB-client-10.5.29-1.el8.x86_64 from cwp
- cannot install both MariaDB-client-10.11.14-1.el8.x86_64 from mariadb and MariaDB-client-10.5.29-1.el8.x86_64 from cwp
- cannot install the best candidate for the job
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
[root@server ~]#
The only way I can find to solve it is by disabling the CWP repo at that point, then it updates without any problem, but it installs some more package, which I really don't know if it's necessary:disabling cwp repo:
Code: [Select]
Installing:
MariaDB-client x86_64 10.11.14-1.el8 mariadb 16 M
MariaDB-devel x86_64 10.11.14-1.el8 mariadb 8.5 M
MariaDB-server x86_64 10.11.14-1.el8 mariadb 28 M
MariaDB-shared x86_64 10.11.14-1.el8 mariadb 128 k
net-snmp x86_64 1:5.8-31.el8_10 appstream 355 k
Installing dependencies:
MariaDB-common x86_64 10.11.14-1.el8 mariadb 88 k
boost-program-options x86_64 1.66.0-13.el8 appstream 140 k
galera-4 x86_64 26.4.23-1.el8 mariadb 1.5 M
net-snmp-agent-libs x86_64 1:5.8-31.el8_10 appstream 749 k
net-snmp-libs x86_64 1:5.8-31.el8_10 baseos 827 k
Installing weak dependencies:
lsof x86_64 4.93.2-1.el8 baseos 252 k
pv x86_64 1.6.6-7.el8 epel 64 k
socat x86_64 1.7.4.1-2.el8_10 appstream 322 k
Transaction Summary
And the rest of the steps are perfect.
By the way, I've used both the one indicated in the URL and the one @starburst mentioned as repos with the same result; the problem isn't the mariadb repository.
Then, in a few hours, I'll run the same tests using the CWP installer created by @starburst and post them here.
23
Installation / Problems installing CWP 8 with MariaDB
« on: October 24, 2025, 08:00:16 AM »
This week I installed CWP 8 from scratch, and I had to do it several times on the same server.
My mistake for not noting and saving the error.
The error appears once installed. It installs MariaDB 10.5, and when you run a yum update, it gives a result similar to this (because I searched for it and it appeared):
Copied from other post but equal than my problem:
yum update
Last metadata expiration date check: 0:05:32 ago on Sat 17 May 2025 14:34:10 UTC. Mistake:
Problem 1: package MariaDB-shared-10.5.29-1.el8.x86_64 from mariadb requires MariaDB-common, but none of the providers can be installed
- cannot install the best update candidate for package mariadb-connector-c-3.1.11-2.el8_3.x86_64
- package MariaDB-common-10.5.27-1.el8.x86_64 from mariadb is filtered out by modular filtering
- package MariaDB-common-10.5.28-1.el8.x86_64 from mariadb is filtered out by modular filtering
- package MariaDB-common-10.5.29-1.el8.x86_64 from mariadb is filtered out by modular filtering
Problem 2: package MariaDB-shared-10.5.29-1.el8.x86_64 from mariadb requires MariaDB-common, but none of the providers can be installed
- cannot install the best update candidate for package mariadb-connector-c-config-3.1.11-2.el8_3.noarch
- package MariaDB-common-10.5.27-1.el8.x86_64 from mariadb is filtered out by modular filtering
- package MariaDB-common-10.5.28-1.el8.x86_64 from mariadb is filtered out by modular filtering
- package MariaDB-common-10.5.29-1.el8.x86_64 from mariadb is filtered out by modular filtering
(try adding '--skip-broken' to skip uninstallable packages or '--nobest' to use not only the best candidate packages)
I read the link mentioned and it takes us Here:
https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/#comment-25
But it doesn't fix it. In my case, it never fixed it; I always had the same problem.
Finally, I was able to fix it (I don't remember exactly how; I was stressed because the production server had crashed).
Now, cwp detects two pending updates. I log in and none appear. Yum update indicates that neither does it. But I see that the latest kernel, although apparently installed, isn't activated even in GRUB. I'm not worried; it will be updated with the next kernel released.
The problem is mariadb in a clean install. I think the installation script should be changed. It's not easy to fix the problem of having version 10.5 and then having yum update not work.
My mistake for not noting and saving the error.
The error appears once installed. It installs MariaDB 10.5, and when you run a yum update, it gives a result similar to this (because I searched for it and it appeared):
Copied from other post but equal than my problem:
yum update
Last metadata expiration date check: 0:05:32 ago on Sat 17 May 2025 14:34:10 UTC. Mistake:
Problem 1: package MariaDB-shared-10.5.29-1.el8.x86_64 from mariadb requires MariaDB-common, but none of the providers can be installed
- cannot install the best update candidate for package mariadb-connector-c-3.1.11-2.el8_3.x86_64
- package MariaDB-common-10.5.27-1.el8.x86_64 from mariadb is filtered out by modular filtering
- package MariaDB-common-10.5.28-1.el8.x86_64 from mariadb is filtered out by modular filtering
- package MariaDB-common-10.5.29-1.el8.x86_64 from mariadb is filtered out by modular filtering
Problem 2: package MariaDB-shared-10.5.29-1.el8.x86_64 from mariadb requires MariaDB-common, but none of the providers can be installed
- cannot install the best update candidate for package mariadb-connector-c-config-3.1.11-2.el8_3.noarch
- package MariaDB-common-10.5.27-1.el8.x86_64 from mariadb is filtered out by modular filtering
- package MariaDB-common-10.5.28-1.el8.x86_64 from mariadb is filtered out by modular filtering
- package MariaDB-common-10.5.29-1.el8.x86_64 from mariadb is filtered out by modular filtering
(try adding '--skip-broken' to skip uninstallable packages or '--nobest' to use not only the best candidate packages)
I read the link mentioned and it takes us Here:
https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/#comment-25
But it doesn't fix it. In my case, it never fixed it; I always had the same problem.
Finally, I was able to fix it (I don't remember exactly how; I was stressed because the production server had crashed).
Now, cwp detects two pending updates. I log in and none appear. Yum update indicates that neither does it. But I see that the latest kernel, although apparently installed, isn't activated even in GRUB. I'm not worried; it will be updated with the next kernel released.
The problem is mariadb in a clean install. I think the installation script should be changed. It's not easy to fix the problem of having version 10.5 and then having yum update not work.
24
CSF Firewall / Re: CSF Auto Update Re-Enabled v14.24 and v15.00
« on: September 16, 2025, 01:25:19 PM »I apologize about that, got the mirror's pages fixed.
Saw other links that where spelled OK, but the hyperlink's were all jinxed.
No problem

Thanks for fixing them and checking out the others

Thanks to you!
25
CSF Firewall / Re: CSF Auto Update Re-Enabled v14.24 and v15.00
« on: September 15, 2025, 08:32:22 PM »Config.pm lists a Backup server.
In downloadservers, it doesn't matter what 2 servers are used.
Again, sorry for the delay in replying.
I understand.
On one server, I configured download servers with:
download.cs.stl.us.ssimn.org
download.gb.ssimn.org
Following your mirror links, I picked the second one from the UK, but it contained an error. The next day I received this email:
"Oops: Unable to download: Can't connect to download.gb.ssimn.org:443 (Name or service not known)"
I changed it to:
download.cs.gb.ssimn.org
And it was fixed.
Thanks
26
CSF Firewall / Re: CSF Auto Update Re-Enabled v14.24 and v15.00
« on: September 10, 2025, 11:19:22 PM »
@Starburst
I've made the changes according to your guide, but I have a question:
Where you specify:
nano /etc/csf/downloadservers
and we set up two servers, for example, OK.
But then, here:
nano /usr/local/csf/lib/ConfigServer/Config.pm
if ($chosen eq “”) {$chosen = “One.Server.only”}
We only set up one server. Does it matter which of the two download servers we set up?
I've made the changes according to your guide, but I have a question:
Where you specify:
nano /etc/csf/downloadservers
and we set up two servers, for example, OK.
But then, here:
nano /usr/local/csf/lib/ConfigServer/Config.pm
if ($chosen eq “”) {$chosen = “One.Server.only”}
We only set up one server. Does it matter which of the two download servers we set up?
27
CSF Firewall / Re: CSF Auto Update Re-Enabled v14.24 and v15.00
« on: September 08, 2025, 05:46:45 PM »I'm not sure what CWP plans are, CSF still lives as open source.
We had an international mirror network already setup for ELRepo, so it was semi-easy for us to add ConfigServer to offer auto updates.
v15.00 is the first release under open source, and removes the closed companies 2 download servers.
This article will advise you how to re-enable auto updates:
https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/csf-firewall-error-oops-unable-to-download-no-host-option-provided/
You can choose 2 download servers from our mirror list at:
https://starburstservices.com/downloads/mirrors-list/
First of all, thanks for your response, as always!
Sorry for the delay in replying. I didn't receive the notification email, and I've been short on time for everything these days.
With what you've said, I think I'm clear on this. I'm going to upgrade from 14.24 to 15.00 and activate Auto Update by following the link you provided. There are several mirrors, and it's perfect.
Thanks for the work!
28
CSF Firewall / Re: CSF Auto Update Re-Enabled v14.24 and v15.00
« on: September 03, 2025, 11:02:35 PM »Please reference: https://starburst.help/control-web-panel-cwp/control-web-panel-cwp-admin-tutorials/csf-firewall-error-oops-unable-to-download-no-host-option-provided/
It has been tested on v14.24 and v15.00 on AlmaLinux 8 / 9 and Debian.
Mirrors are also all updated, and verified working.
Great work, information, and article/guide, thank you.
At this point, would you be able to tell if this is the system CWP is going to implement?
I have one server that I can implement, but another that I always have to keep in a stable version (so to speak).
29
Migration from other control panels / Re: AlmaLinux 8 CWP -> AlmaLinux 9 CWP Migration
« on: June 07, 2025, 07:59:25 AM »
Sorry for bumping this thread. I had the same problem in the past. Has this issue/bug been resolved yet?
I want to migrate from CWP8 to CWP9 (Alma 8 to Alma9), and I don't know if this issue is resolved.
If it is, I'll get a VPS now, but if it isn't... I won't spend the money on a new VPS...
Thanks.
I want to migrate from CWP8 to CWP9 (Alma 8 to Alma9), and I don't know if this issue is resolved.
If it is, I'll get a VPS now, but if it isn't... I won't spend the money on a new VPS...
Thanks.
30
CentOS 8 Problems / Re: Can not install CWP 8 on Rockylinux 8 or Almalinux 8
« on: March 15, 2025, 04:40:09 PM »I've used the CWP script for installs on AL9 without any problem, as long as you load some of the dependances like I put in the AL9 setup I've posted here in the forums.Yes, I've read some of what you posted. I installed it (the script for AL9) without making any changes. When I get back to it, I'll look for your posts to see those changes.
My question was regarding the script for AL8. You made the appropriate changes due to the problem mentioned in this thread, but I don't know if the default CWP script already has those changes.
I need to take the plunge and install AL9, but I need to know if it's possible to transfer a CWP account from AL8 to AL9. When I tried it, it didn't work...
Thanks for the reply.
