MySQL Bugs: #95221: Remote Management dont work with different port

Bug #95221	Remote Management dont work with different port
Submitted:	2 May 2019 11:22	Modified:	3 Jun 2019 17:48
Reporter:	Dennis Meyer	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	8.0.15	OS:	Windows (10)
Assigned to:		CPU Architecture:	Any
Tags:	Connection, remote-management, setup, ssh

Description:
Hi,

i want to setup a remote management connection based on a SSH login.
The Setting Port isnt used properly during "Test Connection"

Workbench Errorlog:
13:17:40 [INF][wb_admin_grt.py:testInstanceSettingByName:675]: Instance test: Connecting to 127.0.0.1
13:17:40 [INF][            grt]: connected.	
13:17:40 [INF][SSHSessionWrapper]: Opening new SSH connection to 127.0.0.1:22
13:17:40 [INF][      SSHCommon]: libssh: ssh_connect ssh_connect: libssh 0.8.5 (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
13:17:40 [INF][      SSHCommon]: libssh: ssh_socket_connect ssh_socket_connect: Nonblocking connection socket: 1696
13:17:40 [INF][      SSHCommon]: libssh: ssh_connect ssh_connect: Socket connecting, now waiting for the callbacks to work
13:17:50 [ERR][     SSHSession]: Unable to connect: 127.0.0.1:22
Error was: Timeout connecting to 127.0.0.1
13:17:50 [ERR][SSHSessionWrapper]: Unable to connect to SSH: Timeout connecting to 127.0.0.1
13:17:50 [ERR][wb_admin_grt.py:testInstanceSettingByName:694]: Exception: Could not connect to SSH server
13:17:55 [INF][      Workbench]: Shutting down Workbench
13:17:55 [INF][ mforms managed]: Shutting down mforms wrapper
13:17:55 [INF][      Workbench]: Done

How to repeat:
On Virtualbox:

Setup a local Portforwarding with Virtualbox for your Virtual Machine which runs CentOS 7 and MySQL 8.0 for SSH: Local: 38001, Target System: 22

On Workbench:
Manage Server Connections
Open the "Remote Management" Tab
Select "SSH login based management"
Enter Hostname 127.0.0.1
Change Port to 38001
Username root
Check "Authenticate Using SSH Key"
Select your SSH Privatekey
Hit "Test Connection"
You will receive a Error:
Test Connection
ERROR Could not connect to SSH Server

Thank you for the bug report. Are you able to do it with the mysql command line?.

This reminds me of Bug #93149, that time I didn't observe any issues at my end. Tried again with 8.0.16, no issues observed.

regards,
Umesh

Hi,
why should i try this with the command line? If i do a SSH tunnel manually and try to connect with the mysql cli on the forwarded port everything is working ok. It's just about the SSH tunnel features for the Remote Management (not connection!) which are broken, this got nothing todo with the cli.
regards,
Dennis

To make it more clear. 

Workbench does not recognize the port i have entered, 38001, it uses allways the default port 22. Thats the bug.

connect ssh using port 38001

Attachment: 95221.png (image/png, text), 127.57 KiB.

I couldn't repeat with version 8.0.16 (see screenshot).

Its about the Remote Management not the Connection setting...

RemoteManagement Screenshot

Attachment: RemoteManagement.png (image/png, text), 71.41 KiB.

Thank you for the feedback.

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.17 release, and here's the changelog entry:

Remote management did not work after the SSH port number on the
destination computer was changed; instead, it continued to use the default
port number.

Thank you for the bug report.