Bash installer for Jibri on supported Ubuntu LTS based systems using nginx as default webserver.
As for our current latest release, as we have integrated more and more features, we highly recommend to use a purpose specific-newly spawn server to host the jitsi-meet framework, making sure you stick to the requirements and recommendations as much as possible, in order to avoid issues.
Your VM must have git and curl befor you start bashing.
sudo apt install git -y
sudo apt install curl -y
Login into your clean server, clone git repository and run the installer,
git clone https://github.com/andzejsp/quick-jibri-installer
cd quick-jibri-installer
sudo bash quick_jibri_installer.sh
Copy the modified add-jibri-node.sh file from your early cloned installation directory once the installation is completed, to the new server meant to be a jibri node using your preferred method, then run it
WARNING: This file contains sensitive information from your setup, please handle with care.
bash add-jibri-node.sh
To add Jibri node with Mattermost (bot/webhook post in finalize_recording.sh) and Nextcloud (upload recording to cloud) options use this:
bash add-jibri-node-mm-nextcloud-no-ssh.sh
Copy the modified add-jvb2-node.sh file from your early cloned installation directory once the installation is completed, to the new server meant to be a jibri node using your preferred method, then run it
WARNING: This file contains sensitive information from your setup, please handle with care.
bash add-jvb2-node.sh
Check more details on our wiki.
- Clean VM/VPS/Server using a supported Ubuntu LTS
- Valid domain with DNS record, mandatory for SSL certs via Let's Encrypt.
- Ports open for ACME (SSL) interaction & validation.
- Highly recommended: 8 GB RAM / 4 Cores.
- Webcam
- SIP account
- Google Cloud Account with Billing setup.
- Valid domain with DNS record for Nextcloud SSL.
For AWS users or any cloud service provider that might use their own kernel on their products (servers/vm/vps), might cause Jibri failure to start due not allowing snd_aloop module.
Make sure that you update your grub to boot the right one.
Feel free to use our test-jibri-env.sh tool to find some details on your current setup.
- Enabled Session Recording using Jibri
- Enabled Jitsi Electron app detection server side.
- Standalone SSL Certbot/LE implementation
- Jigasi Transcript - Speech to Text powered by Google API (stalled)
- JRA (Jibri Recordings Access) via Nextcloud
- Improved recurring updater
- Customized brandless mode
- Setting up custom interface_config.js (to be deprecated by upstream)
- Grafana Dashboard
- Lobby Rooms via
- Conference Duration via
- Automatic Jibri nodes network sync (see more).
- JVB2 nodes network.
- JWT auth.
- Rename Jibri folder with name room + date.
- Jibri Environment Tester
- Jibri Conf Upgrader (late 2020).
- Selenium Grid via Docker
- Optional default language
- Option to enable Secure Rooms
- Option to enable Welcome page
- Option to enable Close page
- Option to set domain as hostname on JMS
- Custom High Performance config
- Start with video muted by default
- Start with audio muted but moderator
- Set pre-join screen by default.
- Please check our wiki for further documentation.
Please note: This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY.
SwITNet Ltd © - 2021, https://switnet.net/