jitsi/jibri — 672★ on GitHub (Kotlin). Jitsi BRoadcasting Infrastructure
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Jibri provides services for recording or streaming a Jitsi Meet conference.
It works by launching a Chrome instance rendered in a virtual framebuffer and
capturing and encoding the output with ffmpeg. It is intended to be run on a
separate machine (or a VM), with no other applications using the display or
audio devices. Only one recording at a time is supported on a single jibri.
NOTE: Jibri currently only works with a full-fledged Jitsi Meet
installation. Using a different frontend won't work.
Installing Jibri
Installation notes
Jibri was built on Ubuntu 18.04 (Bionic), and has been tested with the
pre-built kernel and extra kernel modules (linux-image-extra-virtual
package). Any other distribution or kernel configuration MAY work but has not
been tested.
Pre-requisites
ALSA and Loopback Device
First make sure the ALSA loopback module is available. The extra modules
(including ALSA loopback) can be installed on Ubuntu 16.04 using package name
linux-image-extra-virtual
Perform the following tasks as the root user
Set up the module to be loaded on boot: echo "snd_aloop" >> /etc/modules
Load the module into the running kernel: modprobe snd_aloop
Check to see that the module is already loaded: lsmod | grep snd_aloop
If the output shows the snd-aloop module loaded, then the ALSA loopback
configuration step is complete.
Ffmpeg with X11 capture support
Jibri requires a relatively modern ffmpeg install with x11 capture compiled
in. This comes by default in Ubuntu 16.04, by installing the ffmpeg package.
If building Jibri for Ubuntu 14.04 (trusty), the mc3man repo provides
packages. They can be used by the following in Ubuntu 14.04:
The latest Google Chrome stable build should be used. It may be able to be
installed direclty via apt, but the manual instructions for installing it are as
follows:
Jibri is currently meant to be run as a regular system user. This example
creatively uses username 'jibri' and group name 'jibri', but any user will do.
This has not been tested with the root user.
Ensure that the jibri user is in the correct groups to make full access of the
audio and video devices. The example jibri account in Ubuntu 16.04 are:
"adm","audio","video","plugdev".
sudo usermod -aG adm,audio,video,plugdev jibri
Config files
Edit the jibri.conf file (installed to /etc/jitsi/jibri/jibri.conf by
default) appropriately. You can look at
reference.conf for the default values and
an example of how to set up jibri.conf. Only override the values you want to
change from their defaults in jibri.conf.
By default, Jibri logs to /var/log/jitsi/jibri. If you don't install via the
debian package, you'll need to make sure this directory exists (or change the
location to which Jibri logs by editing the log config
Configuring a Jitsi Meet environment for Jibri
Jibri requires some settings to be enabled within a Jitsi Meet configuration.
These changes include virtualhosts and accounts in Prosody, settings for the
jitsi meet web (within config.js) as well as jicofo.conf.
Prosody
Create the internal MUC component entry. This is required so that the jibri
clients can be discovered by Jicofo in a MUC that's not externally accessible by
jitsi meet users. Add the following in /etc/prosody/prosody.cfg.lua:
-- internal muc component, meant to enable pools of jibri and jigasi clients
Component "internal.auth.yourdomain.com" "muc"
modules_enabled = {
"ping";
}
-- storage should be "none" for prosody 0.10 and "memory" for prosody 0.11
storage = "memory"
muc_room_cache_size = 1000
Create the recorder virtual host entry, to hold the user account for the jibri
chrome session. This is used to restrict only authenticated jibri chrome
sessions to be hidden participants in the conference being recordered. Add the
following in /etc/prosody/prosody.cfg.lua:
The first account is the one Jibri will use to log into the control MUC (where
Jibri will send its status and await commands). The second account is the one
Jibri will use as a client in selenium when it joins the call so that it can be
treated in a special way by the Jitsi Meet web UI.
Jicofo
Edit /etc/jitsi/jicofo/jicofo.conf, set the appropriate MUC to look for the
Jibri Controllers. This should be the same MUC as is referenced in jibri's
jibri.conf file. Restart Jicofo after setting this property. It's also
suggested to set the pending-timeout to 90 seconds, to allow the Jibri some time
to start up before being marked as failed.
Once recording is enabled in yourdomain-config.js, the recording button will
become available in the user interface. However, until a valid jibri is seen by
Jicofo, the mesage "Recording currently unavailable" will be displayed when it
is pressed. Once a jibri connects successfully, the user will instead be
prompted to enter a stream key.
Note: Make sure to update Jibri's jibri.conf appropriately to match any
config done above.
Start Jibri
Once you have configured jibri.conf, start the jibri service:
The most recent commit recorded on jitsi/jibri was 23 days ago, based on the GitHub push timestamp. The repository has 326 forks — one of the better signals of community interest.
How many stars does jitsi/jibri have?
jitsi/jibri has 672 GitHub stars — refresh the page for the live number, or check github.com/jitsi/jibri. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is jitsi/jibri open source?
Yes — jitsi/jibri ships under the Apache-2.0 license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/jitsi/jibri.
What is jitsi/jibri?
jitsi/jibri (jitsi/jibri) is a Kotlin project on GitHub. From the project's own README: Jitsi BRoadcasting Infrastructure
Where do I read more about jitsi/jibri?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/jitsi/jibri is the definitive source.
Read full README in the tab above.
Is jibri worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of jibri.