Introduction
This article will show how to solve an error message appear upon configuring metabase. This article has a connection with the previous article. That article is focusing on how to configure metabase further after the installation. The article exist in this link with the title of ‘How to Configure Metabase in Linux CentOS 8’. Upon connecting metabase to the database, it accidentally generate error message exist below :

The error message is in the following line :
Database name : No matching clause: Could not connect to address=(host=localhost)(port=3306)(type=master):(conn=13) Access denied for user 'metabase'@'localhost' (using password:YES) Current charset is UTF-8. If password has been set using other charset, consider using option 'passwordCharacterEncoding'
So, this article is about how to solve the error message in the previous image and also in the above line.
Solution
The solution to solve the error message appear in the previous part is simple. Apparently, in general there is a problem with the connection from metabase to the database. It is actually part of the previous article with the title of ‘How to Configure Metabase in Linux CentOS 8’ in this link.
Basically, the step for solving the problem is just to check the database configuration connection once more. But in the case of the errror message above, apparently there is no database connection available. So, the error message appear because the step for database connection in the article with the title of ‘How to Configure Metabase in Linux CentOS 8’ in this link is skipped.
Normally, create the database connection to MySQL before filling the metabase database connection configuration form. But if the step is skipped or the database connection configuration is wrong, the error appear. It is clearly available in the SQL error message of the following line :
Access denied for user 'metabase'@'localhost' (using password:YES) Current charset is UTF-8. If password has been set using other charset, consider using option 'passwordCharacterEncoding'
So, the solution is obvious :
- Access the database. In this case it is a MySQL or MariaDB database server.
- Create database, user and the grant rule for the user to the database if it is not available.
- Correct the grant rule for the user so that it can access and perform operation on the database.