MySQL Workbench Cannot Open SSH Tunnel
I want to use MySQL Workbench to access my Linode DB. I enter the information according to the text boxes, but I consistently get the error: Failed to Connect to MySQL at XX.XX.XX.XX:3306 through SSH Tunnel at user@127.0.0.1:22 with user root.
Cannot Open SSH Tunnel: Connection refused.
I have repeatedly confirmed that my MySQL is running on the remote server; that SSH is working properly. I can directly connect through SSH, and from there access the databases. I have checked that the user has the proper privileges, confirmed the passwords, and so on.
I have carefully followed the various tutorials without any success.
What really annoys me is that I recently rebuilt this Linode; I had no problems with Workbench in the previous instance.
I am hoping someone can either tell me what I'm doing wrong, or point me in the right direction to find documentation about this issue.
2 Replies
watrick
Linode Staff
✓ Best Answer
What really annoys me is that I recently rebuilt this Linode; I had no problems with Workbench in the previous instance.
I was considering this comment while reviewing the MySQL :: MySQL Workbench Manual :: 5.3.3 Standard TCP/IP over SSH Connection Method documentation. Then this sentence caught my attention:
If your stored host fingerprint is different than the host's current fingerprint, then an error is generated and you will be required to handle the discrepancy from outside of MySQL Workbench before creating the connection.
It's likely that the rebuild of the Linode changed the host's fingerprint and is causing you issues.
If you've already looked into that, then the following post on Stack Overflow may be helpful: Failed to Connect to MySQL at localhost:3306 with user root - Stack Overflow
Other guides that I thought could be helpful for you are:
- Install MySQL Workbench for Database Administration | Linode
- Create an SSH Tunnel for MySQL Remote Access | Linode
- Connect to a MySQL Database Using the mysql Command | Linode
Each one of those guides are filed under the MySQL section of guides on our website. If one of the links that I provided above does not help, maybe browsing the subset of guides in there will.
