Problems with amazon SSH but not other SSH

Question

why is SSH not working?

I keep getting..

ssh: connect to host ec2-11-11-11-11.compute-1.amazonaws.com port 22: Operation timed out

when trying to connect to my amazon EC2 server, at first i thought it was some sort of firewall but i have no firewall and i can SSH in to my MediaTemple server.

the chmod of my pem is 600. and this is how im trying to ssh..

ssh -i ~/.ssh/ServerKey.pem [email protected]

i have a AMI ID: ami-508c7839 so i seen on a video the user should be ubuntu.

i hope someone can see an error somewhere because i dont have a clue. if it helps to know im on a mac.

thanks in advance

Alpha01 · Accepted Answer · 2011-04-27 00:12:47Z

2

Run your ssh command in verbose mode to see where exactly it's timing out in.

ssh -i ~/.ssh/ServerKey.pem -v [email protected]

Also, I would advice you to specify the absolute path to your ssh key instead of using the ~ tilde sign. (It will save you a headache if you want to auto connect to your EC2 server from a script/cron).

-Tony

answered Apr 27, 2011 at 0:12

Alpha01

8181 gold badge7 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

user633268 Over a year ago

ok, thanks... this is what i got back

MacBook-Pro:~ aaranmcguire$ ssh -i ~/.ssh/ServerKey.pem -v [email protected] OpenSSH_5.2p1, OpenSSL 0.9.8l 5 Nov 2009 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to ec2-11-11-11-11.compute-1.amazonaws.com [50.19.33.24] port 22. debug1: connect to address 50.19.33.24 port 22: Operation timed out ssh: connect to host ec2-11-11-11-11.compute-1.amazonaws.com port 22: Operation timed out

Alpha01 Over a year ago

It sounds like its a firewall issue. You may need to check your Inbound firewall policies on the security group that our instance is using. Make sure the policy "Port 22 (SSH) source 0.0.0.0/0" is set.

user633268 Over a year ago

did that and restarted the instance... still the same

Marcello DeSales · Accepted Answer · 2012-02-27 20:06:59Z

2

Go to Security Group, and make sure the policy "Port 22 (SSH) source 0.0.0.0/0" is set.

answered Feb 27, 2012 at 20:06

Marcello DeSales

22.5k15 gold badges85 silver badges81 bronze badges

Comments

JP. · Accepted Answer · 2012-02-20 06:53:21Z

1

Make sure that you have hit "Apply Rule Changes" in Security Groups tab.

answered Feb 20, 2012 at 6:53

JP.

1,0732 gold badges19 silver badges40 bronze badges

Comments

Lango · Accepted Answer · 2012-12-07 16:49:20Z

0

I do not think it is an problem of ssh. I suggest you check the network reahcability.

Try to ssh the ip address directly. Try to debug the dns.

answered Dec 7, 2012 at 16:49

Lango

234 bronze badges

Collectives™ on Stack Overflow

Problems with amazon SSH but not other SSH

4 Answers 4

3 Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

3 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related