3

I have an Amazon Web Services EC2 instance with a Windows Server 2012 AMI on it. I have installed XAMPP on it, and have started the apache server from the XAMPP Control Panel. It starts successfully.

Also in the AWS Dashboard, I have added rules to the relevant Security Group for the Instance, as detailed in linked image (I don't have enough reputation yet to post an image):

AWS EC2 Instance Security Group Settings

I have replaced the actual source ip setting for the inbound traffic with xxx.xxx.xxx.xxx/32 in this image, but it is set to the ip from which I am trying to establish the http connection, so I am not sure why I am unable to establish an http connection? I have also tried allowing inbound HTTP traffic via port 80 from all sources, by specifying ip 0.0.0.0/0, same problem.

I am trying to establish the http connection via my browser, simply by using the AWS instance public dns/ip, e.g.

http://myAWSinstancedns.compute.amazonaws.com

or

http://myAWSinstancedns.compute.amazonaws.com/xampp/splash.php

When try the same thing from within the AWS instance, using localhost, it works, but not from outside.

Anyone any idea?

2 Answers 2

0

Sounds like Apache may be configured to only accept connections from the local host. Have you tried accessing the website from the hosting server via the public address? Also, for testings sake, I would probably put the 0.0.0.0/0 rule back into place until you figure out the issue. Simplicity!

4
  • Hi Spencer, thanks for your response. I have changed the http rule to allow connections from anywhere, as you suggested, for testing. Anyway, from within the instance, I am able to connect via the public dns as well. But from outside, still not able to connect. Sep 13, 2014 at 20:06
  • Just an update, I also posted on aws forums, and was suggested to check if the instance is running a firewall, which it is, so I turned it off. But I still cant connect from outside. Also, I ran netstat -anp tcp | find ":80" and got this output, so it seems it is listening: C:\Users\Administrator>netstat -anp tcp | find ":80" TCP 0.0.0.0:80 0.0.0.0:0 LISTENING TCP 172.31.34.244:49397 199.193.196.18:80 CLOSE_WAIT TCP 172.31.34.244:50988 169.254.169.254:80 CLOSE_WAIT Sep 13, 2014 at 20:19
  • aha, I had only turned off the firewall for the domain profile, not for the public profile. Now it works! Sep 13, 2014 at 20:26
  • 2
    Just for completeness, I now turned the firewall back on, but created a rule to allow communication via port 80 for http and another port for my BOSH service. Sep 13, 2014 at 20:32
0
  1. Create a second instance on the same subnet and on the same security group and see if you can access the http server. If so that points to security group or ACL issues. If not, then
  2. Check if the http server accepts connections on 0.0.0.0/0 or only 127.0.0.1 (localhost). One allows it to accept only local connections while other allows it to accept incoming connections.

You must log in to answer this question.

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