Strider not serving pages from AWS

[mark-norgate]

Hi there

I am having difficultly getting Strider to serve pages on AWS. I don't mind sharing the URL: ec2-107-21-10-218.compute-1.amazonaws.com. I have been following the instructions on this github site as well as these instructions.

I have variously tried appending a port of 3000, and of course making corresponding changes in the the Ubuntu config, as well as prepending protocols and so on but to no avail. If I try to request a page from port 80, it hangs for a while but then gives up, whereas from port 3000 it used to return immediately, but having just checked this it seems to be taking some processing time now.

What could be the issue? The Strider logs are empty and I don't know if Apache is required for Strider to run. Can someone point me in the direction of something that might throw some light on the subject?

Thanks! Mark

[AdolfVonKleist]

That tutorial page doesn't seem to say anything about the security group for your instance.

By default your instance will typically have all ports except ssh (22) closed to the world. You need to explicitly open anything else in your attached security group (you can do it after the fact in your AWS console in the section related to your instance.) I'd double check this.

I dunno about all that IP tables stuff. If you don't want to use Apache/nginx it seems like it would be easier to just test serve Strider directly on port 80.

[mark-norgate]

Hi Josef

Yes I was aware that there would be security group issues, and I did allow port 3000 through, as well as port 80, but it made no difference. It timed out after a minute or so. I guess it if it were to reject the request immediately it would be easier to solve!

Mark

[knownasilya]

How is your mongo setup?

[mark-norgate]

MongoDB reports to be working fine. Again, some Strider logs would be beneficial!

[knownasilya]

set DEBUG=* in your envs.