Jibri | Bots!

This post is heavily inspired from this community post by https://community.jitsi.org/u/Woodworker_Life. However, the original installation document is based on typical split Jitsi on one VM and Jibri on seperate VM.

A little reworked version is deployed and tested for several client based with no performance issue- this post covers a single VM with Jitsi Videobridge and Jibri Reocording system.

Prerequisites:

Works only on Ubuntu 16 Distribution
Only following DNS entries are needed to be available:
- meet.ensii.net -> 123.45.67.89
- recording.ensii.net-> 123.45.67.89
- recorder.ensii.net-> 123.45.67.89
update /etc/hosts file as following:
- 127.0.0.1 meet.ensii.net
  123.45.67.89 recording.ensii.net
  123.45.67.89 recorder.ensii.net

Part-1: Setup Jitsi Meet on the server

You will need to login to the server you created in step 1. For this, on my Windows laptop, I use PuTTy. Login with initial password and change it to your own.

Update server:

apt update && apt upgrade -y

Use case with Jibri Recorded content to push to cloud storage operators.

Rclone installation (Debian 10)

All below commands are executed as ‘root’. (I know!..)

apt update
apt install curl -y
curl https://rclone.org/install.sh | bash

Rclone is now installed. We need to find where rclone expects it’s config file:

rclone config file

Response:

Configuration file doesn’t exist, but rclone will use this path:
/root/.config/rclone/rclone.conf

So we need to upload the file from our windows pc/laptop (C:\Users\[user]\.config\rclone\rclone.conf) to the location on the Jibri server (/root/.config/rclone/rclone.conf). (I used WinSCP for this). After upload, we check once more to be sure rclone finds it’s config:

Installing Jitsi and Jibri on Same Machine

Install RClone for synching Server contents to Cloud storage- google drive, onedrive, dropbox or own/nextcloud