Summary
The server may be refusing to perform the request using the current protocol, but may be willing to do so after the client upgrades to a different protocol. The server sends an Upgrade header with this response to indicate the required protocol(s).
1
2
Additionally, the user may need to change their server block and allow access on port 80, as this may be causing the issue.
1
It is also suggested to use a different Nginx configuration and allowing SSL on the same port.
1
According to
See more results on Neeva
Summaries from the best pages on the web
Summary
This question is about a user who is having trouble configuring a Websocket proxy on their Nginx server, and is getting an error message with "Status Code: 426 Upgrade Required" when trying to do so. The user is advised to change their server block and allow access on port 80, as this may be causing the issue. Additionally, the user is suggested using a different Nginx configuration and allowing SSL on the same port.
How to solve Nginx WebSocket secure (wss) “error 426 Upgrade Required”? | DigitalOcean
digitalocean.com
How to solve Nginx WebSocket Secure ( WSS ) error 426 Upgrade Required? How to solve Nginx WebSocket secure (wss) “error 426 Upgrade Required”? I tried to ...
What is upgrade in WebSocket? – QuickAdviser
quick-adviser.com
HTTP Status Code 426: The server refuses to perform the request using the current ... send an Upgrade header field in a 426 response to indicate the required ...
426 Upgrade Required — httpstatuses.com
httpstatuses.com
WebSocket Nginx 426 Upgrade required I have a webchat (example.com/chat) anycodings_debian listening on tcp://0.0.0. ...
One moment, please...
anycodings.com
