Level 13
Is your key in openSSH format? And public? Normally you don't pass private keys around.
What versions of db and workbench are you running? Client a Mac,. Windows or linux?
Feb 20, 2016
7
Level 10
Cannot connect to MySQL Workbench
I'm trying to connect to MySQL Workbench using SSH.
I've tried:
Connection Method: Standard TCP/IP Over SSH
SSH Hostname : 159.203.114.xxx
SSH Username: forge
SSH KeyFile: C:\Users\privKey.ppk
MySQL Hostname: 127.0.0.1
MySQL Serve port: 3306
Username: forge
Password: myPassword
When I test connect, I'm getting the following error:
Could not connect the SSh Tunnel
Authentication error.
Please check that your username and password are correct and try again.
Details (Original exception message):
Bad authentication type, the serve is not accepting this type of authentication.
Allowed ones are: [u'publickey']
[Retry] [Cancel]
But I'm able to SSH using putty, Filezilla, Laravel connection using the same credentials.
Any idea?
Level 10
The problem was with the key format. I generated it with PuttyGen and it wasn't in OpenSSH format.
Created a new key from command prompt and it worked.
I was using Windows 10, Workbench 6.3,
Level 1
I just encountered the same problem on windows 10 x64 with SQL WorkBench 6.3
Following this solution http://stackoverflow.com/questions/5514146/generate-valid-openssh-ssh-key-under-windows
I opened my SSH private Key with putty gen and exported it in OpenSSH format ( Conversion -> Export OpenSSH Key ) Using the same key into SQL Workbench in the new format fixed the problem right away.
Hope it helps someone else!
Level 2
My private key is already OPENSSH. I can ssh into Forge using my private key in Terminal...however...using the same private key through MySQL Workbench I get the following...
"Access denied. Authentication that can continue: publickey"
No matter what I try for the connection settings I get this message. PLEASE HELP!! I've searched for days but have had to resort to using the console to run queries while logged in to Forge. Any assistance would be much appreciated!
Level 67
@themberger Don't know about workbench, but I had to use slightly different settings to connect with Navicat than I did Sequel Pro. Maybe it makes a difference for wb as well.
All settings used the forge ip address, except in Navicat I had to use 'localhost' only for the "general connection" portion, while still using the ip address in the ssh portion. It took forever to figure it out, and I still don't understand why it needs to be that way specifically for Navicat.
Level 2
Thanks for the speedy reply! I ended up having to download a test version of Sequel Pro (the full release crashes on OSX Mohave). Using Sequel Pro worked! Strange but at least I'm passed that one! Thanks again!
Please or to participate in this conversation.