Thanks so much Matt! On Wednesday, 25 May 2016 18:58:23 UTC+10, Matt Bray wrote: > > Two things: > > * Ask elm-reactor to bind to all addresses, not just localhost, using > "elm-reactor -a 0.0.0.0". > * On EC2, for your instance's security group, make sure there is a rule > allowing inbound TCP traffic on port 8000. > > Note that you incur the (small?) risk of someone exploiting an unknown > vulnerability in elm-reactor to take over your server - remember > elm-reactor is just a development tool. You can mitigate this by only > allowing access via your home IP address in the security group rule. > > On Wed, 25 May 2016 at 09:35 Stephen Oates <[email protected] > <javascript:>> wrote: > >> I am wondering how to access the Elm-Reactor when the server is remote? I >> have installed elm and run "elm-reactor" but when I go to my EC2s instace >> address on port 8000 I cannot connect to anything. I have checked the port >> settings and even tried changing them but no luck. >> >> Does anyone have any suggestions on what I need to do? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Elm Discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> >
-- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
