This message was deleted.

cc @echoing-kitchen-90064 who might know?

Hey Diego, I have not seen this error before. Looks like it is specific to TURN, but the connection test seems to be able to connect to TURN. Doing some research, I see this error can be related to older versions of chrome. Can you share what browser/version you're using? Also, can you share the config setup you have for TURN in your config similar to https://github.com/livekit/livekit/blob/master/config-sample.yaml#L58 ?

Yeah, I appreciate your time to look into this and help me, below the Chorme version I'm using and this is the config:

turn:
    enabled: true
    domain: <http://turn.MY_DOMAIN.com|turn.MY_DOMAIN.com>
    tls_port: 5349
    udp_port: 3478
    secretName: TURN_SECRET_AKS

I'm creating the TURN_SECRET_AKS using a file like this:

apiVersion: v1
data:
  tls.crt: BASE_64_CRT
  tls.key: BASE_64_KEY
kind: Secret
metadata:
  name: TURN_SECRET_AKS
  namespace: default
type: <http://kubernetes.io/tls|kubernetes.io/tls>

passing CRT and KEY pre created in base64

this thread seems to indicate that 3478 is the correct port to use... https://livekit-users.slack.com/archives/C01KVTJH6BX/p1690786467050499

Good, thanks for sharing Dan, I'll try to change port and browser and I'll keep you posted!

In general these ICE warnings are not a huge deal. as long as the tests are passing, I'd say you are good