How to add TLS support to a websocket server for wss to work? about async-tungstenite HOT 2 CLOSED

If you omit the whole WebSocket part, can you accept connections via that TCP connection? I have no idea how these things work with wasm and if it's even supposed to work like this.

In any case this doesn't look like an error coming from async-tungstenite but something from your TLS stack.

EDIT: Is there a function in async-tungstenite that I can use directly to accept a client connection over wss automatically instead of using async-tls?

There isn't. You'd set up your connection accepting code yourself and then once that's done pass the connections to async-tungstenite.

from async-tungstenite.

@sdroege you are right! regenerating the key file as a .rsa instead of .pem fixed the problem for some reason. thank you for an excellent lib!

from async-tungstenite.