Here are my notes on how I got jitsi working on Ubuntu 18.04. I’ve it to work “back in the day” but I really wanted my tutorial re-written up.


I spun up a VM with 32 Gigs of RAM and 8 vCPUs, and pointed the extrenal IP to On the machine I ran:

apt update
apt upgrade
apt install apt-transport-https
apt-add-repository universe
apt update

Install jitsi meet

First thing I did was set the hostname with hostnamectl:

hostnamectl set-hostname

Next I added the jitsi package repo:

curl | sudo sh -c 'gpg --dearmor > /usr/share/keyrings/jitsi-keyring.gpg'
echo 'deb [signed-by=/usr/share/keyrings/jitsi-keyring.gpg] stable/' | sudo tee /etc/apt/sources.list.d/jitsi-stable.list > /dev/null
apt update

Then I configured the firewall:

ufw allow 80/tcp
ufw allow 443/tcp
ufw allow 4443/tcp
ufw allow 10000/udp
ufw allow 22/tcp
ufw enable

Then a sanity check:

ufw status verbose

Now install the debian package:

apt install jitsi-meet

Note: You want to select Self-Signed initially so you can do Let’s Encrypt later. If you have security rules on your cloud, you’ll need to open up thees ports too:

22, 80, 443, 4443, 10000

Next attempt to run the cert creation script:


If it errors you may have to install this package then run again:

apt install libc6

Now you should be able to go to your domain: and see a working jitsi link.



Install etherpad with the following:

curl -sL | sudo -E bash -
apt install -y nodejs
git clone --branch master

Next open up the port for etherpad to listen on:

ufw allow 9001/tcp

Be sure to add it to your cloud security group too. Next open up the /etc/nginx/sites-available/<hostname>.conf file and add this under xmpp websockets stanza.

   # Etherpad-lite
    location ^~ /etherpad/ {
        proxy_pass http://localhost:9001/;
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_buffering off;
        proxy_set_header       Host $host;

Next open up /etc/jitsi/meet/<hostname>-config.js and add the following after:

    // List of undocumented settings used in jitsi-meet
      etherpad_base: 'https://<hostname>/etherpad/p/',

Now to test it out, you need to run the following. (only have --root if you are running as root:

cd etherpad-lite && bin/ --root

You should now have the “Open Shared Document” option on the meeting!

Streaming to YouTube (I still haven’t gotten this section to work)

jibri setup

The the streaming software is called: jibri.

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.

Being it assumes you have a seperate machine for jibri, i spun up another machine without an external IP to run this software. jibri was built with 16.04, so I spun one up.

First commands I ran:

apt update
apt upgrade
apt install linux-image-extra-virtual

After this I did some ALSA and Loopback Device settings:

echo "snd-aloop" >> /etc/modules
modprobe snd-aloop
lsmod | grep snd_aloop # as a sanity check

Setting up ffmepg with X11 capture support

apt install ffmpeg

Installing Google Chrome and ChromeDriver

curl -sS -o - | apt-key add
echo "deb [arch=amd64] stable main" > /etc/apt/sources.list.d/google-chrome.list
apt-get -y update
apt-get -y install google-chrome-stable

Add chrome managed policies file and set CommandLineFlagSecurityWarningsEnabled to false. It will hide warnings in Chrome. You can set it like so:

mkdir -p /etc/opt/chrome/policies/managed
echo '{ "CommandLineFlagSecurityWarningsEnabled": false }' >>/etc/opt/chrome/policies/managed/managed_policies.json

Chromedriver is also required and can be installed like so:

apt install unzip
unzip ~/ -d ~/
rm ~/
sudo mv -f ~/chromedriver /usr/local/bin/chromedriver
sudo chown root:root /usr/local/bin/chromedriver
sudo chmod 0755 /usr/local/bin/chromedriver

And finally the misc tools and dependancies for jibri

apt-get install default-jre-headless ffmpeg curl alsa-utils icewm xdotool xserver-xorg-input-void xserver-xorg-video-dummy
apt autoremove

Now to install the jibri:

wget -qO - | sudo apt-key add -
sh -c "echo 'deb stable/' > /etc/apt/sources.list.d/jitsi-stable.list"
apt-get update
apt-get install jibri
usermod -aG adm,audio,video,plugdev jibri # sanity check

Edit the config file:

vi /etc/jitsi/jibri/config.json

Note: on the first pass through/read I didn’t change anything.

Prosody (on the machine that is not the recorder)

Add your recorder machine to /etc/hosts:

Edit the prosody.cfg.lua one is a component, and another virtual host:

-- internal muc component, meant to enable pools of jibri and jigasi clients
Component "" "muc"
    modules_enabled = {
    storage = "internal"
    muc_room_cache_size = 1000


VirtualHost ""
  modules_enabled = {
  authentication = "internal_plain"

Next create the two accounts jibri will use:

prosodyctl register jibri jibriauthpass
prosodyctl register recorder jibrirecorderpass

Jicofo setup

Edit the /etc/jitsi/jicofo/

Jitsi Meet

Edit the /etc/jitsi/meet/

fileRecordingsEnabled: true, // If you want to enable file recording
liveStreamingEnabled: true, // If you want to enable live streaming
hiddenDomain: '',

YouTube setup

On the youtube side, go to the creator studio then the “Go Live” button on the right hand side. Create a new stream, and change it from Public to Private for testing. Name the stream too. :)

Grab the “Stream Key”, and add it in to the meeting. Assuming you’re the mod on the meeting.

Create a room on jitsi and try to stream!