Just some clarification: To be able to connect via wss://192.168.2.10:10123 ("Connect via a TLS-encrypted websocket connection to IP 192.168.2.10 on port 10123") you'd have to do this: - enable TLS on the default listener on port 10123 - setup and configure TLS certificates If you'd do this this would happen: - you could no longer connect to WebIQ on ctrlX with WebIQ Designer as it expects an unencrypted connection on port 10123 That's why you don't usually want to do that. In TCP/IP you cannot have both HTTP/WS and HTTPS/WSS on the same port - this means that for using an encrypted connection you'd have to setup a separate listener on another port, e.g. 443, then you could connect using wss://192.168.2.10:443. This also means that you should be able to connect to your system from WebIQ Designer using ws://192.168.2.10:10123 instead of wss://... which is probably the solution for your issue.
... View more
