Initial stream delay across NGINX proxy

Setting up websocket communication using django-channels with NGINX as a proxy may be causing delay issues with Server-to-Client streams. The Server has to send exactly 24 messages regardless of message speed to the Client across the websocket before the Client begins to receive any data.

• Client connected directly to Django test server streams fine
• Client connected directly to Daphne streams fine
• With NGINX acting as proxy neither Django test server nor Daphne server streaming works until after 24 messages have been sent from Server
• Replaced Django server with Node.js socket server and streaming worked fine across NGINX proxy
• Tested connection to Django server through NGINX with both browser and Node.js wscat connection and stream delay existed on both
• If we send a message on connection (from Client to Django server) through NGINX proxy, streaming from server begins to function immediately after initial message

Given the above we believe the problem may exist within django-channels as the problem only appears when django-channels is integrated under a proxy with NGINX while Node.js client/server websocket architecture functions as expected.

[andrewgodwin]

Ah, good to know. Thanks for leaving an update!

[MCBama]

Yet another Update

You probably already received an email update about my last update…but it turns out the only other change I made in addition the the version update was to change the NGINX listen port from default port 80 to port 8000 and out of curiosity I reverted that change and found out that it was actually the port change that had fixed the problem.

Thus…this is probably not your problem after all. I apologize for wasting your time chasing a wild goose.