Bug #99976 Unable to connect to server when using TCIP over SSH with a password
Submitted: 24 Jun 2020 21:51 Modified: 9 Feb 2021 12:46
Reporter: Lawrence Cooke Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:8.0.22 OS:Any
Assigned to: CPU Architecture:Any

[24 Jun 2020 21:51] Lawrence Cooke
Description:
When connecting to a server using using connection mode TCP/IP over SSH

If the server uses a SSH key then it works fine, however if the server uses a password to connect to SSH, then it always returns the following error:

Lost connection to MySQL server at 'reading initial communication packet'

Using Workbench 6.3.10 does not have this issue, it connects without a problem. 

How to repeat:
create  a TCP/IP over SSH connection

use a password to connect to SSH rather than a SSH private Key

connection will fail on Workbench 8, will work on Workbench 6.3.10.
[6 Aug 2020 12:23] MySQL Verification Team
Hello Lawrence Cooke,

Thank you for the bug report.
I tried to reproduce your issue on windows 10 with workbench 8.0.21 but I am not seeing any issues at my end. To investigate further this issue at our end, may I kindly request you to launch workbench under debug mode (-log-level=debug3) and provide unaltered workbench log file(more details about log are explained here - https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html). Thank you.

Regards
Ashwini Patil
[6 Aug 2020 20:53] Lawrence Cooke
It appears as though despite having entered passwords, that Workbench is not sending it to the server. 

This line in log file seems to indicate that:

06:06:57 [INF][      SSHCommon]: libssh: ssh_packet_userauth_failure ssh_packet_userauth_failure: Access denied for 'none'. Authentication that can continue: publickey,password,keyboard-interactive

Just to reiterate, the same saved connection will connect on mysql workbench 6.x

==============================

log file:

06:51:08 [INF][     SSH tunnel]: Existing SSH tunnel not found, opening new one
06:51:08 [INF][     SSH tunnel]: Opening SSH tunnel to wordvillage.com.au:22
06:51:08 [INF][      SSHCommon]: libssh: ssh_connect ssh_connect: libssh 0.8.8 (c) 2003-2018 Aris Adamantiadis, Andreas Schneider and libssh contributors. Distributed under the LGPL, please refer to COPYING file for information about your rights, using threading threads_stdthread
06:51:08 [INF][      SSHCommon]: libssh: ssh_socket_connect ssh_socket_connect: Nonblocking connection socket: 2360
06:51:08 [INF][      SSHCommon]: libssh: ssh_connect ssh_connect: Socket connecting, now waiting for the callbacks to work
06:51:09 [INF][      SSHCommon]: libssh: ssh_kex_select_methods ssh_kex_select_methods: Negotiated curve25519-sha256,ssh-ed25519,aes256-ctr,aes256-ctr,hmac-sha2-256,hmac-sha2-256,none,none,,
06:51:10 [INF][      SSHCommon]: libssh: ssh_packet_dh_reply ssh_packet_dh_reply: Received SSH_KEXDH_REPLY
06:51:10 [INF][      SSHCommon]: libssh: ssh_client_curve25519_reply ssh_client_curve25519_reply: SSH_MSG_NEWKEYS sent
06:51:10 [INF][      SSHCommon]: libssh: ssh_packet_newkeys ssh_packet_newkeys: Received SSH_MSG_NEWKEYS
06:51:10 [INF][      SSHCommon]: libssh: ssh_packet_newkeys ssh_packet_newkeys: Signature verified and valid
06:51:10 [INF][      SSHCommon]: libssh: ssh_packet_userauth_failure ssh_packet_userauth_failure: Access denied for 'none'. Authentication that can continue: publickey,password,keyboard-interactive
06:51:10 [INF][     SSHSession]: Banner: 
06:51:11 [INF][      SSHCommon]: libssh: ssh_packet_userauth_failure ssh_packet_userauth_failure: Access denied for 'unknown'. Authentication that can continue: publickey,password,keyboard-interactive
06:51:11 [INF][     SSH tunnel]: SSH tunnel opened on port: 50051
06:51:22 [ERR][SSHTunnelHandler]: Unable to open tunnel. Exception when opening tunnel: Unable to open channel
06:51:22 [WRN][SQL Editor Form]: Lost connection to MySQL server at 'reading initial communication packet', system error: 0
06:51:22 [ERR][SQL Editor Form]: Connection failed but remote admin does not seem to be available, rethrowing exception...
06:51:22 [ERR][  GRTDispatcher]: exception in grt execute_task, continuing: Exception: Lost connection to MySQL server at 'reading initial communication packet', system error: 0
06:51:22 [ERR][  GRTDispatcher]: worker: task 'execute sql queries' has failed with error:.Lost connection to MySQL server at 'reading initial communication packet', system error: 0
06:51:22 [ERR][    WQE backend]: Got an exception during connection: Lost connection to MySQL server at 'reading initial communication packet', system error: 0
06:51:22 [ERR][SQL Editor Form]: SQL editor could not be connected: Lost connection to MySQL server at 'reading initial communication packet', system error: 0
06:51:22 [ERR][SQL Editor Form]: Your connection attempt failed for user '1021677_20' to the MySQL server at db99a.pair.com:3306:
  Lost connection to MySQL server at 'reading initial communication packet', system error: 0

Please:
1 Check that MySQL is running on address db99a.pair.com
2 Check that MySQL is reachable on port 3306 (note: 3306 is the default, but this can be changed)
3 Check the user 1021677_20 has rights to connect to db99a.pair.com 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 db99a.pair.com connecting from the host address you're connecting from
[23 Nov 2020 0:41] Lawrence Cooke
Something I noticed in regards to this. It appears that the host database it is connecting to , regardless of what the settings are set to, is 127.0.0.1. When the host is anything but 127.0.0.1, the connection is failing. If you do SSH into a server and mysql is able to connect on 127.0.0.1 then it works fine.  

Separately , what I noticed was that in Workbench 6, if you don't have the database password saved, it prompts for the password. in workbench 8 , it just tries to connect without the password. 

All this is only an issue when connecting via a SSH connection. It seems like workbench isn't reading the database connection information at all.
[9 Feb 2021 12:46] MySQL Verification Team
Hello Lawrence Cooke,

Thank you for the valuable feedback and details.
I tried to reproduce your issue on windows 10 with workbench 8.0.22 but I am not seeing any issues at my end.

Regards,
Ashwini Patil