![]() Try it without it to see the difference (If you want to see the actual ssh commands being used, they are. The addition of -nNT prevents us from actually connecting to the remote host (preventing TTY). My assumption is that this shouldn't be an issue since the routing is done from the bastion but that's my last thought as being the issue in this scenario. You can connect Postgres, MySQL, MSSQL, MongoDB, and other databases that are hosted under a private network via SSH tunnels. This will allow us to create port-forwarding ssh tunnel using the bastion host to the mongo relica-set: ssh -nNT bastion-host-mongo-forward. There is one caveat with this setup in that the target host (www) is in an AWS VPC and is only addressable from the bastion. Ssh_exchange_identification: Connection closed by remote host I have added the necessary config options on the bastion server (/etc/ssh/sshd_config): PermitTunnel yesīut I get the following error: OpenSSH_7.2p2 Ubuntu-4ubuntu2.4, OpenSSL 1.0.2g ĭebug1: Reading configuration data /etc/ssh/ssh_configĭebug1: /etc/ssh/ssh_config line 19: Applying options for *ĭebug1: /etc/ssh/ssh_config line 59: Applying options for type -1ĭebug1: identity file ~/.ssh/key.pem-cert type -1ĭebug1: Enabling compatibility mode for protocol 2.0ĭebug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4Ĭhannel 0: open failed: administratively prohibited: open failed Start the Putty client on the Windows box and create an SSH tunnel to 172.31.2.2 using the bastion-host: 2.1 Create the SSH connection. Having looked through various SE questions which potentially solve the problem, nothing has. I'm having an issue with establishing an ssh tunnel through a bastion host.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |