[Solved] Bug when logging in

[San1ty]

When I try to log in it seems that the forum doesn't immediately realize that I am (It'll keep showing log in as a possibility in the header).
It takes a couple of seconds browsing different pages before the header indicates I'm logged in.

[San1ty]

Might this be due to being behind a company proxy that blocks any traffic besides 80 and 443 ports?
I also get this error message in my console on chrome:

WebSocket connection to 'ws://community.nodebb.org/socket.io/1/websocket/blockofrandomletters' failed: Error during WebSocket handshake: Unexpected response code: 502

[Siber]

What version is your nginx? I fix a similar issue by updating nginx to 1.3+

[San1ty]

I'm talking about the version running here (community.nodebb.org). Do you experience any issues when logging in here?

[Scuzz]

Everything is working fine for me.

[julian]

@san1ty Most likely your company firewall is blocking the websocket traffic. Give this test a go, what does it say?

[San1ty]

@julian Spot on!

The WebSockets test - Does your browser supports WebSockets?

(websocketstest.com)

[julian]

Ok - at present the underlying websockets library will attempt to connect using websockets first, and failing that, drops down to ajax polling. This is why it takes a couple seconds.

As long as you eventually get connected, it's okay, although we do realise that it is a problem for some people.