Re: Nodejs websocket 502 bad gateway

2014-04-08 Thread zajca
Solved: It was my bad I had domain without ssl binded to same port as this one with ssl. So it wasn't working. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,249059,249095#msg-249095 ___ nginx mailing list nginx@nginx.org http://mailman.nginx

Re: Nodejs websocket 502 bad gateway

2014-04-07 Thread Maxim Dounin
Hello! On Mon, Apr 07, 2014 at 07:38:00AM -0400, zajca wrote: > I'm trying to make work nginx 1.4.7 with nodejs websockets > but I'm getting 502 bad gateway > > NGINX Error: > [error] 2394#0: *1 upstream prematurely closed connection while reading > response header from upstream, client: 127.0.0

Nodejs websocket 502 bad gateway

2014-04-07 Thread zajca
I'm trying to make work nginx 1.4.7 with nodejs websockets but I'm getting 502 bad gateway NGINX Error: [error] 2394#0: *1 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: xxx.cz, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:8