So after upgrading to 0.4.0, I'm dealing with a situation where my site works just fine in FF, but fails to load properly in Chromium browser.
From Chromium Web console, I get messages like:
'ws://forum.linuxbsdos.com/socket.io/1/websocket/91qNRaWZ3rYcF-mt333a' failed: Unexpected response code: 502 http://forum.linuxbsdos.com/
Failed to load resource: the server responded with a status of 504 (Gateway Time-out) http://forum.linuxbsdos.com/socket.io/1/xhr-polling/91qNRaWZ3rYcF-mt333a?t=1396434040701
Failed to load resource: the server responded with a status of 504 (Gateway Time-out)
And in Nginx error log file, I see:
When the site does not load.
*3345 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: forum.linuxbsdos.com, request: "GET /socket.io/1/xhr-polling/_wPAI1JGYSBw2sCntjYj?t=1396431796572 HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/1/xhr-polling/_wPAI1JGYSBw2sCntjYj?t=1396431796572", host: "forum.linuxbsdos.com", referrer: "http://forum.linuxbsdos.com/topic/62/wayland-in-gnome-3"
And when the home page loads, but the sidebar does not
2089 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: forum.linuxbsdos.com, request: "GET /socket.io/1/websocket/91qNRaWZ3rYcF-mt333a HTTP/1.1", upstream: "http://127.0.0.1:4567/socket.io/1/websocket/91qNRaWZ3rYcF-mt333a", host: "forum.linuxbsdos.com"
I've tried adding these lines to my Nginx config for the subdomain, but that didn't help.
proxy_buffers 8 32k;
large_client_header_buffers 8 32k;
I have no clue why the site works in FF, but not in Chromium. Anu clues?