After release v188.8.131.5295 (64 Bit) - when you try to connect to Postgres via SSH Tunneling, the connection are interrupted with an SSH related problem.
After release *.6395, tunneling SSH is not working anymore
Error on connection attempt:
[Window Title] Error
[Content] SSH exited unexpected. Command line was: ssh.exe email@example.com -pw "**" -p 22 -i "C:\Users\ckleu\OneDrive\Área de Trabalho\Programas\Oracle\oracle_ssh.ppk" -N -L 3307:127.0.0.1:5432
[Footer] Buscar ajuda sobre este erro (=> google.com)
And screenshots attached!
Should be fixed in the next nightly build.
See issue #362 and commit:8656a6459f425803eca8ab71a892aa85b7e09694
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.
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.
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)
Please login to leave a reply, or register at first.