When you deploy DMX at a remote server you have to configure dmx.websockets.url accordingly.
You have to specify the domain or IP address of your server, e.g. ws://www.myserver.com:8081.
The port must match your dmx.websockets.port setting (8081 by default). If your server does HTTPS use wss: as the protocol instead ws: (anyways your config shows you’re not using HTTPS).
If you don’t set dmx.websockets.url properly the DMX Webclient can’t establish a WebSocket connection to the server. This results in the “No WebSocket connection open” error you’re currently experiencing.
To check whether the webclient can establish the WebSocket connection open the browser console. When the webclient starts the console output is supposed to look like this:
BTW: you’re recommended to install the latest DMX snapshot (instead the Beta 2 release). This will raise the possibility you can migrate your data to the upcoming Beta 3 release.
https://download.dmx.systems/ci/dmx-latest.zip
Thank you for the question as it helps us with improving the DMX docs!