AWS EC2 Error: The site can't be reached - ec2.us-west-1.compute.amazonaws.com took too late to respond. Deploy NodeJS AWS EC2 Error: The site can't be reached - ec2.us-west-1.compute.amazonaws.com took too late to respond. Deploy NodeJS express express

AWS EC2 Error: The site can't be reached - ec2.us-west-1.compute.amazonaws.com took too late to respond. Deploy NodeJS


Just check if your Node.js server is running on the EC2 instance.

Debugging:

  1. Check first if It working locally properly.
  2. Check for the node.js server in EC2.
    • sudo netstat -tulpn | grep :3000
  3. try to run server with --verbose flag i.e npm run server --verbose
    • it will show logs of the server while starting.
  4. Check for the security group Setting for the EC2 instance.
  5. try to connect with the ip:port i.e 35.2..:3000

If still it not working and response taking long time. that means some other service is running on the same port.

try this in ec2:

sudo killall -9 node npm run server

And connect with using IP(54.4.5.*:3000) or public DNS (http://ec2...us-west-1.compute.amazonaws.com:3000).

Hope It will help :)


You may be encountering an issue with outbound traffic. You may be inside a company's network, either physically connected or VPN'd in. In some instances, your VPN isnt set up to handle split traffic, so you must abide by your company's outbound restrictions.

In a situation like this, you would want to use a proxy to access your site. when locking down your security group, make sure you use your proxy's public IP (not your company's).


Usually, when we have connectivity issues, it is something basic or a firewall. I assume you have checked whether a firewall is running on either end, eg. iptables -L -n. Also, any protocol analyzer like wireshark or tcpdump would tell you where packets to port 3000 are visible.