incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pablo Ojanguren <pablo...@gmail.com>
Subject Re: Can not connect from the outside, only localhost is working
Date Tue, 22 Jul 2014 09:45:04 GMT
I've made following tests on my Ubuntu Box:

Configured /etc/hosts to point "local.net" to my LAN IP

*a) Set all http* properties to my LAN IP (192.168.1.103)*


   - http://local.net:9898/ -> OK
   - http://192.168.1.103:9898/ - NOK (404)
   - http://192.168.1.103:9898/atmosphere -> NOK (404) So if websockets are
   not available, atmosphere doesn't work.


*b) Set all http* properties to "local.net <http://local.net>"*


   - http://local.net:9898/ -> OK
   - http://http://local.net:9898/atmosphere -> OK
   - http://192.168.1.103:9898/ - NOK (404)


Couldn't it be a Jetty IP binding issue?






2014-07-20 22:49 GMT+02:00 Ali Lown <ali@lown.me.uk>:

> This is my guess as well, but I can't seem to get anything unhappy in
> logs to diagnose from...
>
> On 20 July 2014 21:33, Yuri Z <vega113@gmail.com> wrote:
> > well, it is ptobably related to atmosphere use instead of socket.io
> > On Jul 20, 2014 11:05 PM, "Ali Lown" <ali@lown.me.uk> wrote:
> >
> >> Ronny,
> >>
> >> Okay. I have setup a Server 2012 R2 machine to test this on, with JRE7.
> >>
> >> Using the RC5 binary, setup as above with only the 4 http_* lines
> >> adjusted to match my machine, I get 404's when attempting to access
> >> from anywhere other than localhost.
> >>
> >> So, this seems to be a Windows specific problem....
> >>
> >> @Anybody else: any thoughts?
> >>
> >> Regards,
> >> Ali
> >>
> >> On 20 July 2014 19:18, Ronny Roscher <ronny.roscher@gmail.com> wrote:
> >> > Hey Ali,
> >> >
> >> > Yes it is a Windows Server 2012 R2.
> >> >
> >> > "HomeServer.DreamScape.local", HomeServer is the name of the machine,
> >> > DreamScape the name of the domain. I'm not too familiar with that
> concept
> >> > tbh, I had to define one on installing the OS and so far it didn't
> >> > interfere with much of my network usage.
> >> >
> >> > Concerning the the firewall, I only defined the Port for TCP.
> >> >
> >> > But as I said, with the same settings the RC4 binary of WIAB is
> working
> >> > fine, I don't have to use any domain for reaching the webpage, just
> the
> >> ip
> >> > or the internet domain + :9898 at the ned and its working.
> >> >
> >> >
> >> > Best regards,
> >> > Ronny
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message