MySQL Forums
Forum List  »  MySQL Workbench

Re: Upgrade my MySql Workbench 6.3.4 to 8.x fails in db connect
Posted by: João Paulo Oliveira
Date: May 22, 2020 02:20PM

I am just starting to use MySQL database.
I have installed version 8.0.20 of the mysql server on a Ubuntu 18.04 system. I have checked, using the command line, that I am able to use the server with the root user with a password and using the 'caching_sha2_password' authentication.
The mysqladmin command reports that the connection to Localhost is done via UNIX socket. It uses the one in /var/run/mysqld/mysqld.sock.

I have entered those options in the mysql workbench (version 8.0.20) and I get the same results reported previously. The results from the log file are:

20:05:55 [ERR][SQL Editor Form]: SqlEditorForm: exception in do_connect method: Exception: Wrong or unknown protocol
20:05:55 [ERR][ GRTDispatcher]: exception in grt execute_task, continuing: Exception: Wrong or unknown protocol
20:05:55 [ERR][ GRTDispatcher]: worker: task 'execute sql queries' has failed with error:.Wrong or unknown protocol
20:05:55 [ERR][ WQE backend]: Got an exception during connection: Wrong or unknown protocol
20:05:55 [ERR][SQL Editor Form]: SQL editor could not be connected: Wrong or unknown protocol
20:05:55 [ERR][SQL Editor Form]: Your connection attempt failed for user 'root' to the MySQL server at localhost:NULL:
Wrong or unknown protocol

1 Check that MySQL is running on address localhost
2 Check that MySQL is reachable on port NULL (note: 3306 is the default, but this can be changed)
3 Check the user root has rights to connect to localhost from your address (MySQL rights define what clients can connect to the server and from which machines)
4 Make sure you are both providing a password if needed and using the correct password for localhost connecting from the host address you're connecting from.

Options: ReplyQuote

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.