Yep, it worked that way. Thanks Ali.
On Mon, Jan 20, 2014 at 5:43 PM, Ali Lown wrote:
>
> https://serverfault.com/questions/166899/how-to-set-ip-address-of-amazon-ec2-instance-to-its-elastic-ip
>
> So, Amazon is indeed nat'ing it for you.
>
> The IP you need to enter in the config for
> http_w
https://serverfault.com/questions/166899/how-to-set-ip-address-of-amazon-ec2-instance-to-its-elastic-ip
So, Amazon is indeed nat'ing it for you.
The IP you need to enter in the config for
http_websocket_public_address is your _actual_ ip (probably 10.x.x.x),
and you can put your external ip (wave
El 20/01/14 06:35, Yuri Z escribió:
> 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?
Yuri check this:
http://stackoverflow.com/questions/tagged/amazon-ec2+websocket
it seems that it
El 20/01/14 06:35, Yuri Z escribió:
> Thanks Ali
> Yeah, waveinabox.net is a public address, it's an ubuntu machine on EC2
> using elastic ip.
And you have NAT via some firewall? any other machine/software between
the browser and the server?
--
Vicente
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
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