luvolondon/fvtt-module-jitsiwebrtc

Public Jitsi Meet servers no longer work for the module

ChamoFx opened this issue · 6 comments

ChamoFx commented

Hi ! the Jitsi client was working perfectly fine until a couple of foundry updates now i version 9.255 if i have the module activated the video and audio of any user just dissapear.
Actually after the update if i had the module activate i couldnt even select the input for the camera or the audio .

Foundry version: v9 build 255
OS: windows 10, 21H2
Native application
Game system : call of Cthulhu 7th Edition ( unofficial) 0.7.6
Modules:
Jitsi WebRTC client 0.6.5
libCaptions 0.1.4
let me know if you guys need something else , thanks!

simulacrum-1 commented

Getting the same problem

Abourass commented

Same issue here, happy to provide logs or help debug if needed.

cleciojunior2 commented

Here too, show this in the console:
image

bekriebel commented

It appears that Jitsi has begun blocking external use of their beta.meet.jit.si and meet.jit.si servers. Unfortunately, there's nothing I can do to resolve this. There are three options:

  1. Switch to the newer and still updated LiveKit AVClient module. LiveKit also doesn't provide public servers, but running your own LiveKit server is easier than running Jitsi and in my experience works much better. I also provide a LiveKit server cluster for Patreon supporters (to cover my costs of running the servers).
  2. Try to use one of the other community servers listed in the link that is included in this ticket: #96. I still need to update documentation to include this link.
  3. Run your own hosted Jitsi server. This is what I used to do, but I continued to have issues using Jitsi, so I have stopped recommending it and won't be making further updates to this module.

Thanks for reporting. I'll leave the ticket open until I get a chance to update documentation and removed the old public server from the module code.

  • 👍1
Abourass commented

@bekriebel - Unfortunately, this issue persist even when I was hosting the Jitsi instance myself, so your third suggestion is moot.

As you no longer support this module, might I suggest making the repo archive only, with the same explanation you've given here, and a link to your LiveKit AVClient module. I had already switched to your LiveKit module shortly after posting this, but as someone new to Foundry, going through the process of setting up Jitsi (a big pain) only to find it's essentially not the best solution was frustrating. A quick message at the top of this repo would do a lot to head that off.

Thanks for your work, appreciate the solutions you've built.

bekriebel commented

@bekriebel - Unfortunately, this issue persist even when I was hosting the Jitsi instance myself, so your third suggestion is moot.

I was able to test this with a different server that doesn't have the CORS restrictions in place and it continued to work. It should be possible to configure a self-hosted server to accept external connections with the proper CORS policy. This has actually always been a thing that needed to be adjusted in the configuration, but in the past the public Jitsi server accepted connections as well.

As you no longer support this module, might I suggest making the repo archive only, with the same explanation you've given here, and a link to your LiveKit AVClient module.

I do have a warning that was added when the public server started limiting meetings to 5 users that already redirects folks to LiveKit. I suppose I should put it up at the top of the description and mark the module as deprecated and available for another developer to take over maintenance if they'd like.

  • 👍1