This message was deleted.
# helpdesk
s
This message was deleted.
f
Copy code
LOG  room event connectionStateChanged {"args": ["connecting"], "event": "connectionStateChanged"}
 DEBUG  ConnectionStateChanged >  connecting
 LOG  room event audioPlaybackChanged {"args": [false], "event": "audioPlaybackChanged"}
 DEBUG  [onAudioPlaybackStatusChanged] roomCanPlay:  false
 LOG  connecting to <wss://maum-nbtvlj09.livekit.cloud/rtc?access_token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE3MDI5ODgxNDIsImlzcyI6IkFQSWd0WmRueHlEcFlhQSIsIm5hbWUiOiI4ODQiLCJuYmYiOjE3MDI5MDE3NDIsInN1YiI6ImVmYmJjZTQwLTY2OTgtNGQ4OS1hYmIwLTRmNmM3MWZkZjVmZiIsInZpZGVvIjp7InJvb20iOiJhYWZiMGIxMC1lYmVhLTQxYWMtOTg3ZC1lNTg1MjgwZWQwNTYiLCJyb29tSm9pbiI6dHJ1ZX19.22q2RSz7oQMMjjJbxEyXrHpOWo-wIIx8HVqteVVDHSU&auto_subscribe=1&sdk=reactnative&version=1.15.4&protocol=11&os=ios>
 LOG  ping config {"interval": 5, "timeout": 15}
 LOG  clearing ping interval
 LOG  start ping interval
 LOG  rn-webrtc:pc:DEBUG 0 ctor +0ms
 LOG  rn-webrtc:pc:DEBUG 1 ctor +5ms
 LOG  connected to Livekit Server edition: 1, version: 1.5.1, protocol: 11, region: Japan, nodeId: NM_VNRTA_djAR7rnTQSGC, debugInfo:
 LOG  room event signalConnected {"args": [], "event": "signalConnected"}
 LOG  received server offer {"RTCSdpType": "offer", "signalingState": "stable"}
 LOG  rn-webrtc:pc:DEBUG 1 setRemoteDescription +20ms
 LOG  rn-webrtc:pc:DEBUG 1 setRemoteDescription OK +5ms
 LOG  rn-webrtc:pc:DEBUG 1 addIceCandidate +0ms
 LOG  rn-webrtc:pc:DEBUG 1 addIceCandidate +0ms
 LOG  rn-webrtc:pc:DEBUG 1 addIceCandidate +0ms
 LOG  rn-webrtc:pc:DEBUG 1 addIceCandidate +0ms
 LOG  rn-webrtc:pc:DEBUG 1 createAnswer +1ms
 LOG  setting munged local description
 LOG  rn-webrtc:pc:DEBUG 1 setLocalDescription +3ms
 LOG  rn-webrtc:pc:DEBUG 1 setLocalDescription OK +1ms
 LOG  sending answer
 LOG  pc state change: from NEW to CONNECTING
 LOG  primary PC state changed 1
 LOG  room event participantDisconnected {"args": [{"_connectionQuality": "unknown", "_events": [Object], "_eventsCount": 13, "_maxListeners": 100, "audioLevel": 0, "audioTracks": [Map], "identity": "d610c2a6-f825-426a-906b-f3ab43871ef7", "isSpeaking": false, "metadata": "", "name": "935", "participantInfo": [Qe], "permissions": [ze], "sid": "PA_3UndnMpR65xB", "signalClient": [ys], "tracks": [Map], "videoTracks": [Map], "volumeMap": [Map]}], "event": "participantDisconnected"}
 DEBUG  [handleParticipantDisconnected]
 INFO  disconnect from room {"identity": "efbbce40-6698-4d89-abb0-4f6c71fdf5ff"}
 WARN  abort connection attempt
 WARN  abort transport connection
 ERROR  Livekit Connect Error: Error: Client initiated disconnect
"@livekit/react-native": "^1.4.1"
This is a log of disconnection when using the version.
I was using version 1.3.0 just fine and suddenly I'm having connection issues. I'm confused.
Is this a DNS issue with the server in Japan or a react-native client issue?
d
hmm interesting, does it eventually connect?
I think even in the event of connectivity issues, it should have a retry step. wondering if that's happening for you.. or did it give up after one attempt
f
Yes sometimes the connection seems weird. But it does connect. We're offering service a fast matching people and if it doesn't RTC connected each other within 15 seconds, we're looking at it as an unmatched. So if even 1 reconnection occurs, the match will fail.
d
Hey @few-midnight-94961, checking with our infra team, they did report one server in Japan having RTC issues around the time of your report. Just following up to see if this is still happening to you, or if it's been resolved
f
Thanks @dry-elephant-14928 We have modified our strategy to minimize the use of servers in the Japan region. For now, we have only applied livekit calls to people in India and Indonesia. We will test on servers in the Japan region again in the future. Thanks for letting us know, is there anywhere we can check the system status of each server?
d
That would be our job to ensure each server that is taking requests remains healthy. In this case, it was due to a misconfigured firewall on one of the servers (out of 15 SFUs). It would have caused an increase in failure rate. We've implemented additional steps to ensure this doesn't happen again in the future
f
Thank you.