LiveKit Community

Screen Shot 2022-10-04 at 5.07.27 PM.png

Hey David, can you confirm if you are connected via TURN/TLS or regular TURN?  To check, you can visit <chrome://webrtc-internals> and see the specific TURN url it ended up using (attached)

Even if it's using TURN/TLS properly, there could still be strict corporate firewalls that ends up blocking the domain/IP. Certain customers may need to whitelist your domain in their firewall rules

image.png

I see a few instances of RTCIceCandidate_… (local-candidate). They differ in networkType and priority but otherwise look the same. url is the same on all of them (see screenshot).

Does this mean it’s not using TURN/TLS?

I’m reading the docs for firewall settings <https://docs.livekit.io/deploy/ports-firewall/>. Could the problem be that I have defined turn.tls_port in my config yaml  while also using a load balancer?

correct, try removing the `udp_port: 443` from your config.. having it may be causing the browser to prefer TURN/UDP instead of TURN/TLS.

removing `udp_port: 443` from the config seemed to do the trick. I’m now seeing my browser use TURN/TLS. Thanks for the help!