...
There are two parts to making this work -
- having the client connect on wss: port 443
...
- having the proxy forward the events URL to the websocket for OMK.
Request the clients browser to use 443 for the websocket
...
Code Block | ||||
---|---|---|---|---|
| ||||
'websocket_proxy_port' => '443'
or in opCommon.json:
"websocket_proxy_port": "443", |
After updating the opCommon configuration, restart the omkd daemon.
Proxy the connection from your SSL/TLS termination to the OMK webservice
...
Code Block | ||
---|---|---|
| ||
<VirtualHost *:443>
SSLEngine on
SSLProxyEngine on
ServerName some.example.com
ProxyPass "/en/omk/opCharts/events/log" "ws://localhost:8042/en/omk/opCharts/events/log"
ProxyRequests off
RequestHeader set X-Forwarded-Proto "https" |
After updating the Apache configuration, restart the Apache daemon.
Info | ||
---|---|---|
| ||
Proxy WS Tunnel module WSS HTTPS interaction Please note apache will force the use of WSS (SSL websocket) if you are using HTTPS. This is because the apache configuration: RequestHeader set X-Forwarded-Proto "https" |