Closed 0-wHiTeHand-0 closed 3 months ago
At least libwebrtc shipped a short, hard-coded list of trusted CAs that didn't include Let's Encrypt for quite a while. I think that has been fixed by now, but I'm not sure, and I think I've seen other client libraries with the same issue. If the client code you're using allows for disabling certificate validation (libwebrtc does), that might be the easiest workaround. (Assuming you're using TLS just as a fallback for circumventing restrictive firewalls, as opposed to being interested in its security properties for TURN.)
Hi,
I have been using the TCP TURN server for a while, and it works pretty well. However, today I was trying to enable TURNS with my Lets Encrypt certificate, and I always get the following error when connecting to the TURNS server from a TURNS client:
I've been looking around, and couldn't find anything about this error in eturnal or coturn; can someone throw some light into this? I use the certificate for my nginx too, and it works good. Also, if I connect to the TURNS server using openssl s_client, the connection is successfully established. Weird.
Thanks!
Eturnal config: