After release *.6395, tunneling SSH is not working anymore

After release v11.3.0.6395 (64 Bit) - when you try to connect to Postgres via SSH Tunneling, the connection are interrupted with an SSH related problem.

I added support for OpenSSH tunnels yesterday. Probably there is something left to do in PG mode.

Is there any error message? What is set up in the SSH tunnel tab?

Error on connection attempt:

[Window Title] Error

[Content] SSH exited unexpected. Command line was: ssh.exe ubuntu@api.prismachem.com.br -pw "**" -p 22 -i "C:\Users\ckleu\OneDrive\Área de Trabalho\Programas\Oracle\oracle_ssh.ppk" -N -L 3307:127.0.0.1:5432

[OK]

[Footer] Buscar ajuda sobre este erro (=> google.com)

And screenshots attached!

I saw that now the new version uses pure ssh.exe command.

This worked for me: ssh -i key_name.pem -N -L 3307:etc.etc.sa-east-1.rds.amazonaws.com:5432 ubuntu@my.ip.number

The same here.

Better to keep both options (SSH and plik) and during the road map rely on the OpenSSH only.

Now, I'm not able to login into all my servers due to this infection.

Should be fixed in the next nightly build.

See issue #362 and commit:8656a6459f425803eca8ab71a892aa85b7e09694

I'm currently running on 11.3.0.6406 and still the same issue.

any Idea?

The same here.

Better to keep both options (SSH and plik) and during the road map rely on the OpenSSH only.

Now, I'm not able to login into all my servers due to this infection.

That's why you shouln't use nightly builds (of any piece of software) in prod environment. Rollback to may/21 stable build.

@snake_eyes probably you have already saved some modification of your session with the broken build. In that case just doublecheck the path to the SSH executable in the SSH tunnel tab.

For completeness sake: the error comes up due to a PuTTY key which is not compatible with the keys expected by ssh.exe. So, just reenter the path to plink ("plink.exe" should do it).

For completeness sake: the error comes up due to a PuTTY key which is not compatible with the keys expected by ssh.exe. So, just reenter the path to plink ("plink.exe" should do it).

I'll try to convert the PEM file to a PPK to see if it fixes the problem.

For completeness sake: the error comes up due to a PuTTY key which is not compatible with the keys expected by ssh.exe. So, just reenter the path to plink ("plink.exe" should do it).

I'll try to convert the PEM file to a PPK to see if it fixes the problem.

I have changed to plik and still the same issue with the same mentioned build.

Check the enclosed screenshot.

@snake_eyes please verify the file name and path. It's called "plink", not "plik".

I can confirm that when I changed to plink, it worked.

Note that the plik is another software, and I was confused between them :)

Something to note: anyone using a Putty flavour which has its own name for the plink executable (like, in my situation, the Kitty flavour with klink.exe) will not be able to use the tunnel feature natively. See issue#1529.

(Workaround can be to rename the executable, if that does not limit necessary functionality elsewhere)