we've been seeing these errors for few days now and room joining and access creation endpoints are taking 17+ seconds:
_app-ca3b851950aef5f9.js:99 [RTC_CLIENT] pub conn: ice candidate error - code: 701, text: STUN host lookup received error., url: stunip 143 223 91 49.host.livekit.cloud3478
(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: turnip 143 223 91 49.host.livekit.cloud3478?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: turnslms google cloud henrf1gr.turn.livekit.cloud443?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: turnsomumbai1a.turn.livekit.cloud443?transport=tcp