3

This is the command I am told to use by clicking connect in the control panel

ssh -i private_key.pem root@instancePublicDNS

Well, that one failed so I wanted to know what happen so I ran:

ssh -vvv private_key.pem root@instancePublicDNS

OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
debug2: ssh_connect: needpriv 0
debug1: Connecting to private_key.pem [...] port 22.
debug1: connect to address ... port 22: Attempt to connect timed out without establishing a connection.
ssh: connect to host private_key.pem port 22: Bad file number

Any Ideas?
I have searched for the answer on Google and serverfault, I found a few possible solutions that did not work.

info about the instance

AMI-ID : ami-688c7801 ( ubuntu 10.10 Server )

Improve this question

1 Answer 1

Reset to default
5

Configure "Security Groups" to allow ssh:

Improve this answer
3
  • @Mark if the answer is correct, then confirmed it Commented Feb 20, 2011 at 22:39
  • I think most people forget to apply rules changes. I did. Commented Jan 19, 2012 at 21:38
  • Does not work. I already have this in the rules. But after an instance reboot, ssh-ing does not work. Commented Mar 21, 2013 at 2:21

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.