• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Installation of WordPress at ... failed. Database user name is invalid.

AaronMcH

New Pleskian
While trying to install WordPress on a website using the Application Catalogue, several errors appeared one after the o ther, I followed steps in each article linked below to fix each error:
After solving the above errors, I am now faced with the error "Installation of WordPress at https://testdomain.test/ failed. Database user name is invalid.", in /var/log/plesk/panel.log an error saying "FIXME: database type is not supported."

Our MySQL Server version is 5.7.18, could this be the issue?

Thank you
Aaron
 
Hi AaronMcH,

pls. note, that the following database - servers are supported by Plesk ( => Software Requirements for Plesk ):

Hello thanks for the reply

This is not solved, as I mentioned in my original post we are running MySQL 5.7, so obviously there is an issue here. It's also as if Plesk wasn't able to detect which version of MySQL we are running, since the error "FIXME: database type is not supported.", and there were two spaces between "type" and "is", suggesting it was supposed to insert a version number or something here.
 
Hi AaronMcH,

pls. what are the outputs of the commands ( logged in as user "root" over SSH ):
Code:
mysql -V

and

mysql -uadmin -p`cat /etc/psa/.psa.shadow`

In addition, pls. add as well the output of the command:
Code:
plesk version
 
Hello thanks for the reply

For each command:

mysql -V
mysql Ver 14.14 Distrib 5.7.18, for Linux (x86_64) using EditLine wrapper

mysql -uadmin -p`cat /etc/psa/.psa.shadow`
Opens the MySQL Terminal

plesk version
Product version: Plesk Onyx 17.5.3 Update #10
Update date: 2017/06/22 13:59
Build date: 2017/03/17 16:00
OS version: CentOS 6.9
Revision: 55d1b49a272f44666e1920eca8b6e4da449a38cd
Architecture: 64-bit
Wrapper version: 1.2
 
mysql -uadmin -p`cat /etc/psa/.psa.shadow`
Opens the MySQL Terminal
Correct... pls copy&paste the informations, that you get from your mysql - server, for further investigations! ;)

(shortened example):
Code:
Welcome to the MySQL monitor.  Commands end with ; or \g.
...
...
...
...



Pls. consider as well to inform us about the output of the command:
Code:
dpkg --get-selections | grep mysql
 
Last edited by a moderator:
Correct... pls copy&paste the informations, that you get from your mysql - server, for further investigations! ;)

(shortened example):
Code:
Welcome to the MySQL monitor.  Commands end with ; or \g.
...
...
...
...

There's no other useful information, it's simply just the version information (already provided), and copyright notices, as one would expect.

Pls. consider as well to inform us about the output of the command:
Code:
dpkg --get-selections | grep mysql

Given that we're running CentOS (as shown above by running plesk version command) I'll use rpm instead:

rpm -qa | grep mysql
mysql-community-client-5.7.18-1.el6.x86_64
mysql-community-server-5.7.18-1.el6.x86_64
plesk-php70-mysql-7.0.20-centos6.17060816.x86_64
plesk-php56-mysql-5.6.30-centos6.17031314.x86_64
mysql57-community-release-el6-10.noarch
mysql-connector-odbc-5.3.8-1.el6.x86_64
plesk-php53-mysql-5.3.29-centos6.15102117.x86_64
plesk-php52-mysql-5.2.17-centos6.15100614.x86_64
php-mysql-5.3.3-49.el6.x86_64
mysql-community-libs-compat-5.7.18-1.el6.x86_64
mysql-community-libs-5.7.18-1.el6.x86_64
plesk-php55-mysql-5.5.38-centos6.17031317.x86_64
plesk-php54-mysql-5.4.45-centos6.16032517.x86_64
plesk-php71-mysql-7.1.6-centos6.17060817.x86_64
plesk-mysql-server-17.5.3-cos6.build1705170317.16.x86_64
mysql-community-common-5.7.18-1.el6.x86_64
 
Hi AaronMcH,

Given that we're running CentOS (as shown above by running plesk version command) I'll use rpm instead:
sorry... my fault... ( I'm more the Debian/Ubuntu - man ^^ ... that's why I try to call for a CentOS - specialist now, by mentioning @Peter Debik here in the thread ).


Edit: After writing with @Peter Debik, we both came to the same conclusion, that it might be better, to get in contact with the Plesk Support ( => Contact Support - Plesk ), as it is unclear, what sort of previous mysql - installation/de- installation /modification you made on your server and deeper investigations should be done.
 
Last edited by a moderator:
My first guess is that maybe several database servers are installed and active.
Tools & Settings > Applications & Database: What are the servers listed there?
And maybe check
# netstat -plnt | grep 'sql'
whether there might be several servers listening.
 
Back
Top