WordPress installation via script, management via WP Workbench fails with RDS SSL Connection (Error 1045)

[Ilia]

@keijo

Went to the MySQL module, selected the domain2_wordpress database and ran the SQL query from Virtualmin - domain2 → Edit Database → Execute SQL

That won’t have the same effect. You should su - domain_user, navigate to the WordPress installation directory, and then run it.

Something is failing here, on the side of the install script.

What makes you so confident? Could you please try the latest development version of Virtualmin to see if you still have this issue?

@keijo

If I use the host’s mysql client from ssh, it goes through. In any case, when I don’t specify the login has to go with SSL (and the attached CA certificate for the AWS region), it WILL fail like a user/password incorrect, and that’s what’s happening here.

As I mentioned earlier, you shouldn’t perform any additional SSL configuration beyond what Virtualmin does for you. At the very least, avoid doing it all at the same time—ensure one moving part is working before going on to the next.

[keijo]

@Ilia

That won’t have the same effect. You should su - domain_user, navigate to the WordPress installation directory, and then run it.

How can I run a wp command when wp doesn’t install from the script?

Out of frustration, I’ve reformatted/reinstalled the server from 0 (with some problems here as well, but could work around them after several retries), reconfigured RDS, and saw that root connects fine to it. I redid the first domain and it errors out just like it did the first time:

Now installing WordPress version 6.7.1 ..

`wp config create` failed : Error: Database connection error (1045) Access denied for user 'ddomain1'@'ipaddress' (using password: YES)
Installation can be continued manually at [https://domain1.com/wp-admin].

Installation can be continued manually at *https://domain1.com/*
More information on using this web app can be found at http://wordpress.org/

.. installation was only partially complete.

Re-loading Webmin ..
.. done

and wp db query "SHOW STATUS LIKE 'Ssl_cipher';" shows nothing, since it’s not installed:

domain1@webserver:~/public_html$ wp db query "SHOW STATUS LIKE 'Ssl_cipher';" wp: command not found

My last resort is to go full-monolithic and ditch the RDS in favor of the local MariaDB, but my boss (and the compliance dept) won’t like it. At least I have it all documented here

On a final note, it could be that the ‘root’ perms on the RDS may be borked somehow, but if I go on and continue setting this up via the proposed URL, thus editing the SSL parameters in wp-config, it will work, but WP Workbench will keep complaining on that DB error anyway, plus the second domain will fail completely. Been there, done that. Plan C: Monolithic!

Thanks.-