You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our application that uses the livekit go server-sdk is spitting out a tsunami of Fail to refresh permissions: all retransmissions failed for error messages. At some point hundreds of these messages per hour. Note that this application is handling multiple multiple livekit rooms at the same time, each with 1-5 video streams & 2 audio streams.
The error seems to originate from the pion turn project, which is used by Pion Webrtc. From what I read in the the code of pion turn, it seems this error happens when the turn server does not respond to the turn createpermission request. Since were not seeing any failed to refresh allocation messages, my guess is that somehow the TURN connection is still alive? It's weird.
I cannot see anything weird in the actual video streams. But I'm worried that these errors are a sign of a leftover connection or something that's not cleaned up properly.
The text was updated successfully, but these errors were encountered:
We are still seeing about 19k of these errors every day.
Could anyone maybe point me into the direction of where to start debugging? I'm happy to add extra logs or do some experimentation. But I have no idea where to even start looking. Guidance would be much appreciated.
Our application that uses the livekit go server-sdk is spitting out a tsunami of
Fail to refresh permissions: all retransmissions failed for
error messages. At some point hundreds of these messages per hour. Note that this application is handling multiple multiple livekit rooms at the same time, each with 1-5 video streams & 2 audio streams.The error seems to originate from the pion turn project, which is used by Pion Webrtc. From what I read in the the code of pion turn, it seems this error happens when the turn server does not respond to the turn createpermission request. Since were not seeing any failed to refresh allocation messages, my guess is that somehow the TURN connection is still alive? It's weird.
I cannot see anything weird in the actual video streams. But I'm worried that these errors are a sign of a leftover connection or something that's not cleaned up properly.
The text was updated successfully, but these errors were encountered: