Amazon EC2 SSH Failed to connect “Bad File Number”

Question

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 )

ooshro · Answer 1 · 2011-02-20 22:26:36Z

up vote 4 down vote accepted

Configure "Security Groups" to allow ssh:

answered Feb 20 '11 at 22:26

ooshro
5,147716

	Thank you, this worked! – Mark McCook Feb 20 '11 at 22:33
	@Mark if the answer is correct, then confirmed it – ooshro Feb 20 '11 at 22:39
	Awesome! Thanks for that! – jonathanconway Jul 13 '11 at 17:09
	I think most people forget to apply rules changes. I did. – Jose Adrian Jan 19 at 21:38

feedback

1 Answer