Docker-jitsi-meet: SpeakerStats don't work anymore

[JacBra]

I installed stable-5076 (from scratch). The speaker stats aren't working anymore.
Before I used stable-4857. I did a compare but couldn't find any difference that would relate to the speaker stats.
Has anyone else seen this same behaviour?

Moreover, conference duration only works when authentication is disabled (ENABLE_AUTH=0 in .env).
I'm not sure whether this is since stable-5076, or that this happened before.

[sysadmama]

I tried to work with stable-5076, but I ran into so many problems that I just switched back to stable-4857.
Indeed, non-working speakerstats was one of my problems. So I can confirm what @JacBra wrote few hours ago.

[saghul]

Thanks for the report, we'll take a look!

[saghul]

@sysadmama Did you have any authentication configured?

[sysadmama]

@sysadmama Did you have any authentication configured?

Indeed @saghul ENABLE_AUTH=1 with AUTH_TYPE=internal is set.

[MarkusPaul1989]

After updating yesterday, I got the same issue.
The speaker stats are displayed, but the time counter always show zero seconds for all participants.
Is there any a solution or a work-around yet?

[JacBra]

With stable-5142 the speaker stats work again. Thanks!

The conference duration does still not work.
I saw this documentation: https://jitsi.github.io/handbook/docs/devops-guide/speakerstats but it's not clear to me in which config file I should put this. Can someone help?

[MarkusPaul1989]

Hi @JacBra,
this might be a prosody configuration located in the jitsi-meet.cfg.lua file

[juradoz]

Confirmed speakerstats not working on vanilla docker instalation, pulled from stable-5142.

[juradoz]

Problem gets solved if ~/.jitsi-meet-cfg/web/config.js gets edited AFTER web container is started. Last occurrence of config.openBridgeChannel must be set to true:

config.openBridgeChannel = true;

Parameter gets reset to 'websocket' on every 'web' container restart or creation.

[juradoz]

On top of not overriding ~/.jitsi-meet-cfg/web/config.js file (since it is monted on a volume so custom parameters can get persisted out of transient containers), web/rootfs/defaults/settings-config.js should somehow allow setting true (no quotes) to config.js.

[JacBra]

Hi @JacBra,
this might be a prosody configuration located in the jitsi-meet.cfg.lua file

https://github.com/jitsi/docker-jitsi-meet/commit/bec928c3aa6c512fde98ad3d746963107c8f8e3c#diff-199f45103a3a23a514583143479a6ce9a61672842b115a183202503dbf315459

I think that this pull request has something to do with it, but I can't exactly know how the syntax of these .lua files/templates work. Can someone point me to a direction for that? Thanks a lot.

[debfx]

Removing the configs in web/nginx/ and restarting the container fixed the issue for me.

The websocket requires changes in nginx's meet.conf. They were done in web/rootfs/defaults/meet.conf but web/rootfs/etc/cont-init.d/10-config doesn't touch the config inside the container if already exists. As a result jvb websockets are broken on upgrade.

[JacBra]

I found that the conference duration works fine when authentication is disabled. When (LDAP) authentication is enabled, it doesn't work anymore.

[prayagsingh]

Removing the configs in web/nginx/ and restarting the container fixed the issue for me.

The websocket requires changes in nginx's meet.conf. They were done in web/rootfs/defaults/meet.conf but web/rootfs/etc/cont-init.d/10-config doesn't touch the config inside the container if already exists. As a result jvb websockets are broken on upgrade.

Can you please share which config did you remove?

[prayagsingh]

@saghul I'm using master branch and still speaker-stats aren't coming up. Also, I'm getting Failed to send E2E ping request or response. undefined warning in console continuously. Getting both errors when using websocket.
AUTH_TYPE=jwt

[mfts]

I'm seeing the same thing as @prayagsingh

[debfx]

Can you please share which config did you remove?

All *.conf files inside the web/nginx/ config subdirectory (as set in the CONFIG variable in .env).

[prayagsingh]

Update
I have created jicofo/jvb unstable image and I'm not seeing Speaker stats and E2E errors any more. So,I think this issue will be fixed in next release.
@saghul @mfts

[netcom]

Issue is in config variable in config.js, config variable config.openBridgeChannel has quotes in its value, but it should be set to boolean value.

How to check if this affects you?

Open in browser: https://yourjitsideployment.com/config.js
Check if config.openBridgeChannel = 'true'; // (this has quotes but it should be boolean)

[F-Node-Karlsruhe]

Issue is in config variable in config.js, config variable config.openBridgeChannel has quotes in its value, but it should be set to boolean value.

How to check if this affects you?

Open in browser: https://yourjitsideployment.com/config.js
Check if config.openBridgeChannel = 'true'; // (this has quotes but it should be boolean)

The issue still persists in the latest version :/

[saghul]

The default is "websocket", did you override the value?

[F-Node-Karlsruhe]

Yes, went into the container, changed the value and restarted it. Checked on domain/config.js