CODEWITHSUNDEEP
amazon-web-servicesamazon-ec2connectivity
Vel Kumar
Vel Kumar

Reputation: 11

EC2 Instance Network Error : "Request time out"

We have EC2 Redhat instance with 1TB of volume. After modifying volume to 2TB, when we try to access server via SSH it throwing error as Network Error : Request time out.

We followed Requesting Modifications to Your EBS Volumes - Amazon Elastic Compute Cloud to modify the volume.

Could any one help me to fix this issue?

Debug Log:

OpenSSH_for_Windows_7.6p1, LibreSSL 2.6.4
debug3: Failed to open file:C:\\Users\\Max-Asset-03/.ssh/config error:2
debug3: Failed to open file:C:\\ProgramData\\ssh/ssh_config error:2
debug2: resolving "<ip>" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to <ip> [<ip>] port 22.
debug3: finish_connect - ERROR: async io completed with error: 10060, io:000001B6073FB750
debug1: connect to address <ip> port 22: Connection timed out
ssh: connect to host <ip> port 22: Connection timed out

Upvotes: 1

Views: 2277

Answers (2)

Aress Support
Aress Support

Reputation: 1425

Basically, "Network Error : Request time out" error occurs when there is a network related issue.

Possibilities that you can troubleshoot are as follows:

  1. Make sure that your NACL rules are not being an obstacle.
  2. There may be the chances of your IP address getting blacklisted.

[Visit spamhaus.org for checking if your IP address has been black listed]. If yes, the whitelist the IP and try to login again.

  1. Also, there might be a possibility that EBS volume have been corrupted due to the activities on your EC2 instance when it is in 'running' state. If yes, try to recover your EBS volume using the snapshot (incase you have taken it).

Hope this helps.

Upvotes: 1

Nishant Singh
Nishant Singh

Reputation: 3199

Here is the approach i would take:

 1. Try doing a Telnet to port 22 from your env and see if it connects
 2. If it does not connect then you should look at your security group first and see if you have open inbound rule to port 22
 3. If you think you have the sec group open then i would look at NACL layer.
 4. If you think that is also not the issue, you should see are you in the public subnet

This should give u a good idea of what is wrong

Upvotes: 1

Related Questions