wss: Error during WebSocket handshake: Unexpected response code: 200

[lpinca]

This is strange. Did you try with other browsers? Does it work with Firefox?
The strange thing is that you get a 200 status code. It seems that you are not hitting the WebSocket server as it will never answer with 200. Is there a proxy in the middle?

[Ratismal]

The site itself is rerouted through a nginx reverse proxy. Firefox and Chrome work fine, I've only seen this issue on Chromium. My project is open-source; would it help if I provided you my source code + wss url to help you debug?

[lpinca]

Maybe, but if you have already isolated the issue to be Chromium specific I think there is not much I can do.
Does it work if you connect directly to the server via Chromium bypassing nginx?

[lpinca]

Closing this as I think there is not much we can do. @Ratismal please reopen if needed.

[Ratismal]

Fair enough. Thank you for your support.

[mklimek]

A fix for me was setting these response headers: _Host_, _Connection_ and _Upgrade_.
For nginx case (socket.io server is behind the proxy):

```nginx
location /foo/ {
proxy_pass http://foobar:3005/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
}

[venkateshthallam]

@mklimek This worked great for my setup. Thanks.

[PassTheMayo]

@mklimek Worked for me! Thank you!

[naknode]

@mklimek @venkateshthallam @PassTheMayo You guys are commenting on ws library whereas @mklimek mentioned socket.io. What libraries are you guys using?

[PassTheMayo]

@naknode Read the previous comments, this issue was resolved.

[lf1029698952]

nginx don't support websocket，but it can proxy websocket connetions，you neet config it:
location / {
proxy_pass http://backend;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}

Reference link:
http://nginx.org/en/docs/http/websocket.html

[xingchen19]

A fix for me was setting these response headers: _Host_, _Connection_ and _Upgrade_.
For nginx case (socket.io server is behind the proxy):

location /foo/ {
    proxy_pass http://foobar:3005/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
}
`

resolved my issue

[memstone]

@mklimek This worked great for my setup. Thanks.

[leeroya]

@mklimek , that worked 100%.
I am using signalR with Angular and that was the final piece of the configuration.

[joviqiao]

I think your server used sockjs, client not use.

[kjr247]

Any note on how to solve this in IIS using nodeiis?

[aleksandar-kandzhichki]

Any note on how to solve this in IIS using nodeiis?

What we use is:
in <system.webServer> add
<webSocket enabled="false" />

then in add
<rule name="WSockets"> <match url="/socket.*" /> <conditions> <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="True"/> </conditions> <action type="Rewrite" url="backend/server.js"/> </rule>
this makes the IIS proxy the WS request to your backend. We are sending open request to domain/socket and handling it in node.js (or whatever you use) server on the backend

[tmacharia]

A fix for me was setting these response headers: _Host_, _Connection_ and _Upgrade_.
For nginx case (socket.io server is behind the proxy):

location /foo/ {
    proxy_pass http://foobar:3005/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
}

I think this was a general web socket issue, i experienced the same error while working with SignalrR for an asp.net core site hosted on linux.

I changed nginx config file specifying 'proxy_set_header Connection "upgrade"' and everything worked.

Thank you for your suggestion sir!

[AdamZaczek]

A fix for me was setting these response headers: _Host_, _Connection_ and _Upgrade_.
For nginx case (socket.io server is behind the proxy):

location /foo/ {
    proxy_pass http://foobar:3005/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
}

A hero can be anyone, even a man doing something as simple as putting a working nginx config in Github issues.

[RamyTayseer]

A fix for me was setting these response headers: _Host_, _Connection_ and _Upgrade_.
For nginx case (socket.io server is behind the proxy):

location /foo/ {
    proxy_pass http://foobar:3005/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
}

Kindly, referring to your solution above, I need to apply it using apache as I have the same issue, so please feedback me about the needed code for apache.

[rdefulio]

proxy_set_header Host $host;

this saved my life tonight. Thank you!

[leefsmp]

I not able to solve the issue on my AWS ElasticBean instance... maybe someone could provide some much appreciated insights on what is the problem with my nginx config file below:
files:
"/etc/nginx/conf.d/upload.conf" :
mode: "000755"
owner: root
group: root
content: |
client_max_body_size 500M;

server {
    listen 8081;

    #server_name xxx.elasticbeanstalk.com

    # prevents 502 bad gateway error
    large_client_header_buffers 8 32k;

    # enables WS support
    location / {
      proxy_pass http://localhost:5000;
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";
    }
}

[PrakashLakhara]

Any one can provide the same solution for apache ?

[devboosters]

A fix for me was setting these response headers: _Host_, _Connection_ and _Upgrade_.
For nginx case (socket.io server is behind the proxy):

location /foo/ {
    proxy_pass http://foobar:3005/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
}

Amazing, worked for me too like a charm, as i was banging my hand since a couple of days on account of setting this reverse proxy configuration in nginx,
Thanks a lot man you made my day :)

[NFDeap]

How I can create this header in apache?

[theavuthnhel]

This document is for those who use laravel-echo-server & Nginx & socket.io & Redis-server with the separated server between client project and Redis-server.

Please follow the link here.

Thanks

[akinsikuoluwafemi]

Is there any fix for those who are hosting on Heroku and not Nginx?