Hello!
On Tue, Aug 27, 2013 at 05:49:19PM +0100, Ben wrote:
> Nothing at all ... I promise you ! (I've been tail -f'ing the logs)
> , and I can promise you its not a DNS problem because I can see the
> NGINX default website on port 80 ;-)
The location with websocket proxy you are testing is on p
Nothing at all ... I promise you ! (I've been tail -f'ing the logs) ,
and I can promise you its not a DNS problem because I can see the NGINX
default website on port 80 ;-)
I found a workaround setting "proxy_buffering off;" in nginx makes it
work again. Don't know if this is the way it's sup
Hello!
On Tue, Aug 27, 2013 at 03:57:03PM +0100, Ben wrote:
> Hi,
>
> I've tried this with NGINX 1.4.1-1ppa1~precise and node v0.10.17 and
> just can't get it to work.
>
> What I've tried / what happens :
> (a) Yes, I have tested this direct between client code and node
> listening on 0.0.0.0 a
Hi,
I've tried this with NGINX 1.4.1-1ppa1~precise and node v0.10.17 and
just can't get it to work.
What I've tried / what happens :
(a) Yes, I have tested this direct between client code and node
listening on 0.0.0.0 and it works as expected
(b) I have tried a multitude of alternative config
