• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

Question Redirect wss:// to ws:// with Apache and ProxyPass

Lrnt

Basic Pleskian
Hi,

I need to use websocket to send command to a "Soundcraft UI12" from my (secured) website (https).
This device only accept unsecure websocket (on ws://[DEVICE_IP).
I read a lot a of things about ProxyPass/ProxyReverse and tried to use them without success.

Here what I have got :
  • OS : Debian 9.11‬
  • Plesk Onyx Version 17.8.11
  • Domain : mydomain.com on https:// (Let's encrypt certificate)
  • Device : Soundcraft Ui12 on lan (IP: 10.0.0.8)
  • Apache modules enabled : proxy, proxy_wstunnel, proxy_connect, proxy_http
I put this in the Apache Additionnal Directive on mydomain.com :

Code:
ProxyRequests Off
ProxyPreserveHost On
ProxyPass /wss ws://10.0.0.8
ProxyPassReverse /wss ws://10.0.0.8

Then I change websocket address from ws://10.0.0.8 to wss://mydomain.com/wss
But it does not work.

What am I missing?
I just want to set this without NGINX just in Apache for mydomain.com in order to send command to the device on HTTPS in Chrome.

Note: I will try to use later regex like ProxyPass /wss/(*.) ws://$1 if possible
 
Did you find a solution finally ?

A bit late... (3 years... sorry) I finally choose to do nothing else than not redirect HTTP to HTTPS.
So I was able to reach ws:// with no redirect to wss://
 
Back
Top