it works for me too on a fresh VM. The problem is on the production VM and I don’t know where to look or how to fix it. The modules are installed but Virtualmin somehow doesn’t recognize that. Is there anyway to repair virtualmin?
Start by analyzing the output of the following commands:
dnf clean all
dnf repolist
dnf install php-mysqlnd
Well, I have already done these.
[root@vwm ~]# dnf clean all
118 files removed
[root@vwm ~]# dnf repolist
repo id repo name
appstream AlmaLinux 9 - AppStream
baseos AlmaLinux 9 - BaseOS
elevate ELevate
epel Extra Packages for Enterprise Linux 9 - x86_64
epel-cisco-openh264 Extra Packages for Enterprise Linux 9 openh264 (From Cisco) - x86_64
extras AlmaLinux 9 - Extras
mariadb-main MariaDB Server
mariadb-maxscale MariaDB MaxScale
mariadb-tools MariaDB Tools
ookla_speedtest-cli ookla_speedtest-cli
ookla_speedtest-cli-source ookla_speedtest-cli-source
remi-modular Remi's Modular repository for Enterprise Linux 9 - x86_64
remi-safe Safe Remi's RPM repository for Enterprise Linux 9 - x86_64
virtualmin Virtualmin 7 - x86_64
virtualmin-noarch Virtualmin 7 GPL - noarch
webmin-noarch Webmin - noarch
zabbix Zabbix Official Repository - x86_64
zabbix-non-supported Zabbix Official Repository non-supported - x86_64
[root@vwm ~]# dnf install php-mysqlnd
ELevate 109 kB/s | 97 kB 00:00
AlmaLinux 9 - AppStream 3.8 MB/s | 12 MB 00:03
AlmaLinux 9 - BaseOS 4.2 MB/s | 11 MB 00:02
AlmaLinux 9 - Extras 19 kB/s | 20 kB 00:01
Extra Packages for Enterprise Linux 9 - x86_64 4.5 MB/s | 23 MB 00:05
Extra Packages for Enterprise Linux 9 openh264 (From Cisco) - x86_64 2.0 kB/s | 2.5 kB 00:01
MariaDB Server 219 kB/s | 734 kB 00:03
MariaDB MaxScale 3.7 kB/s | 6.9 kB 00:01
MariaDB Tools 39 kB/s | 25 kB 00:00
ookla_speedtest-cli 131 B/s | 972 B 00:07
ookla_speedtest-cli-source 58 B/s | 296 B 00:05
Remi's Modular repository for Enterprise Linux 9 - x86_64 628 kB/s | 677 kB 00:01
Safe Remi's RPM repository for Enterprise Linux 9 - x86_64 1.2 MB/s | 1.0 MB 00:00
Virtualmin 7 - x86_64 6.5 kB/s | 5.5 kB 00:00
Virtualmin 7 GPL - noarch 839 kB/s | 694 kB 00:00
Webmin - noarch 477 kB/s | 2.6 MB 00:05
Zabbix Official Repository - x86_64 99 kB/s | 296 kB 00:02
Zabbix Official Repository non-supported - x86_64 619 B/s | 1.1 kB 00:01
Package php-mysqlnd-8.2.23-1.el9.remi.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
[root@vwm ~]#
You should follow our guide to install additional PHP versions:
The default PHP version on Alma 9 is 8.0. If you changed it to 8.2 using the module subcommand, revert it first by running:
dnf module reset php
I installed 8.2 using the terminal. By the way, the VM was elevated from Centos 7. Can’t be related, right? There are no centos 7 packages or repos as far as I checked (I removed them). Virtualmin though was installed before it was elevated to alma 9.
We don’t know! This is something only the server admin can know. However, I would never recommend cross-upgrading. It’s much cleaner to spin up a new Alma or Rocky 9 instance and perform a migration.
Thanks a lot for your time guys! I will probably migrate the hosting services to a new VM.
The message here about it being a “required” module is confusing - I’ll fix that.
But this is a required module! Though, we show a different message for auxiliary PHP modules …
That’s ridiculous, it absolutely is not required. Our very own website runs without it, and it does not exist on any modern distribution we support, and there are tens of thousands, maybe hundreds of thousands, of WordPress installs on those systems.
e.g. a system with a working WordPress installation:
$ rpm -qa|grep mysql|grep php
php81-php-mysqlnd-8.1.29-2.el8.remi.x86_64
php-mysqlnd-7.2.24-1.module+el8.4.0+413+c9202dda.x86_64
php80-php-mysqlnd-8.0.30-8.el8.remi.x86_64
php74-php-mysqlnd-7.4.33-17.el8.remi.x86_64
I meant php-mysqlnd module.
@Joe, please see my actual fix above.
It’s required, though we didn’t request the right module name! 
So, I finally figured out why it wasn’t working (didn’t want to give up and just migrate to a fresh VM). After I disabled mailing for the new virtual server. It has successfully installed wordpress on creation. This was the 2nd attempt to install it. On the first one it installed the required php modules (not sure what happened there). If I keep mailing for server enabled, it will still give the same error.
Saving server details …
… done
Creating administration group test …
… done
Creating administration user test …
… done
Adding administration user to groups …
… done
Creating home directory …
… done
Creating mailbox for administration user …
… done
Adding new virtual website …
… done
Setting up CGI scripts support with FCGIwrap server execution mode …
… done
Adding webserver user apache to server’s group …
… done
Performing other Apache configuration …
… done
Creating SSL certificate and private key …
… done
Adding new SSL virtual website …
… done
Setting up log file rotation …
… done
Creating MariaDB login …
… done
Creating MariaDB database dbtest …
… done
Setting up AWStats reporting …
… done
Setting up password protection for AWStats …
… done
Creating Webmin user …
… done
Saving server details …
… done
Applying webserver configuration …
… done
Restarting PHP-FPM 8.2 server …
… done
Re-loading Webmin …
… done
Re-starting Usermin …
… done
Restarting mail server …
… done
Updating Webmin user …
… done
Installing third-party web apps …
Installing wordpress version 6.6.1 …
Configuring webserver PHP settings …
… already done
Creating MariaDB database test.com_wordpress …
… done
… done. WordPress installation completed. It can be accessed at https://test.com/public_html/
… done
Setting up initial SSL certificate …
… keeping self-signed certificate
Setting up chroot jail …
… jail directory is now /home/chroot/17252930812942011
Creating initial website index page …
… done
Re-loading Webmin …
… done
Restarting PHP-FPM 8.2 server …
… done
1 Like
Still haven’t figure out why and how “accept mail for domain” interfere with the automatic installation of wordpress on server creation. Any clue where to look or what could be causing this?
How exactly does it interfere? Can you provide a screenshot of the error?
Its the same previous error, I have found that when I untick “accept mail for domain” on server creation, there are no errors on the automatic installation of wordpress. Its being installed normally. But when the “accept mail for domain” is ticked, it gives the same errors as stated before.
I figured out what interferes with “Mail for domain” option being enabled. It seems to be the “Mail Client Configuration” under Virtualmin → Email Settings → Mail Client Configuration. After disabling it, it worked. Any idea why?
Isn’t that a different issue to the original post, or is it the helping with the wordpress issue.
yes that fixed the wordpress issue