Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I read:

But could not fix it: suddenly (after a year of service, no changes on my winscp settings) it gives me "network error connection timed out" (im using ec2-user) (also from the amazon console).

  • Log FILE: http://pastebin.com/vNq6YQvN
  • All Sites that run on it run fine
  • port 22 is allowed (never changed it) (security group)
  • using the correct ec2-user and domain
  • via my winscp / putty i can connect to other hosting (via ssh)

update: SOLVED. I spend 2 days without looking at my own IP address .... (since it did not change the past 3 years....). Your comments made the spark in my brain. thank you so much. (and only now i find dozens of discussions from angry users that the static addresses from my provider are changed to dynamic ones: http://gathering.tweakers.net/forum/list_messages/1501005/12 ...)

share|improve this question
    
Your post is > 30K character limit and I suspect that some of the information you tried to post has been truncated. Please review your question and attempt to whittle it dow to relvant information. –  Iain Jul 9 '12 at 20:32
    
A service such as fpaste.org / pastebin will help here I suspect sshd has not started, but I can't tell as the information provided appears truncated, per Iains comment. –  Oneiroi Jul 9 '12 at 20:34
    
updated the logs (made a pastebin account), thanks –  edelwater Jul 9 '12 at 20:48
add comment

2 Answers 2

up vote 1 down vote accepted

I think your logs are snipped.

Here are the things you need to check

Check if the name you are connecting to is correct. It may have changed and we have no idea about you setup/

Check the security group of the EC2 instance , is SSH allowed by firewall? What about IP

Check in your log files if it copied the SSH Public Key

share|improve this answer
    
"what about IP" made the spark –  edelwater Jul 9 '12 at 20:59
1  
hah :D so you have the all-spark –  Vangel Jul 9 '12 at 21:28
1  
im glad there are primes –  edelwater Jul 9 '12 at 21:35
    
Something similar happened to me before when rebooting an instance. The Elastic IP was disassociated with the server. –  David Csonka Jul 10 '12 at 1:14
    
@David, yeah that happens. I know it happens when you stop the instance. Now with multipe IPs to EC2 this is gonna be one hell of a headache. –  Vangel Jul 10 '12 at 8:05
show 2 more comments

If it's connection timed out, then it's the problem on the firewall. Check with your desktop, ISP, and home/company firewall, GPO policy, as well the EC2 firewall. Eventually delete and remove each rule so hopefully you will get thru. It clearly says that the sshd is started.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.