Problems with Jitsi app on mobile and config.js: it seems to be solved

Hello !

My YunoHost server

Hardware: VPS bought online
YunoHost version: 11.2.5 (stable)
I have access to my server : Through SSH

Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

  1. I installed the Jitsi instance;
  2. Created a room with my login and password;
  3. Entered the room via browser with another desktop device;
  4. Entered the room via browser with a mobile device;
  5. Tried to enter the room with Jitsi Android and iOs app with no success.

Android logs:

10-20 18:51:49.113   704   752 E JitsiMeetSDK: [features/base/lib-jitsi-meet] Failed to load config from Error(Error){"message":"ReferenceError: identifier 'enableJaaS' undefined","code":"EUNSPECIFIED","stack":"\\ngeneratorResume@[native code]\\\\\\\\\\\\\nvalue@[native code]\nvalue@[native code]"}

6. Opened the config.js file
7. Changed the bottom lines as follows:

var enableJaaS = false;
if (enableJaaS) {
config.dialInNumbersUrl = ‘’;
config.dialInConfCodeUrl = ‘’;
config.roomPasswordNumberOfDigits = 10; // skip re-adding it (do not remove comment)

so I simply added:
**var enableJaaS = false;**

8. Now I can enter the created room as a guest also using the Android Jitsi App. Have not yet tried with iOs.

The problem seems to be solved.

9. What I've noticed:

comparing the YH configuration file with a standard one it seems to be incomplete, infact 

var enableJaaS = false;

is not present at all.


Kind regards

1 Like

Hi Mario,

Welcome to the forums!

Thank you for taking the trouble to create an account to share your tip, just yesterday I saw a post by @Luncheon3462 , describing just the kind of problem you solved. Perhaps you might take the trouble to hand them your suggestion?

It was not clear to me directly whether it was missing in the Jitsi version or in the YNH version, and had a look at the config.js you linked. It is there at line 25, so you must mean it is not in the YNH version.

Some speculation, without having any facts at hand:

  • The freely available Jitsi web client at is behind a login since a couple of weeks (months?).
  • I guess it has to do with cash flow, and the cost of running the infrastructure of such a platform.
  • Maybe “Jaas” means “Jitsi as a service”; when self-hosting, the hosted Jitsi is not needed.
  • Before, when everyone could just use their servers, it would not have mattered how the connection was established
  • Now that the hosted platform is behind a login, they need a new parameter to tell whether to use the hosted platform
  • The new parameter is not yet included in the YNH config

Anyway, so far for letting my fantasy run :smiley:

Thanks again!

Hi wkk, thanks for you replay !

the post you saw the day before yesterday is related to Jitsi integration in Nextcloud. A speculation about JaaS may be probably useful but don’t know how.

Blockquote What I’ve noticed:
comparing the YH configuration file with a standard one it seems to be incomplete, infact
var enableJaaS = false;
is not present at all.

I meant the YH Jitsi configuration is missing some elements of the Jitsi standard configuration. Infact I added the line
var enableJaaS = false;
to my YH Jitsi configuration.


1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.