To clarify the situation (I presume you use chrome).
The website is downloaded via http or https (depending on the protocol you type in).
Regardless of this, your login, and communication with our API’s is via https.
When you then connect to a server via websocket it is ws (not wss). No personal/confidential information is sent over this connection. Unfortunately it’s more than a “quick switch” to swap this over to be an encrypted wss connection.
Chrome by default will fail any ws connection on a https website. Unfortunately, the ironic “easy” fix, is to access the website in an even less secure fashion (http).
A more secure user-side solution for now is to click the “lock” symbol next to the URL, go to “Site Settings”, and change “Insecure Content” to “Allow”. That way, the site is still loaded via https, your api communication is still https, and it’s simply the websocket that is not encrypted.
On many other browsers (firefox, etc.), I believe they do not place this limitation on websockets, so you should be able to use the dashboard via https without changing any settings.