MySQL Bugs: #70862: Uses another host on connection over SSH

Bug #70862	Uses another host on connection over SSH
Submitted:	8 Nov 2013 11:39	Modified:	14 Sep 2014 18:43
Reporter:	Mik Yo	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	6.0.7.11215	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any
Tags:	127.0.0.1, host, localhost

Description:
When I connect to DB by method TCP/IP over SSH in field "Mysql hostname" is value "127.0.0.1" and this host success connects by realy SSH. But if I try button "Test connection" it give me error messagebox with "Failed to connect to Mysql 127.0.0.1:3306 ...." and text "Host 'backend.du......' is not allowed to connect to this Mysql server", where 'backend.du......' is domain for this server in LAN.

If I click button "Connect" on this configured server it not make connection and return to hello-screen. If I try "test connection" it make critical error and program shutdown. And it can shutdown some minutes after my first try to connect.

Shutdown gives some text like:
AppName: mysqlworkbench.exe      AppVer: 6.0.7.11215     AppStamp:5220ca31
ModName: python27.dll      ModVer: 2.7.3150.1013      ModStamp:4fd60272
fDebug: 0       Offset: 000d56e0

How to repeat:
make connection over SHH to localhost or 127.0.0.1 to server which allowed only locahosts. Use "connect" or "test connection" buttons.

Suggested fix:
May be program detect host before connect and use domain

Error message with another host

Attachment: HowIsIt.jpg (image/jpeg, text), 124.85 KiB.

If you use hostname localhost success?. Thanks.

localhost gives the same error.
My admin said that it is tunnel problem. Than program connecting it becomes like external ip and another host for mysql server

Does it work if you just accept the connection settings and use it to connect, without clicking Test first?

The local port used for the SSH-tunnel must already be in use for a previous tunnel or SSH connection - thus the new connection will connect to the same server as the previous connection does. But I don't know in detail how WB allocates/reserves the local port.

Do you have another program running using SSH (putty, a SFTP client etc.)? And (stupid question, maybe) have your tried rebooting the sytem (in order to terminate possible running and orphaned processes that occupy a local port)?

Peter
(not a MySQL/Oracle person)

Yes, I have another programs using SSH. I can not test now, because my admin change mysql config for my non stop working.

Please try version 6.1.7. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".