I am looking at the simple server source code to create a signalling server. While a lot of example client code uses “wss://”, am I correct in assuming that with the server as written, only a “ws://” (non-secure) connection is possible, since that server source uses http instead of https?
(I’m trying to diagnose exactly where the problem I’m seeing lies, and I suspect that may be it.)
You could add certificates to the y-webrtc signaling server. However, I suggest putting the server behind a reverse proxy, which handles certificates for you.
My projects usually don’t have a convenient method to add certificates to a nodejs server, as this is usually done by reverse proxies which are better suited for encryption.