Switch branches/tags
stable/jitsi-meet_3383 stable/jitsi-meet_3344 stable/jitsi-meet_3229 stable/jitsi-meet_3135 stable/jitsi-meet_2988 jitsi-meet_3389 jitsi-meet_3388 jitsi-meet_3387 jitsi-meet_3386 jitsi-meet_3385 jitsi-meet_3384 jitsi-meet_3383 jitsi-meet_3382 jitsi-meet_3381 jitsi-meet_3380 jitsi-meet_3379 jitsi-meet_3378 jitsi-meet_3377 jitsi-meet_3376 jitsi-meet_3375 jitsi-meet_3374 jitsi-meet_3373 jitsi-meet_3372 jitsi-meet_3371 jitsi-meet_3370 jitsi-meet_3369 jitsi-meet_3368 jitsi-meet_3367 jitsi-meet_3366 jitsi-meet_3365 jitsi-meet_3364 jitsi-meet_3363 jitsi-meet_3362 jitsi-meet_3361 jitsi-meet_3360 jitsi-meet_3359 jitsi-meet_3358 jitsi-meet_3357 jitsi-meet_3356 jitsi-meet_3355 jitsi-meet_3354 jitsi-meet_3353 jitsi-meet_3352 jitsi-meet_3351 jitsi-meet_3350 jitsi-meet_3349 jitsi-meet_3348 jitsi-meet_3347 jitsi-meet_3346 jitsi-meet_3345 jitsi-meet_3344 jitsi-meet_3343 jitsi-meet_3342 jitsi-meet_3341 jitsi-meet_3340 jitsi-meet_3339 jitsi-meet_3338 jitsi-meet_3337 jitsi-meet_3336 jitsi-meet_3335 jitsi-meet_3334 jitsi-meet_3333 jitsi-meet_3332 jitsi-meet_3331 jitsi-meet_3330 jitsi-meet_3329 jitsi-meet_3328 jitsi-meet_3327 jitsi-meet_3326 jitsi-meet_3325 jitsi-meet_3324 jitsi-meet_3323 jitsi-meet_3322 jitsi-meet_3321 jitsi-meet_3320 jitsi-meet_3319 jitsi-meet_3318 jitsi-meet_3317 jitsi-meet_3316 jitsi-meet_3315 jitsi-meet_3314 jitsi-meet_3313 jitsi-meet_3312 jitsi-meet_3311 jitsi-meet_3310 jitsi-meet_3309 jitsi-meet_3308 jitsi-meet_3307 jitsi-meet_3306 jitsi-meet_3305 jitsi-meet_3304 jitsi-meet_3303 jitsi-meet_3302 jitsi-meet_3301 jitsi-meet_3300 jitsi-meet_3299 jitsi-meet_3298 jitsi-meet_3297 jitsi-meet_3296 jitsi-meet_3295
Nothing to show
Find file Copy path
132 lines (90 sloc) 6.09 KB

Jitsi Meet quick install

This document describes the required steps for a quick Jitsi Meet installation on a Debian based GNU/Linux system. Debian 8 (Jessie) or later, and Ubuntu 14.04 or later are supported out-of-the-box.

Debian Wheezy and other older systems may require additional things to be done. Specifically for Wheezy, libc needs to be updated.

Also note that a recent default Ubuntu installation has only the main repository enabled, and Jitsi Meet needs packages from universe. Check your /etc/apt/sources.list file, and if universe is not present refer to Ubuntu's documentation on how to enable it. (Usually it amounts to copying the main lines and changing to universe.)


a.) All commands are supposed to be run by root. If you are logged in as a regular user with sudo rights, please prepend sudo to each of the commands.

b.) You only need to do this if you want to host your own Jitsi server. If you just want to have a video conference with someone, use instead.

Basic Jitsi Meet install

Add the repository

echo 'deb stable/' >> /etc/apt/sources.list.d/jitsi-stable.list
wget -qO - | apt-key add -

Update the package lists

apt-get update

(If you get an error: E: The method driver /usr/lib/apt/methods/https could not be found. run:

apt-get install apt-transport-https


Install Jitsi Meet

Note : Something to consider before installation is how you're planning to serve Jitsi Meet. The installer will check if Nginx or Apache is present (with this order) and configure a virtualhost within the web server it finds to serve Jitsi Meet. If none of the above is found it then configures itself to be served via jetty. So if for example you are planning on deploying Jitsi Meet with a web server, you have to make sure to install the server before installing jitsi-meet.

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 hostname 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

Simply run the following in your shell


Advanced configuration

If installation is on a machine behind NAT further configuration of jitsi-videobridge is needed in order for it to be accessible. 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 the file /etc/jitsi/videobridge/<Local.IP.Address><Public.IP.Address>

See the documenation 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 conferencee: 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

Open a conference

Launch a web browser (Chrome, Chromium or latest Opera) and enter in the URL bar the hostname (or IP address) you used in the previous step.

Confirm that you trust the self-signed certificate of the newly installed Jitsi Meet.


Adding sip-gateway to Jitsi Meet

Install Jigasi

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-web jicofo jitsi-videobridge

Sometimes the following packages will fail to uninstall properly:

  • jigasi
  • jitsi-videobridge

When this happens, just run the uninstall command a second time and it should be ok.

The reason for 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 jvb daemons are already stopped.

Systemd details

To reload the systemd changes on a running system execute systemctl daemon-reload and service jitsi-videobridge restart. To check the tasks part execute service jitsi-videobridge status and you should see Tasks: XX (limit: 65000). To check the files and process part execute cat /proc/`cat /var/run/`/limits and you should see:

Max processes             65000                65000                processes
Max open files            65000                65000                files