Google Chrome Issue

[brunocalado]

Hii

I'm having a problem with Google Chrome for sometime. Some players just can't conect to livekit using Google Chrome. Changing to Edge solves the problem.

To try to solve the problem I:

• google chrome anonymous tab
• remove Google folder C:\Users\myuser\AppData\Local\Google
  This solved for some players, but not for others.

Is there some tip to help it work on chrome?

tks

[igorteuri]

I'm having the same problem here.

[bekriebel]

Hrmm... I just tested against my cluster with Chrome v111.0.5563.65 on Windows and it seems to be working fine. This seems like either a configuration issue, or a Chrome issue. Are these new installations that have never worked, were any updates done, or did this just start happening with no changes to your LiveKit install?

[brunocalado]

They worked for a time. Then, this started to happen with some of my players. I happened once with me, I deleted google data folder and solved.

[bekriebel]

Hrmm... this sounds like it may be either a chrome or LiveKit issue, then. It may be worth checking the Chrome bug tracker or check on LiveKit's support Slack to see if there is any known issue. I haven't had any reports of a similar issue against my Patreon cluster, so it may be version specific to LiveKit as well.

[mathsteck]

Yesterday I also had the exactly same issue with one of my players. Everyone using Chrome but one particular player couldn't join the A/V.

The server is hosted by myself and I am not using the LiveKit cloud. It might be related with the duck dns issue maybe?

[jaimemnds]

This is still an issue.

Does anyone know if this package is still being maintained? Has anyone found an alternative to it?

[brunocalado]

Use https://flc.ruleplaying.com/ helps. Em qua, 31 de mai de 2023 12:43, Jaime Mendes ***@***.***> escreveu:

…

This is still a issue. Does anyone know if this package is still being maintained? Has anyone found an alternative to it? — Reply to this email directly, view it on GitHub <#46 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGEUZ7GWUPFBL257546QBLXI5RJ5ANCNFSM6AAAAAAV4KPOOQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bekriebel]

It is still maintained, but I have yet to be able to reproduce the issue. It seems to be fixed by clearing data in google chrome or sometimes using an incognito mode tab. This makes me think it's something specific with browser configuration. If anyone has more details to add to help me reproduce, I can see if there's any workaround to be done.

[mathsteck]

I might have some logs that can be useful:

LivekitChromeError.log

[bekriebel]

This may not be everyone's issue, but for this log in particular it is almost certainly the use of duckdns combined with ad blockers. For some reason, ad blockers seem to block all webrtc connections to duckdns domains. I have a warning about that on the README: https://github.com/bekriebel/fvtt-module-avclient-livekit#running-your-own-livekit-server

I might have some logs that can be useful:

LivekitChromeError.log

[theripper93]

Something seems to have changed recently with adblockers , chrome, duckdins or a mix of them - disabling adblockers on the page fixed it for me. This problem started apparently randomly, never had duckdns issues before 2\3 days ago

[bekriebel]

Something seems to have changed recently with adblockers , chrome, duckdins or a mix of them - disabling adblockers on the page fixed it for me. This problem started apparently randomly, never had duckdns issues before 2\3 days ago

It may be intermittent based on whatever rules are in place with the blockers at any given time, but it's been a recurring problem for some time.