Had it worked nowhere, I probably would have tried resetting the password earlier, and was dumbfounded as to why the technically correct, working everywhere else, password wouldn't work (stopped working) with Workbench.Īnyway, this is at lease a note to myself in case I ever run across a similar strangeness again. I found it strange that the password worked everywhere, except for connecting to the database via Workbench. When starting the session, select SSH -> Tunnels. Turns out that I was not even using a putty generated key for this particular connection, despite the message. This can also be achieved using Putty (assuming that Computer A is the Windows machine). Password for MySQL did not need to change. Updating the master server password (everywhere) fixed the issue. Oddly once I clicked to "edit" the master password on my server, I saw that the current password did not match their new password requirements. While my password still worked for connecting via FTP, MySQL Workbench could not connect to the database. It seems they changed the format for (new) master password to the server my website & database are on. I had been successfully making the connection for years. This error appears in the PLINK/PuTTY/ssh window, when you try to establish a connection to the tunnel, and the server cannot connect to the remote port. You can distinguish between the two types of keys by viewing them in any text editor and reading the first line. I was then able to connect to the MySQL server using the RSA private key.
Make sure you backup your OpenSSH private key beforehand as this will override id_rsa. ssh-keygen -p -m PEM -f C:/Users/username/.ssh/id_rsa The solution here was to convert the OpenSSH private key to an RSA private key. I set the location of the key to C:/Users/username/.ssh/id_rsa and received the error. I try to access the MySQL database using an OpenSSH generated private key. The solution here of course was to regenerate the keys.
I deleted the corresponding public key (mistakenly) from my server then tried to re-connect and received the error. For example, the command 'ssh -L 8080:localhost:80 userremote.host -N' would establish an SSH tunnel from port 8080 on your local computer to port 8080 on the distant.
Ubuntu putty ssh tunnel not working mac os#
I gained access to the MySQL database successfully using a private key generated by my server (I am using CPanel). In Mac OS (or Ubuntu), use the 'ssh' command with the '-L' option to select the local port and destination, and the '-N' mark to execute the SSH connection in the background. The issue occurred in two different scenarios. I had a similar issue connecting to MySQL and wanted to share my solution in case anyone else ends up here.
0 kommentar(er)
