TUN host lookup received error.,

Client SDKs
,
1

we’ve been seeing these errors for few days now and room joining and access creation endpoints are taking 17+ seconds.

we are not using any vpn or customized services.

_app-ca3b851950aef5f9.js:99 [RTC_CLIENT] pub conn: ice candidate error - code: 701, text: STUN host lookup received error., url: stun:ip-143-223-91-49.host.livekit.cloud:3478
(anonymous) @ _app-ca3b851950aef5f9.js:99
emit @ _app-ca3b851950aef5f9.js:105
e.pc.onicecandidateerror @ _app-ca3b851950aef5f9.js:105Understand this error
2_app-ca3b851950aef5f9.js:99 [RTC_CLIENT] pub conn: ice candidate error - code: 701, text: TURN host lookup received error., url: turn:ip-143-223-91-49.host.livekit.cloud:3478?transport=udp
(anonymous) @ _app-ca3b851950aef5f9.js:99
emit @ _app-ca3b851950aef5f9.js:105
e.pc.onicecandidateerror @ _app-ca3b851950aef5f9.js:105Understand this error
3_app-ca3b851950aef5f9.js:99 [RTC_CLIENT] pub conn: ice candidate error - code: 701, text: Address not associated with the desired network interface., url: turns:lms-google-cloud-henrf1gr.turn.livekit.cloud:443?transport=tcp
(anonymous) @ _app-ca3b851950aef5f9.js:99
emit @ _app-ca3b851950aef5f9.js:105
e.pc.onicecandidateerror @ _app-ca3b851950aef5f9.js:105Understand this error
3_app-ca3b851950aef5f9.js:99 [RTC_CLIENT] pub conn: ice candidate error - code: 701, text: Address not associated with the desired network interface., url: turns:omumbai1a.turn.livekit.cloud:443?transport=tcp

console [RTC_CLIENT] pub conn: ice candidate error - code: 701, text: STUN host lookup received error., url: stun:ip-149-118-69-113.host.livekit.cloud:3478 12:13:11.741
logger “console”
arguments [ “[RTC_CLIENT] pub conn: ice candidate error - code: 701, text: STUN host lookup received error., url: stun:ip-149-118-69-113.host.livekit.cloud:3478” ]

User-Agent

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36

browser (browser)

name

Chrome

version

147.0.0

culture (culture)

calendar

gregory

**locale
**
device (device)

brand

Apple

family

Mac

model

Mac

os (os)

name

Mac OS X

version

10.15.7

react

version

18.3.1

image
image2096×1666 441 KB

2

Did you update any of your firewall settings recently? It feels like the delay could be caused by the client trying different connections: Connecting to LiveKit | LiveKit Documentation

3

Yes, but before reporting this to you guy, i already tried wildcard access to all ports but it didn’t help. i do see the issue mentioned on your status page. We started having these issues around the same week.

image
image2314×1600 443 KB

4

Also, livekit doesn’t work under dns change. i tested it with cloudflare warp with only dns enabled. audio and video goes out completely.

5

That incident, LiveKit Status - Increased Latency in RoomService APIs, brief period of higher error rate , has been fully resolved and all of the customers who originally reported it have said they no longer see the issue. So, I don’t believe this is related to what you are seeing (the error messages are also different)

What do you see in the connection tester? Connection Tester | LiveKit

So, just going back to your original issue. Joining a room is taking 17+ seconds. Is this only with Chrome on mac? Or that was just the environment you tested with.

Is there a pattern to which clients see a delayed connection, or is it all clients?