Ssh – Connection error in bitvise ssh client

openshift-online-2puttysshssh-tunnel

Iam able to connect to ssh server host on openshift using putty but while using the same setting in bitvise ssh client i get the folowing error –

01:47:18.424 Connecton failed. getaddrinfo() failed. Windows error 11003: A
non-recoverable error occurred during a database lookup.
01:47:18.424 The SSH2 session has been terminated.

I have added the public key in it keypair section.
is there a way to connect to ssh servers on port 22 using bitvise.

Best Answer

This can be done by following these instructions:

generate your ssh keys
add key to openshift, if not done already
import the key into the user keypair manager (private key)
import the key into the host key manager (public key)
- for host, grab the remote access url and remove the ssh. *everything is needed except the ssh for the url and save
- add everything after the @ to the host back on the main application and everything before the @ to the username field
- select the slot for the key you imported and enter the passphrase
- when / if you get prompted to accept a cert, accept it

you should now be connected with ssh and sftp!

Related Solutions

Ssh – PuTTY use agent forwarding for chain of servers

Since $SSH_AUTH_SOCK is not set, its likely either a problem with putty/pagent, or sshd itself.

You can put sshd into debug mode easily enough. Log into the server (this can be safely done over ssh, as long as you remember to restart sshd after you are done) and stop sshd (via your init scripts). Then run:

/usr/sbin/sshd -Dddd

(-D for foreground mode, -ddd for verbose debugging)

Try to connect via putty again, and watch the output from sshd. If putty is sending the keys for agent forwarding, you should see something about auth-agent-req@openssh.com. If you don't see that, then putty is not properly sending the key along for agent forwarding/requesting agent forwarding.

That should narrow down where the issue lies. You can also run 'ssh -vvv' from host1 for verbose debugging output while trying to ssh to host2.

(At this point, please remember to ctrl+C the foreground sshd process and restart it from your init scripts, otherwise you'll be locked out of your server!)

Windows – Laravel Forge SSH on windows not recognized

The answer from @alysdal worked perfectly for me. Just to have the steps on this site as well:

You have to modify your public key and transform your generated key from this form

---- BEGIN SSH2 PUBLIC KEY ----
Comment: "rsa-key-20160907"
AAAAB3NzaC1yc2EAAAABJQAAAIEA3nfXA8oSOGcx1OJg0/2dkgH2gDXhN6GX5/QW
KyPif8tHYh/GBvwsnoLyPAUNq9D9wv/g+DxBr1nGpIwIAICxycHNEq7iNGcImhWs
rlEWBWRE8fYG4Qpx0/CKDcNsCZzjiu0exwp4pw5nDcZQOsr321bly3edRgfgmgix
rzLaOCk=
---- END SSH2 PUBLIC KEY ----

into this form

ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAIEA3nfXA8oSOGcx1OJg0/2dkgH2gDXhN6GX5/QWKyPif8tHYh/GBvwsnoLyPAUNq9D9wv/g+DxBr1nGpIwIAICxycHNEq7iNGcImhWsrlEWBWRE8fYG4Qpx0/CKDcNsCZzjiu0exwp4pw5nDcZQOsr321bly3edRgfgmgixrzLaOCk= user@host

which means:

Remove first two lines and the last line.
Join the remaining lines into one single line without whitespaces
Insert ssh-rsa with one trailing space at the beginning of the file
Optional: You can append <user>@<host> at the end of the file preceded with a whitespace.

Best Answer

Related Solutions

Ssh – PuTTY use agent forwarding for chain of servers

Windows – Laravel Forge SSH on windows not recognized

Related Topic