Can't get it working with NginX

[catamphetamine]

If i insert this into my nginx config

map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

...

    location /socket.io/ {
        proxy_pass http://localhost:8080;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
    }

Most times it won't connect - it's stuck.
Sometimes it connects after being stuck for some time.

[catamphetamine]

this is so difficult to make it work behind a proxy.
some detailed logs could help.

[catamphetamine]

and no one on the internet has a working example.
just meaningless pieces of config.

[catamphetamine]

maybe i should resort to using bare websockets.
too much complexity for a simple library.

[catamphetamine]

bare websockets don't work too.
i think i just won't use websocket proxying at all - it isn't usable yet.

[catamphetamine]

wasted 3 hours on such a stupid thing.
those who tell you websocket proxying works are liars.

[reqshark]

your nginx.conf file is all wrong, make sure you have nginx 1.4 or higher because this is not a socket.io issue.

[catamphetamine]

If no one knows how to make your software work in a real world use case then it's not "not a socket.io issue", it is an issue.
I managed to get it working in the simplest case but advanced use case still fails.
If you have interest in how to get socket.io working with nginx and why the advanced use case may fail you can check out my example:
https://github.com/kuchumovn/nginx_node_websocket_example

For now the simplest use case is sufficient for me, but still some features of socket.io fail to work out with nginx.

[catamphetamine]

Another 5 cents from me:

For some strange reason "localhost" doesn't work with websockets when proxying, but 127.0.0.1 does work (spent a couple of hours to nail this bug)