Heya, I’ve been trying to setup jitsi stack with jibri as well for both using docker-compose and my own kubernetes manifest. So the setup I was done is jitsi + jibri using docker-compose, and sometimes I turn off the jibri docker-compose and deploy jibri on top of kubernetes.
When I try to record using jibri on kubernetes, it records just fine. However when I played back the recording result turns out that jibri does not record anything, just showing grey page (no sound and no audio recorded).
I checked the logs on jibri for both docker-compose and kubernetes are the same. But when I check the jvb logs for both cases (jibri docker-compose vs jibri kubernetes), I realize that seems like the jvb does not recognize the jibri IP, hence maybe the only participant in that conference is only the user itself.
and if I exec into the container and run java -version then I get:
openjdk version “1.8.0_252”
OpenJDK Runtime Environment (build 1.8.0_252-8u252-b09-1~deb9u1-b09)
OpenJDK 64-Bit Server VM (build 25.252-b09, mixed mode)
@Kali here I attach the jibri logs jibrilogs.k8s.txt (18.2 KB)
I replaced my jitsi domain to my.domain, and eventually update the /etc/hosts file so that when I access meet.my.domain it will resolve to the VM that holds the jitsi stack private IP address
If the recording starts both as a core and as a ram, you’re fine.
Is Jibri a separate server from jitsi?
I had your problem because i had java 11.
Does Jibri solve jitsi’s fqdn?
From the log i see an IP 10.x.y.z. Why?
@Kali yes jibri been setup on the different server from other jitsi components, and they can talk using private IP (hence you see 10.xx.xx.xx there). I actually add to jibri container’s /etc/hosts file, so when I run nslookup meet.my.domain it will resolve to the jitsi public IP but when I run ping meet.my.domain it will ping to the jitsi’s private IP address. But if I try to resolve other subdomains from *.meet.my.domain it doesn’t resolve anything. I think jibri and jitsi will resolve it internally?
@Freddie I run the command on all containers (jibri on k8s, jibri on docker-compose, and jvb on docker-compose) and all of them giving me the same response:
There is only one alternative in link group java (providing /usr/bin/java): /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
Nothing to configure.
i can play the videos without any problems. And recordings work like live streaming works.
The problem you have, i had it when i installed java 11 by mistake.
I have removed java, jibri. Then i installed java 8 as the first package then everything else.
I had a few minor file permissions issues but they can be fixed in seconds.
When you run this command sudo apt-get install default-jre-headless ffmpeg curl alsa-utils icewm xdotool xserver-xorg-input-void xserver-xorg-video-dummy don’t install Java because it updates Java from 8 to 11.
So you just run sudo apt-get install ffmpeg curl alsa-utils icewm xdotool xserver-xorg-input-void xserver-xorg-video-dummy
My jibri is not in dmz but it is in lan. The video files is immediately available for my colleagues. The videos are not stored inside the jibri server but in a storage with read-only permissions.
any one fixed the no audio and video in jibri recording files,
it jitsi meet latest version only getting issue, old jitsi meet working fine same jibri.
I have changed trusted-domains = [ "recorder to recording still same issue.