In AWS, “network error connection timed out” indicates a connectivity issue with the instance.

Here at Bobcares, we have seen several such AWS related errors as part of our Server Management Services for web hosts, AWS users, and online service providers.

Today we’ll take a look at the causes for this error and see how to fix it.

What causes AWS “network error connection timed out” error to occur

Generally, this error occurs if there is any connectivity problem with the instance. It means the request is not able to reach the instance and finally times out.

This can happen if the SSH is not running or if a firewall is rejecting access to the instance.

Also, if any necessary ports are not open then this error occurs.

How we fix AWS “network error connection timed out” error

Now let’s see the solution that our Support Engineers provide to our customers to resolve this error.

1. Adding an SSH rule for inbound connection

Here are the steps to add an SSH rule for inbound connection to EC2.

1. Initially, access the EC2 console.
2. From the left navigation pane, click on ‘Instances’ and select the Instance.
3. In the Description tab, locate Security Groups and click the available group link
4. On the Inbound tab, click on the ‘Edit’ button.
5. Then click Add Rule and select SSH for type, Port Range 22, and Source Anywhere
6. Finally, connect with putty.

2. Check for any Firewall blockage

First, open the AWS manager console and then start a session.

Now, restart the SSH service to disable the firewalls. To do so, run the below commands.

$ sudo iptables -F
$ sudo service sshd restart

Now run the below command to verify SSH is listening to port 22.

$ sudo netstat -tnlp | grep :22

After this, terminate the session.

Finally, connect to the instance using SSH.

[Need any further assistance in fixing AWS errors? – We are here to help you.]

Conclusion

In short, this error occurs if there is a connectivity issue with the instance. Today, we saw how our Support Engineers fix this error.