Android App "You have been disconnected"

orko · January 31, 2023, 5:04pm

Hi,

I’ve noticed that the Android app doesn’t work with my selfhosted Jitsi server.
If I try to start a meeting or join an existing one, I just receive the message, that I’ve been disconnected.
If I try the same in a browser on the same device, it’s working fine.

I installed the server with the base installer scripts by @emrah
I’ve already changed the nginx configuration to use the fullchain.pem file instead of the crt file as described in the FAQ. But this didn’t had any effect.
Also I can’t find any errors in all of the existing logfiles.
Does anyone has any idea what else could cause this issue?

emrah · January 31, 2023, 5:44pm

When did you install?

A new jitsi-meet is released today. The previous version has a known bug. If the following line doesn’t exist in your config.js, add it

github.com

jitsi/jitsi-meet/blob/master/config.js#L1550


      
              // whiteboard: {
              //     // Whether the feature is enabled or not.
              //     enabled: true,
              //     // The server used to support whiteboard collaboration.
              //     // https://github.com/jitsi/excalidraw-backend
              //     collabServerBaseUrl: 'https://excalidraw-backend.example.com',
              // },
          };
          
          
// Temporary backwards compatibility with old mobile clients.
          config.flags = config.flags || {};
          config.flags.sourceNameSignaling = true;
          config.flags.sendMultipleVideoStreams = true;
          config.flags.receiveMultipleVideoStreams = true;
          
          
// Set the default values for JaaS customers
          if (enableJaaS) {
              config.dialInNumbersUrl = 'https://conference-mapper.jitsi.net/v1/access/dids';
              config.dialInConfCodeUrl = 'https://conference-mapper.jitsi.net/v1/access';
              config.roomPasswordNumberOfDigits = 10; // skip re-adding it (do not remove comment)
          }

orko · February 1, 2023, 10:29am

Thank you so much.
Adding this line fixed the issue!