TURN server connectivity test fails with IP-based TLS certificate

Self Hosting
1

This question originally came up in our Slack community and the thread has been consolidated here for long-term reference.

I’ve deployed LiveKit on a VPS without a load balancer. Everything works except the TURN part - the connectivity test fails on the TURN step.

My setup uses a TLS certificate issued for a raw IP address (not a domain name) as the tls_domain.

Could this be causing the TURN test to fail? Does LiveKit’s TURN server require a proper domain name for TLS?

2

If the embedded TURN service in LiveKit is failing with an IP-based TLS certificate, you can use an external TURN server like coturn instead.

This workaround has been confirmed to work successfully when the built-in TURN server has issues with non-domain certificates.