Other options is to use password less ssh login using keypair which is far more secure than user/passwords and much quicker for most folks. OpenStack gives you a built in way to create your own keypairs - It will download the private key to you system, and create a public key in the system, it can then be injected into images as they are launched.
Hi,
Did you add port 22 to default sec group ? And after saving the keypair ,did you do the following ?
chmod 0600 MY_PRIV_KEY.pem
ssh-add MY_PRIV_KEY.pem
and then try ssh -i MY_PRIV_KEY.pem cirros@10.0.0.2 .
You can also verify whether the nodes are configured to allow port 22 by checking iptables.
iptables -L -n
I do not use a private key, but a root password to acces the instance.
Asked: 2014-02-09 03:12:09 -0500
Seen: 966 times
Last updated: Feb 11 '14
Use ssh verbose and paste the output here, this will provide more details. Just add the `-v` to your SSH CLI invocation: `ssh -v -i key.pem user@host`.
OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 192.168.0.1 [192.168.0.1] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type 1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: ssh_exchange_identification: ssh_exchange_identification: Connection closed by remote host
Hello, no ideas? the same problem persist.