mrAndywendy

Also the same issue discovered in Korea, some users can not connect to the server. The connection to websocket is OK, but PeerConnection is timeout.

Yes, the server is self-deployed. We tried your test-tool and if user uses mobile internet or some providers it displays error could not connect PeerConnection after timeout via VPN it...

No, WebSocket is OK, it connects and receives data. Problem is with TURN, as I understand.

Yes, TURN is enabled. I will attach the config.

webhook: api_key: 'key1' urls: - 'https://connect.xxx.com/api/livekit/webhook' log_level: error rtc: port_range_start: 50000 port_range_end: 60000 tcp_port: 7881 use_external_ip: true packet_buffer_size: 3000 pli_throttle: low_quality: 5s mid_quality: 5s high_quality: 5s stun_servers: - dev-turn.xxxx.com:3478 turn:...

We used it with disabled TURN, but on test tool it does not pass, so we enabled it back.

Unfortunately  We used an external IP address and an internal. Sometimes it connected, but after page reloading it could not connect.

We used extended log mode on the livekit server looks like it does not sense. The only one error is in a log livekit-server[1566650]: 2023-02-01T03:00:28.056-0600#011ERROR#011livekit.turn#011logger/logadapter.go:108#011error when handling datagram: failed to...