You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[mysql-async] [ERROR] ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client`
#177
Open
Almeidowski opened this issue
Jun 22, 2021
· 2 comments
Describe the bug
I'm getting this when trying to connect to mysql-async:
[mysql-async] [ERROR] ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client
To Reproduce
I'm using this in server.cfg:
set mysql_connection_string "server=localhost;database=portugalrpdb;userid=root;password=passpass"
start mysql-async
I'm using MySQL Workbench, instead of XAMPP, because that's what I'm more used to, but I'm still a beginner. Expected behavior
To connect to MySQL server. I don't know. I'm stil learning.
Screenshots / Logs
Software:
OS: Windows 10
Version of the resource: I downloaded it just today so I assume it's the latest recommended.
Database Version: I don't know, but I downloaded it from MySQL website.
Additional Information
I'm not using ESX.
The text was updated successfully, but these errors were encountered:
Yea depending on updates they release things like database sql software
needs updating so you work with a lower version now it will run super slow
at loading stuff
Describe the bug
I'm getting this when trying to connect to mysql-async:
[mysql-async] [ERROR] ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client
To Reproduce
I'm using this in server.cfg:
I'm using MySQL Workbench, instead of XAMPP, because that's what I'm more used to, but I'm still a beginner.
Expected behavior
To connect to MySQL server. I don't know. I'm stil learning.
Screenshots / Logs
Software:
Additional Information
I'm not using ESX.
The text was updated successfully, but these errors were encountered: