How to install Jitsi Meet quickly
This guide helps you host your own Jitsi server. If you want to have a video conference without setting up any infrastructure, use https://meet.jit.si instead.
This document describes the required steps for a quick Jitsi Meet installation on a Debian based GNU/Linux system. Debian 9 (Stretch) or later, and Ubuntu 18.04 (Bionic Beaver) or later are supported out-of-the-box.
On Ubuntu systems, Jitsi requires dependencies from Ubuntu’s universe package repository. To ensure this is enabled, run apt-add-repository universe at the command-line.
Note: Many of the installation steps require elevated privileges. If you are logged in using a regular user account, you may need to temporarily increase your permissions (for example, by using sudo for individual commands).
Basic Jitsi Meet install
Set up the Fully Qualified Domain Name (FQDN) (optional)
If the machine used to host the Jitsi Meet instance has a FQDN (for example meet.example.org) already set up in DNS, /etc/hostname must contain this FQDN; if this is not the case yet, change the hostname.
Then add the same FQDN in the /etc/hosts file, associating it with the loopback address:
127.0.0.1 localhost meet.example.org
Finally on the same machine test that you can ping the FQDN with: ping “$(hostname)”-
Add the Jitsi package repository
echo ‘deb https://download.jitsi.org stable/’ >> /etc/apt/sources.list.d/jitsi-stable.list
wget -qO – https://download.jitsi.org/jitsi-key.gpg.key | sudo apt-key add –
Install Jitsi Meet
Note: The installer will check if Nginx or Apache is present (in that order) and configure a virtualhost within the web server it finds to serve Jitsi Meet. If none of the above is found it then defaults to Nginx. If you are already running Nginx on port 443 on the same machine you better skip the turnserver configuration as it will conflict with your current port 443, so use the command apt install –no-install-recommends jitsi-meet.
Ensure support is available for apt repositories served via HTTPS
apt-get install apt-transport-https
Retrieve the latest package versions across all repositories
Perform jitsi-meet installation
apt-get -y install jitsi-meet
During the installation, you will be asked to enter the hostname of the Jitsi Meet instance. If you have a FQDN for the instance already set up in DNS, enter it there. If you don’t have a resolvable hostname, you can enter the IP address of the machine (if it is static or doesn’t change).
This hostname (or IP address) will be used for virtualhost configuration inside the Jitsi Meet and also, you and your correspondents will be using it to access the web conferences.
Generate a Let’s Encrypt certificate (optional, recommended)
In order to have encrypted communications, you need a TLS certificate. The easiest way is to use Let’s Encrypt.
Note: Jitsi Meet mobile apps require a valid certificate signed by a trusted Certificate Authority and will not be able to connect to your server if you choose a self-signed certificate.
Simply run the following in your shell:
Note that this script uses the HTTP-01 challenge type and thus your instance needs to be accessible from the public internet. If you want to use a different challenge type, don’t use this script and instead choose I want to use my own certificate during jitsi-meet installation.
If the installation is on a machine behind NAT jitsi-videobridge should configure itself automatically on boot. If three way call does not work further configuration of jitsi-videobridge is needed in order for it to be accessible from outside. Provided that all required ports are routed (forwarded) to the machine that it runs on. By default these ports are (TCP/443 or TCP/4443 and UDP/10000). The following extra lines need to be added to the file /etc/jitsi/videobridge/sip-communicator.properties:
And comment the existing org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES. See the documentation of ice4j for details.
Default deployments on systems using systemd will have low default values for maximum processes and open files. If the used bridge will expect higher number of participants the default values need to be adjusted (the default values are good for less than 100 participants). To update the values edit /etc/systemd/system.conf and make sure you have the following values:
To load the values and check them look here for details.
By default, anyone who has access to your jitsi instance will be able to start a conference: if your server is open to the world, anyone can have a chat with anyone else. If you want to limit the ability to start a conference to registered users, set up a “secure domain”. Follow the instructions at https://github.com/jitsi/jicofo#secure-domain.
Confirm that your installation is working
Launch a web browser (Chrome, Chromium or latest Opera) and enter the hostname or IP address from the previous step into the address bar.
If you used a self-signed certificate (as opposed to using Let’s Encrypt), your web browser will ask you to confirm that you trust the certificate.
You should see a web page prompting you to create a new meeting. Make sure that you can successfully create a meeting and that other participants are able to join the session.
If this all worked, then congratulations! You have an operational Jitsi conference service.
Adding sip-gateway to Jitsi Meet
Jigasi is a server-side application acting as a gateway to Jitsi Meet conferences. It allows regular SIP clients to join meetings and provides transcription capabilities.
apt-get -y install jigasi
dpkg -i jigasi_1.0-107_amd64.deb
During the installation, you will be asked to enter your SIP account and password. This account will be used to invite the other SIP participants.
Reload Jitsi Meet
Launch again a browser with the Jitsi Meet URL and you’ll see a telephone icon on the right end of the toolbar. Use it to invite SIP accounts to join the current conference.
apt-get purge jigasi jitsi-meet jitsi-meet-web-config jitsi-meet-prosody jitsi-meet-turnserver jitsi-meet-web jicofo jitsi-videobridge2
Sometimes the following packages will fail to uninstall properly:
When this happens, just run the uninstall command a second time and it should be ok.
The reason for the failure is that sometimes the uninstall script is faster than the process that stops the daemons. The second run of the uninstall command fixes this, as by then the jigasi or jitsi-videobridge daemons are already stopped.
To reload the systemd changes on a running system execute systemctl daemon-reload and service jitsi-videobridge2 restart. To check the tasks part execute service jitsi-videobridge2 status and you should see Tasks: XX (limit: 65000). To check the files and process part execute cat /proc/
cat /var/run/jitsi-videobridge/jitsi-videobridge.pid/limits and you should see:
Max processes 65000 65000 processes
Max open files 65000 65000 files
If you run into problems, one thing to try is using a different web browser. Some versions of some browsers are known to have issues with Jitsi Meet. You can also visit https://test.webrtc.org to test your browser’s WebRTC support.
Another place to look is the various log files:
© 2020 GitHub, Inc.