0

My EC2 instance does not answer pings or requests from a certain network, while it does answer pings from other ones. This causes my webapp to crash for that network. The particular network where it's failing right now is an open public network at a large university. The transfer protocol is HTTP going to port 3000. What could be the problem, and how can I resolve it?

I'm pretty new to server administration, so if I should provide any other details, I would be glad to.

Edit: My security groups:

TCP to port 3000 (Node.js) from everywhere  
TCP to port 22 (SSH) from my working IP  
TCP to port 80 (HTTP) from everywhere  
TCP to port 443 (HTTPS) from everywhere  
All ICMP from everywhere

All outbound traffic is allowed.

Improve this question
3
  • Show traceroute from a good network, and traceroute from a bad network?
    – Slartibartfast
    Apr 3, 2014 at 0:09
  • The SGs look ok. My answer below still stands.
    – EEAA
    Apr 3, 2014 at 0:28
  • Traceroute from university network chokes up after two hops. I guess we're opening a ticket with them, then.
    – sg.cc
    Apr 3, 2014 at 0:35

1 Answer 1

Reset to default
0

Assuming you've verified that:

  1. Your security groups are not blocking these
  2. You don't have iptables rules that would be blocking anything

the only thing you can do is open up a ticket with AWS support. Additionally, you should talk with the IT department of this University to see if they might be blocking your traffic.

Improve this answer
1
  • Thank you for the comment, I will include my security groups in the question.
    – sg.cc
    Apr 3, 2014 at 0:13

You must log in to answer this question.

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