• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue I have problem 426 No Sec-WebSocket-Protocols requested supported

arabtion

New Pleskian
all my websocket fine but i get err 426 No Sec-WebSocket-Protocols requested supported plesse help me
Screenshot_526.png
Screenshot_527.png
location /socket/ {
proxy_pass http://xx.xx.x.xx:2589;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
Screenshot_528.png
anyone can help me where wrong
 
So a few things I can think of. Since this is HTTP response 426 it's basically means upgrade required. The way you have your nginx set up one thing you can try to do is do away with the upgrade proxy headers and see what happens. So it goes from:

NGINX:
location /socket/ {
    proxy_pass http://xx.xx.x.xx:2589;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
}

To

NGINX:
location /socket/ {
    proxy_pass http://xx.xx.x.xx:2589;
}

Another thing to try is, if the application is running on the same server, is to not use the public IP address but instead the local loopback (127.0.0.1) since this is done on the backend anyways and does not affect what the end user will get.
 
So a few things I can think of. Since this is HTTP response 426 it's basically means upgrade required. The way you have your nginx set up one thing you can try to do is do away with the upgrade proxy headers and see what happens. So it goes from:

NGINX:
location /socket/ {
    proxy_pass http://xx.xx.x.xx:2589;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
}

To

NGINX:
location /socket/ {
    proxy_pass http://xx.xx.x.xx:2589;
}

Another thing to try is, if the application is running on the same server, is to not use the public IP address but instead the local loopback (127.0.0.1) since this is done on the backend anyways and does not affect what the end user will get.
i test all thing i get same problem 426
 
i use this config
location ^~ /socket {
#add_header 'Access-Control-Allow-Origin' '*';

proxy_pass http://127.0.0.1:2589;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Client-Verify SUCCESS;
proxy_set_header X-NginX-Proxy true;
proxy_read_timeout 60;
proxy_connect_timeout 60;
proxy_redirect off;

proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
 
Back
Top