What Should I Do If I Can't Connect to My GaussDB(for MySQL) Instance?

1. Error cause: The username or password of the GaussDB(for MySQL) instance is incorrect.
   Solution: Check whether the username and password are correct. If you are not sure, log in to the GaussDB(for MySQL) console to view the username and reset the password.

   

   Changing the password may affect services.

   If the username and password are correct, log in to the database using a client or CLI tool and run select * from mysql.user where user = 'user_name' to view the account. Make sure that the DAS CIDR block is within the CIDR block of the user. user_name @ % and user_name @100.% are two different users whose passwords and permissions are independent. Make sure to enter the password of user user_name @100.%.

2. Error cause: The IP address of the DAS server is not in the whitelist of the login user.
   Solution: Log in to the database using the client or CLI tool, and create a user that can be used to access the database through DAS.

   create user 'user_name'@'100.%' identified by 'password';
   grant all privileges on *.* to 'user_name'@'100.%';

   

   1. Ensure that the IP address of the DAS server is in a CIDR block starting with 100. Add the IP address to the whitelist of the login user.
   2. Grant permissions to user user_name@100.% based on service requirements.

Error cause: The SSL function is not enabled on the server.

Solution: Run the following SQL statement to check whether the user is an SSL user. If yes, enable SSL on the GaussDB(for MySQL) instance details page. The user is an SSL user if the ssl_type field has a value.

select user, host, ssl_type from mysql.user where user = 'user_name';

Error cause: DAS does not allow you to connect to the database whose password is encrypted with SHA-256.

Solution: Execute the following SQL statements to change the password encryption method to mysql_native_password.

alter user 'user_name'@'%' identified with mysql_native_password by 'password';

Error cause: The network between the DAS server and the instance is disconnected.

Solution: Contact technical support.