1

I started an EC2 instance and am trying to listen to different ports now.

But I can connect only through port 80, ie., i can access the server through the elastic IP, telnet ONLY to port 80. Telnet to any other port fails.

I have the same configuration for all ports on the security gateway.

enter image description here

I even have the Network ACL configured with similar rules. What is wrong and how do I fix it ?

Note: I do not have enough points to attach more than one link.

9
  • Is anything running on the ports you're trying to connect to?
    – ceejayoz
    Jan 12, 2016 at 2:13
  • @ceejayoz: I have set up a node server that is listening on port 9000. That is also the application I am trying to access.
    – dpm
    Jan 12, 2016 at 2:14
  • Should I kill all process, run my node application again and try connecting to port 9000 ?
    – dpm
    Jan 12, 2016 at 2:15
  • I'd check with one of the techniques at cyberciti.biz/faq/what-process-has-open-linux-port that your app is actually listening on that port.
    – ceejayoz
    Jan 12, 2016 at 2:29
  • 1
    @msanford : I update the post with a picture of my Security Group permissions
    – dpm
    Jan 12, 2016 at 4:15

1 Answer 1

-1

What services are you trying to access, on which ports? Why are you using telnet to port 80? Port 80 is http. http and RDP appear to be responding.

There are many, many resources that describe how to connect to your ec2 instance. Can you go through the efforts you've tried?

Your instances does appear to be open to the world on a wide variety of ports according to security groups. I'd delete your ACLs as that's most likely to be a problem based on what limited information we have.

If you post the IP maybe we can test it.

Can you connect to port 9000 when you RDP in?

6
  • I have a node server listening on port 9000 and this is the application I am trying to access. My ssh and/or telnet request times out. I cannot connect. But telnet request specifying port 80, seems to make a connection. I just used it to check. I used the following command to connect through: ssh -vvv xxx.pem administrator@publicDNS
    – dpm
    Jan 12, 2016 at 2:19
  • the elastic IP is 52.27.160.173
    – dpm
    Jan 12, 2016 at 2:20
  • I deleted all the ACL rules I added. It has a default rule 100, allowing all traffic from all sources and another rule * denying all traffic from all sources. The problem does not go away though
    – dpm
    Jan 12, 2016 at 2:28
  • Ok since it's a windows server my SSH comments don't apply. I guess you need to open RDP or similar. HTTP and RDP seem to work fine. So I guess the problem is most likely that you have your listening application set up wrong. Can you connect to it locally with telnet, when you RDP into the machine?
    – Tim
    Jan 12, 2016 at 3:31
  • 1
    Any chance Windows local firewall is blocking the traffic? Also beware that AWS VPC network ACLs are stateless so if you use them, be sure to allow return traffic as well.
    – Jukka
    Jan 12, 2016 at 4:54

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .