Jibri recording

[uberiain]

Hello, I have one local jitsi + jibri installation that is working well. When I record one meeting I obtain the recording with a message on it :

“El nombre de la reunión no debe de contener ninguno de estos caracteres: ?,&,:,’,”,%,#." but the meeting name is video.

Where is the problem?

Regards.

[saghul]

That's odd. What meeting name are you using?

[uberiain]

Te Meeting mame is: Video

[saghul]

That's odd, there is nothing special to that name. What versions of the software are you running? (Jitsi Meet and Jibri)

[uberiain]

My versions are:

OS : Linux jitsi 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18) x86_64 GNU/Linux debian version: 10.10

jitsi-meet 2.0.6345-1 all WebRTC JavaScript video conferences jitsi-meet-prosody 1.0.5349-1 all Prosody configuration for Jitsi Meet jitsi-meet-turnserver 1.0.5349-1 all Configures coturn to be used with Jitsi Meet jitsi-meet-web 1.0.5349-1 all WebRTC JavaScript video conferences jitsi-meet-web-config 1.0.5349-1 all Configuration for web serving of Jitsi Meet jitsi-videobridge2 2.1-557-gba6a8492-1 all WebRTC compatible Selective Forwarding Unit (SFU) prosody 0.11.2-1+deb10u2 amd64 Lightweight Jabber/XMPP server prosody-modules 0.0~hg20190203.b54e98d5c4a1+dfsg-1+deb10u1 all Selection of community modules for Prosody jibri 8.0-104-g9871ba1-1 all Jibri

[gpatel-fr]

I have no idea if this is relevant to your problem, but should you not use a matched version for Chromedriver and Chrome ? you are using 93 and 94 respectively.

[uberiain]

I have updated chromedriver, but the problem persist

[gpatel-fr]

well, so much for this obvious idea then. Usually when people have weird and illogical problem nobody else has, it's either a hardware problem or that they are doing something no one else does (or very few people). You are running jitsi-meet and jibri on the same (logical) computer and it's something very few people do because i'ts not officially recommended. Do you have at least enough resources (RAM and CPU allocated to your VM) for that ? I'd say that 4GB should definitely be a problem, and 12 Gb should be good for small meetings. Edit: as an afterthought, are you running on a widely used and supported (up-to-date) hypervisor such as KVM or Hyper-v or vmware ?

[saghul]

It looks as if some accessibility feature is turned on in Chrome, since that text is not to be visible in the input field. Not to mention that's on the welcome page and Jibri should be in the meeting...

[uberiain]

Hi, I think that I found the problem:

With latest chrome version for debian, the message appears. I have downloaded google chrome to 86.0.4240.75 and chromedriver to LATEST_RELEASE_86.0.4240 and the message disapear.

So I think that the problem is with chrome.

[gpatel-fr]

I don't use currently Chrome 94 on my workstation - Snap Ubuntu is not immediately updated to current Chrome stable (I was thinking it was but I was mistaken). I tried to open a meeting on another computer with Chrome 93 and join it on my computer with Chrome 94 and I don't see anything strange on the meeting screen so it's not Chrome by itself. I don't have time to try to reproduce it with Jibri.

[uberiain]

I test with this versions, and the result:

google-chrome-stable 90.0.4430.72-1 Works google-chrome-stable 91.0.4472.164-1 Works google-chrome-stable 93.0.4577.82-1 Don't work

[saghul]

I don't use currently Chrome 94 on my workstation - Snap Ubuntu is not immediately updated to current Chrome stable (I was thinking it was but I was mistaken). I tried to open a meeting on another computer with Chrome 93 and join it on my computer with Chrome 94 and I don't see anything strange on the meeting screen so it's not Chrome by itself. I don't have time to try to reproduce it with Jibri.

Note that Jibri uses kisko mode and the remote protocol, amongst other things, so it may exhibit different behavior than a desktop run.

[gpatel-fr]

@uberiain interesting. In a way I was right on thinking it could come from something unusual you did, but I did not think that you were using a very recent Chrome/chromedriver version and it's probably not that typical since many heavy Jibri users are pinning their chrome version to avoid bad surprises, so it's not sure many are even at 93.

@saghul yes I'm aware that chromedriver means something, that's why I was saying Chrome by itself is not the culprit BTW if it's not an operational secret, what's the current version of chromedriver/Chrome used by meet.jit.si ?

[saghul]

BTW if it's not an operational secret, what's the current version of chromedriver/Chrome used by meet.jit.si ?

Not a secret, but TBH I don't know that myself. @damencho ?

[damencho]

Chrome 93 and corresponding driver.

[gpatel-fr]

then it's very weird that it failed for the OP @uberiain are you 100% sure that when you did your test with 93 the chrome and chromedriver version were matched? IIRC it's in the logs but not at the same place.

[uberiain]

This is my test with chrome 93 and driver 93 browser.0.txt

With this packages:

ii jitsi-meet 2.0.6416-1 all WebRTC JavaScript video conferences ii jitsi-meet-prosody 1.0.5403-1 all Prosody configuration for Jitsi Meet ii jitsi-meet-turnserver 1.0.5403-1 all Configures coturn to be used with Jitsi Meet ii jitsi-meet-web 1.0.5403-1 all WebRTC JavaScript video conferences ii jitsi-meet-web-config 1.0.5403-1 all Configuration for web serving of Jitsi Meet ii jitsi-videobridge2 2.1-568-g9cbc8644-1 all WebRTC compatible Selective Forwarding Unit (SFU) ii jibri 8.0-104-g9871ba1-1 all Jibri ii prosody 0.11.2-1+deb10u2 amd64 Lightweight Jabber/XMPP server ii prosody-modules 0.0~hg20190203.b54e98d5c4a1+dfsg-1+deb10u1 all Selection of community modules for Prosody

With chrome 91 it's working

[gpatel-fr]

I have setup a test system this we with Jitsi-meet and Jibri installed together, Chrome 94; and I definitely don't see he problem. I had no great expectation to see it anyway since there is on the forum at least one regular with this setup, he would have complained already. I wanted to see how it was possible to connect to the Jibri session using vnc and it's easy. Can you try it and take a look at what is displayed when the problem happens ?

sudo apt install tigervnc-scraping-server configuration : connect as jibri, mkdir -p ~/.vnc, launch vncpasswd, enter a password. then edit ~/.icewm/startup with something like

!#/bin/sh x0vncserver -passwordfile /home/jibri/.vnc/passwd -display :0 >/dev/null 2>&1 &

restart the services, you should see 5900 with sudo ss -tapnu | grep 5900 then connect from outside the VM with a vnc viewer. Enter the password and you should see the start screen of icewm.

[uberiain]

Hi, @gpatel-fr . I don't have any graphics system on my jitsi/jibri system. I install the Chrome chromium package that comes with debían, and Jibri is working por me.

Regards

[gpatel-fr]

@uberiain It does not matter that you don't have graphics; you can still connect to the headless X server with Vnc and display it (on a workstation of course). When you say that 'jibri is working', does that mean that you have found a solution to your problem ? If yes you should close the issues you opened.

[uberiain]

Yes, my solution is install chromium that come with debian 10. So I close this. Thanks por all