• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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