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 wrote:
> Yuri,
>
> Does your 'server' machine have your public IP directly, or is it
> coming from so
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
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/16751/#review32267
---
Ship it!
LGTM.
- Ali Lown
On Jan. 13, 2014, 3:07 p.m., Pablo Oja
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17105/#review32266
---
Ship it!
LGTM.
- Ali Lown
On Jan. 19, 2014, 8:52 p.m., Yuri Zeli
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17105/
---
Review request for wave, Ali Lown and Vicente J. Ruiz Jurado.
Repository: wave
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
SelectChann
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
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/16751/#review32258
---
Ship it!
Ship It!
- Pablo Ojanguren
On Jan. 13, 2014, 3:07 p.m.,
