[commandbox-4.4.0] in production on Amazon EC2

Communities ColdBox HMVC
1

I’m hoping that someone has done this and/or that I’m making a simple error:

I installed commandbox on an Amazon EC2 instance and then ran:

start host=[instance private IP] port=80

Then, on the server, when I drop this into a browser, it works fine:

http://[instance private IP]

However, OFF the server, when I drop this into a browser, it produces ERR_CONNECTION_TIMED_OUT:

http://[instance public IP]

I made sure to edit the instance’s security group to allow inbound HTTP TCP on port 80 from 0.0.0.0/0.

What am I missing?

2

You need to bing to an ip that routes externally. Just bind to all ips with a host of 0.0.0.0

3

I thought it might be a host header issue so I added this to the hosts file on the server:

[instance private IP] test.domain.com

And then ran:

start host=test.domain.com port=80

And then added this to the hosts file on my box:

[instance public IP] test.domain.com

And then tried:

http://test.domain.com

Same result.

4

You need to bing to an ip that routes externally. Just bind to all ips with a host of 0.0.0.0

Brad, that did not seem to make a difference. Any other ideas?

5

[bump]

Anyone else running CommandBox in production on Amazon EC2?

6

SOLVED: add rule to Windows firewall to allow traffic on port 80.

I’m so used to dealing with IIS which, apparently, handles this for me.