Help needed NGINX reverse proxy to NODE.JS

Maxim Dounin mdounin at
Tue Aug 27 17:14:59 UTC 2013


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 port 80 
too.  Do you see other requests to the host in access log?

> I found a workaround setting "proxy_buffering off;" in nginx makes
> it work again.  Don't know if this is the way it's supposed to be
> and/or a recommended way to do things ??

The fact that it helps indicate that connection is ok (that is, 
you should see it in access log once it completes - unless you 
disabled access logging or looking into wrong logs), but isn't 
considered to be upgraded to a websocket protocol for some reason.

Most obvious reason I can think of is an old version of nginx 
actually running, the one without websocket proxy support 
(something before 1.3.13 instead of 1.4.1 you claim in your 
initial message).  It's trivial to check by looking into Server 
header line returned.

If still no lock, try configuring a debug log and obtaining one 
while trying a websocket request, see for details.

Maxim Dounin

More information about the nginx mailing list