After 30 seconds JitsiRTC is dropping my cam and voice connection

[nirurin]

Every 30 seconds Jitsi dumps me from the server entirely (my webcam portrait vanishes and I lose voice ability, even while in the middle of talking). I can still hear other people though. I need to refresh the page to get it back.

Any thoughts on why it might be happening?

Error says 'no participant' but I'm connected, the webcam is transmitting (I can see myself) and I'm talking (the players can hear me). It just then drops me mid-sentance after 20-30 seconds

[bekriebel]

My first guess would be that something is dropping the webrtc connection. Perhaps a firewall/vpn on your network or something with your ISP is blocking session after it is detected. The best I could suggest is to attempt to test using https://beta.meet.jit.si/ directly to see if it is related to Jitsi itself, or the module.

However, I'm no longer putting active debugging time into Jitsi as there have been too many connections issues in my experience. My recommendation would be to switch to LiveKit for better connectivity. However, if it is something like your ISP blocking the WebRTC connection, you may have the same problem there as well.

[nirurin]

Yeh the problem with live is I would need to set up a docker service to run it, which I don't really have time for. I'll look into it. Thanks

On Tue, 11 Jan 2022, 18:54 Brint E. Kriebel, @.***> wrote:

My first guess would be that something is dropping the webrtc connection. Perhaps a firewall/vpn on your network or something with your ISP is blocking session after it is detected. The best I could suggest is to attempt to test using https://beta.meet.jit.si/ directly to see if it is related to Jitsi itself, or the module.

However, I'm no longer putting active debugging time into Jitsi as there have been too many connections issues in my experience. My recommendation would be to switch to LiveKit for better connectivity. However, if it is something like your ISP blocking the WebRTC connection, you may have the same problem there as well.

— Reply to this email directly, view it on GitHub https://github.com/luvolondon/fvtt-module-jitsiwebrtc/issues/94#issuecomment-1010264327, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4T22OL66T5GHRUUUOB74DUVR4H3ANCNFSM5LWZTF2Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[DAMO238]

I can confirm that I have been having this issue on both Brave and FireFox on two different networks using the default public beta jitsi, however it does not seem to affect anyone else connected and only sometimes kicks me off. Interestingly, I can still see and hear the other participants even though they cannot see or hear me.

[nirurin]

Unfortunately it seems this project is no longer supported, in favour of a new one that they can monetise.

I've resorted to using the default webcam setup, which does work fine it's just less efficient with bandwidth. It'll have to do.

On Sat, 12 Feb 2022, 17:23 DAMO238, @.***> wrote:

I can confirm that I have been having this issue on both Brave and FireFox on two different networks using the default public beta jitsi, however it does not seem to affect anyone else connected and only sometimes kicks me off. Interestingly, I can still see and hear the other participants even though they cannot see or hear me.

— Reply to this email directly, view it on GitHub https://github.com/luvolondon/fvtt-module-jitsiwebrtc/issues/94#issuecomment-1037328024, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4T22PX23BJRTWA4V6YELTU22JRRANCNFSM5LWZTF2Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[bekriebel]

Unfortunately it seems this project is no longer supported, in favour of a new one that they can monetise.

For what it's worth, I didn't drop support for Jitsi so I could monitise LiveKit. I've stopped developing on this module because of issues like this one that were constantly popping up and I never could find ways to keep the platform stable. LiveKit has proven to be a much better system to develop against.

I do offer a paid option for LiveKit because there is no free server option. Running these services costs money, and I need to cover my expenses for it. It's an alternative for those who don't want to manage their own servers. I promise it isn't coming near paying for the time and effort put into these modules 🙂

Regarding this ticket, I wish I had answers. It's possible that more could be done in the module to solidify the connections, but I don't have the time (or, honestly, desire) to continue trying to make Jitsi work well when LiveKit has been working better for me and my parties.

I'll leave the ticket open in case anyone else decides to take up maintenance of the project, though.

[nirurin]

After looking at your live kit more closely I do notice you're charging just to cover costs, so I'm sorry I implied you were just monetising. I may see if I can get my party to donate and see what happens. Until then I'll just use the default cams. Thanks for responding.

On Sun, 13 Feb 2022, 02:23 Brint E. Kriebel, @.***> wrote:

Unfortunately it seems this project is no longer supported, in favour of a new one that they can monetise.

For what it's worth, I didn't drop support for Jitsi so I could monitise LiveKit. I've stopped developing on this module because of issues like this one that were constantly popping up and I never could find ways to keep the platform stable. LiveKit has proven to be a much better system to develop against.

I do offer a paid option for LiveKit because there is no free server option. Running these services costs money, and I need to cover my expenses for it. It's an alternative for those who don't want to manage their own servers. I promise it isn't coming near paying for the time and effort put into these modules 🙂

Regarding this ticket, I wish I had answers. It's possible that more could be done in the module to solidify the connections, but I don't have the time (or, honestly, desire) to continue trying to make Jitsi work well when LiveKit has been working better for me and my parties.

I'll leave the ticket open in case anyone else decides to take up maintenance of the project, though.

— Reply to this email directly, view it on GitHub https://github.com/luvolondon/fvtt-module-jitsiwebrtc/issues/94#issuecomment-1037683265, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4T22NNPM2YQZ2TV6FYUXDU24I25ANCNFSM5LWZTF2Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>