Bug #104256 Workbench cannot connect to database server
Submitted: 9 Jul 2021 0:43 Modified: 17 Jul 2021 5:20
Reporter: Horacio Flores Gomez Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:8.0.25 OS:Windows (Microsoft Windows 10 Home Single Language)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[9 Jul 2021 0:43] Horacio Flores Gomez
Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\123\AppData\Roaming\MySQL\Workbench\log\wb.log]

I receibed this message in first page of the workbench:
Cannot Connect to Database Server
Your connection attempt failed for user 'root' to the MySQL server at localhost:3306:
SSL connection error: Failed to set ciphers to use

How to repeat:
Just start the workbench application and click on MySQL Connections Local Instance MySQL80

wb.log

17:43:05 [ERR][      Workbench]: Console redirection failed.
17:43:05 [INF][      Workbench]: Starting up Workbench
17:43:05 [INF][      Workbench]: Current environment:
	Command line: "C:\Program Files\MySQL\MySQL Workbench 8.0\MySQLWorkbench.exe" 
	CurrentDirectory: C:\Program Files\MySQL\MySQL Workbench 8.0
	HasShutdownStarted: False
	OSVersion: Microsoft Windows NT 6.2.9200.0
	SystemDirectory: C:\WINDOWS\system32
	TickCount: 65277343
	UserInteractive: True
	Version: 4.0.30319.42000
	WorkingSet: 51257344
17:43:05 [INF][      Workbench]: Environment variables:
	COMPUTERNAME = XPS8700
	USERPROFILE = C:\Users\123
	HOMEPATH = \Users\123
	LOCALAPPDATA = C:\Users\123\AppData\Local
	PSModulePath = C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
	PROCESSOR_ARCHITECTURE = AMD64
	CommonProgramW6432 = C:\Program Files\Common Files
	CommonProgramFiles(x86) = C:\Program Files (x86)\Common Files
	ProgramFiles(x86) = C:\Program Files (x86)
	PROCESSOR_LEVEL = 6
	LOGONSERVER = \\XPS8700
	PATHEXT = .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
	HOMEDRIVE = C:
	SystemRoot = C:\WINDOWS
	SESSIONNAME = Console
	ALLUSERSPROFILE = C:\ProgramData
	DriverData = C:\Windows\System32\Drivers\DriverData
	APPDATA = C:\Users\123\AppData\Roaming
	Path = C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\MySQL\MySQL Server 8.0\bin;C:\Program Files\MySQL\MySQL Shell 8.0\bin\;C:\Users\123\AppData\Local\Programs\Python\Python39\Scripts\;C:\Users\123\AppData\Local\Programs\Python\Python39\;C:\Users\123\AppData\Local\Microsoft\WindowsApps;C:\Users\123\.dotnet\tools
	USERNAME = 123
	OneDrive = C:\Users\123\OneDrive
	CommonProgramFiles = C:\Program Files\Common Files
	OS = Windows_NT
	USERDOMAIN_ROAMINGPROFILE = XPS8700
	PROCESSOR_IDENTIFIER = Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
	OneDriveConsumer = C:\Users\123\OneDrive
	USERDOMAIN = XPS8700
	SystemDrive = C:
	TEMP = C:\Users\123\AppData\Local\Temp
	ProgramFiles = C:\Program Files
	NUMBER_OF_PROCESSORS = 8
	ComSpec = C:\WINDOWS\system32\cmd.exe
	TMP = C:\Users\123\AppData\Local\Temp
	ProgramData = C:\ProgramData
	ProgramW6432 = C:\Program Files
	windir = C:\WINDOWS
	PROCESSOR_REVISION = 3c03
	PUBLIC = C:\Users\Public
17:43:05 [INF][      Workbench]: Current version given by meta info is: 8.0.25
17:43:05 [INF][      Workbench]: Setting PATH to: C:\WINDOWS\system32;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\MySQL\MySQL Server 8.0\bin;C:\Program Files\MySQL\MySQL Shell 8.0\bin\;C:\Users\123\AppData\Local\Microsoft\WindowsApps;C:\Users\123\.dotnet\tools
17:43:05 [INF][ mforms managed]: Initializing mforms wrapper
17:43:06 [INF][   WBContext UI]: Initializing workbench context UI with these values:
	base dir: C:\Program Files\MySQL\MySQL Workbench 8.0
	plugin path: C:\Program Files\MySQL\MySQL Workbench 8.0
	struct path: 
	module path: C:\Program Files\MySQL\MySQL Workbench 8.0/modules
	library path: C:\Program Files\MySQL\MySQL Workbench 8.0
	user data dir: C:\Users\123\AppData\Roaming\MySQL\Workbench
	open at start: 
	open type: 
	run at startup: 
	run type: 
	Force SW rendering: No
	Force OpenGL: No
	quit when done: No
17:43:06 [INF][      WBContext]: WbContext::init
17:43:07 [INF][            WBA]: Looking for extension modules for WBA...
17:43:07 [INF][            WBA]: 0 extension modules found
17:43:07 [WRN][            grt]: Duplicate plugin name wb.tools.cmdlineClient	There is more than one plugin with the name wb.tools.cmdlineClient (in PyWbUtils and PyWbUtils).
17:43:07 [WRN][            grt]: C:\Users\123\AppData\Roaming\MySQL\Workbench\connections.xml:32: link '{10DD9CF4-DD79-4D2D-8172-C057661877A0}' <object GrtObject> key=owner could not be resolved
17:43:07 [WRN][            grt]: Duplicate plugin name wb.tools.cmdlineClient	There is more than one plugin with the name wb.tools.cmdlineClient (in PyWbUtils and PyWbUtils).
17:43:07 [INF][      WBContext]: System info:
 	MySQL Workbench Community (GPL) for Windows version 8.0.25 CE build 788958 (64 bit)
	Configuration Directory: C:\Users\123\AppData\Roaming\MySQL\Workbench
	Data Directory: C:\Program Files\MySQL\MySQL Workbench 8.0
	Cairo Version: 1.17.4
	OS: Microsoft Windows 10 Home Single Language
	CPU: 8x Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 12.0 GiB RAM
	Active video adapter NVIDIA GeForce GTX 650 Ti
	Installed video RAM: 1024 MB
	Current video mode: 1824 x 1026 x 4294967296 colores
	Used bit depth: 32
	Driver version: 27.21.14.6109
	Installed display drivers: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3621da861144492b\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3621da861144492b\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3621da861144492b\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3621da861144492b\nvldumdx.dll
	Current user language: Español (México)

17:43:07 [INF][      Workbench]: UI is up
17:43:08 [INF][      Workbench]: Running the application
17:43:20 [INF][   WBContext UI]: Opening Migration Wizard...
17:43:20 [WRN][         mforms]: Resource file not found: migration_win.png
17:43:20 [WRN][            grt]: C:\Program Files\MySQL\MySQL Workbench 8.0/modules/data\msaccess_rdbms_info.xml:8: link 'com.mysql.rdbms.msaccess.driver.odbc' <object > key=defaultDriver could not be resolved
17:43:20 [WRN][            grt]: in com.mysql.rdbms.sql92.driver.odbc_dsn: unserialized XML contains invalid member db.mgmt.PythonDBAPIDriver::accessibilityNameLoaded 0/0 new non-MySQL connections
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:21 [WRN][         mforms]: Resource file not found: migration_check_open_win.png
17:43:48 [INF][   WBContext UI]: Opening Migration Wizard...
17:44:02 [ERR][SQL Editor Form]: SqlEditorForm: exception in do_connect method: Exception: SSL connection error: Failed to set ciphers to use
17:44:02 [ERR][  GRTDispatcher]: exception in grt execute_task, continuing: Exception: SSL connection error: Failed to set ciphers to use
17:44:02 [ERR][  GRTDispatcher]: worker: task 'execute sql queries' has failed with error:.SSL connection error: Failed to set ciphers to use
17:44:02 [ERR][    WQE backend]: Got an exception during connection: SSL connection error: Failed to set ciphers to use
17:44:02 [ERR][SQL Editor Form]: SQL editor could not be connected: SSL connection error: Failed to set ciphers to use
17:44:02 [ERR][SQL Editor Form]: Your connection attempt failed for user 'root' to the MySQL server at localhost:3306:
  SSL connection error: Failed to set ciphers to use

Please:
1 Check that MySQL is running on address localhost
2 Check that MySQL is reachable on port 3306 (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
17:44:47 [ERR][SQL Editor Form]: SqlEditorForm: exception in do_connect method: Exception: SSL connection error: Failed to set ciphers to use
17:44:47 [ERR][  GRTDispatcher]: exception in grt execute_task, continuing: Exception: SSL connection error: Failed to set ciphers to use
17:44:47 [ERR][  GRTDispatcher]: worker: task 'execute sql queries' has failed with error:.SSL connection error: Failed to set ciphers to use
17:44:47 [ERR][SQL Editor Form]: SQL editor could not be connected: SSL connection error: Failed to set ciphers to use
17:44:47 [ERR][SQL Editor Form]: Your connection attempt failed for user 'root' to the MySQL server at localhost:3306:
  SSL connection error: Failed to set ciphers to use

Please:
1 Check that MySQL is running on address localhost
2 Check that MySQL is reachable on port 3306 (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
17:45:03 [ERR][SQL Editor Form]: SqlEditorForm: exception in do_connect method: Exception: SSL connection error: Failed to set ciphers to use
17:45:03 [ERR][  GRTDispatcher]: exception in grt execute_task, continuing: Exception: SSL connection error: Failed to set ciphers to use
17:45:03 [ERR][  GRTDispatcher]: worker: task 'execute sql queries' has failed with error:.SSL connection error: Failed to set ciphers to use
17:45:04 [ERR][SQL Editor Form]: SQL editor could not be connected: SSL connection error: Failed to set ciphers to use
17:45:04 [ERR][SQL Editor Form]: Your connection attempt failed for user 'root' to the MySQL server at localhost:3306:
  SSL connection error: Failed to set ciphers to use

Please:
1 Check that MySQL is running on address localhost
2 Check that MySQL is reachable on port 3306 (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
[9 Jul 2021 0:47] Horacio Flores Gomez
Workbench log

Attachment: wb.log (application/octet-stream, text), 11.07 KiB.

[9 Jul 2021 0:49] Horacio Flores Gomez
¿Could you please send an answer to my mail address hfloresg@prodigy.net.mx?
Thanks in advance for your support.
[16 Jul 2021 12:22] MySQL Verification Team
Hello,

Thank you for the bug report.
I tried to reproduce your issue on windows 10 with workbench 8.0.25 but I am not seeing any issues at my end.

Regards,
Ashwini Patil
[17 Jul 2021 5:20] Horacio Flores Gomez
I got the solution to this problem with a workaround. I created a new connection in the main page of the workbench that works pretty well. I deleted the original connection afterwards.