• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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