• 6 Posts
  • 126 Comments
Joined 1 year ago
cake
Cake day: June 26th, 2023

help-circle


















  • Ah I had that popup confused with one of our own; Now that I checked the text on google translate I figured out what’s happening.

    The meet.jit.si domain is a public jitsi instance that is kept by jitsi themselves. They recently implemented this login requirement on that domain (one user in every meeting must authenticate); They probably assumed that those meetings would always be in a browser and our desktop app is not handling that authentication flow properly. I’ll register a task for someone from our app’s team to take a look.

    If you host your own jitsi instance, this login requirement won’t be there and you won’t have this specific issue (though I assume you probably won’t stay with Rocket.Chat anyway due to the E2EE requirement).