incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yuri Z <vega...@gmail.com>
Subject Re: Web-sockets in server.config
Date Mon, 20 Jan 2014 05:35:01 GMT
Thanks Ali
Yeah, waveinabox.net is a public address, it's an ubuntu machine on EC2
using elastic ip.
By the way, what settings are used on your demo server?

On Monday, January 20, 2014, Ali Lown <ali@lown.me.uk> wrote:

> Yuri,
>
> Does your 'server' machine have your public IP directly, or is it
> coming from some NATing device?
>
> The error you are seeing suggests that waveinabox.net:80 is not an
> address associated with a network interface on your machine, so
> attempting to listen on it makes no sense...
>
> You will need to explain your network situation a bit more...
>
> Ali
>
> On 19 January 2014 18:01, Yuri Z <vega113@gmail.com> wrote:
> > Thanks Vicente
> > My problem is that Jetty cannot bind to waveinabox.net:80, in fact in
> can't
> > bind to any host that is public.
> >
> > INFO: Transports loaded: [jsonp-polling, xhr-polling, htmlfile,
> > xhr-multipart, websocket, flashsocket]
> > 2014-01-19 17:44:03.718:INFO:oejs.AbstractConnector:Started
> > SelectChannelConnector@10.96.71.215:80
> > 2014-01-19 17:44:03.719:WARN:oejuc.AbstractLifeCycle:FAILED
> > SelectChannelConnector@184.73.205.236:80: java.net.BindExcep
> > tion: Cannot assign requested address
> > java.net.BindException: Cannot assign requested address
> >         at sun.nio.ch.Net.bind(Native Method)
> >         at
> > sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:137)
> >         at
> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77)
> >         at
> >
> org.eclipse.jetty.server.nio.SelectChannelConnector.open(SelectChannelConnector.java:173)
> >         at
> >
> org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:311)
> >         at
> >
> org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:251)
> > 2014-01-19 17:44:19.858:WARN:oejs.AsyncHttpConnection:Closing EndPoint
> > making no progress: 200 SCEP@7a9d1714{l(/84.229.3
> > .247:61375)<->r(/10.96.71.215:80
> >
> ),d=true,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=1r}-{AsyncHttpConn
> >
> >
> > On Sun, Jan 19, 2014 at 3:15 PM, Vicente J. Ruiz Jurado <
> vjrj@ourproject.org
> >> wrote:
> >
> >> El 18/01/14 22:11, Yuri Z escribió:
> >> > Hi
> >> > I have an old issue with waveinabox.net - for some reason the browser
> >> can
> >> > connect only via socket.io fallback. I think it happened since the
> >> > following settings were added.
> >> >
> >> > # A optional host:port address on which to listen for websocket
> >> connections.
> >> > # If no value is set for http_websocket_public_address it defaults to
> the
> >> > first address specified
> >> > # by http_frontend_public_address.
> >> > # Default value: localhost:9898
> >> > http_websocket_public_address = @HTTP_WEBSOCKET_PUBLIC_ADDRESS@
> >> >
> >> > # An optional host:port address for which the client is told to
> attempt
> >> > websocket connections.
> >> > # If no value is set for http_websocket_presented_address it defaults
> to
> >> > http_websocket_public_address
> >> > # Default value: localhost:9898
> >> > http_websocket_presented_address = @HTTP_WEBSOCKET_PRESENTED_ADDRESS@
> >> >
> >> > I am not sure if it's something wrong on the server side - maybe
> firewall
> >> > settings, or something with incorrect configuration...
> >> > Does anyone has these settings configured right on non local
> environment?
> >> > Would be nice to see an example.
> >> >
> >>
> >> It seems to me that the code of webclient in waveinabox.net maybe it's
> >> outdated from upstream. Socket.io was only used as a fallback if
> >> websocket does not work.
> >>
> >> More info: http_websocket_public_address just add an new IP to listen
> >> to, if you don't use it, all traffic will go to the same IP.
> >>
> >> Anyway, a running configuration. We use cloudflare CDN in kune.cc, but,
> >> cloudflare does not support websockets so we have configured one IP with
> >> normal traffic that can run via proxy (and benefit from cache, protect
> >> from attacks, etc), and other different IP for the websocket traffic
> >> (same situation cant appy if you use mod-proxy in apache, etc). So:
> >>
> >>

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