Jitsi Meet on Docker
Jitsi is a set of Open Source projects that allows you to easily build and deploy secure videoconferencing solutions.
Jitsi Meet is a fully encrypted, 100% Open Source videoconferencing solution that you can use all day, every day, for free — with no account needed.
Table of contents
- Quick start
In order to quickly run Jitsi Meet on a machine running Docker and Docker Compose, follow these steps:
- Create a
.envfile by copying and adjusting
docker-compose up -d.
- Access the web UI at
http://localhost:8000for HTTP, or a different port, in case you edited the compose file).
If you want to use jigasi too, first configure your env file with SIP credentials
and then run Docker Compose as follows:
docker-compose -f docker-compose.yml -f jigasi.yml up -d
A Jitsi Meet installation can be broken down into the following components:
- A web interface
- An XMPP server
- A conference focus component
- A video router (could be more than one)
- A SIP gateway for audio calls
The diagram shows a typical deployment in a host running Docker. This project separates each of the components above into interlinked containers. To this end, several container images are provided.
- base: Debian stable base image with the S6 Overlay for process control and the Jitsi repositories enabled. All other images are based off this one.
- base-java: Same as the above, plus Java (OpenJDK).
- web: Jitsi Meet web UI, served with nginx.
- prosody: Prosody, the XMPP server.
- jicofo: Jicofo, the XMPP focus component.
- jvb: Jitsi Videobridge, the video router.
- jigasi: Jigasi, the SIP (audio only) gateway.
Jitsi Meet uses XMPP for signalling, thus the need for the XMPP server. The setup provided by these containers does not expose the XMPP server to the outside world. Instead, it's kept completely sealed, and routing of XMPP traffic only happens on a user defined network.
The XMPP server can be exposed to the outside world, but that's out of the scope of this project.
The configuration is performed via environment variables contained in a
.env file. You
can copy the provided
env.example file as a reference.
IMPORTANT: At the moment, configuration is not regenerated on every container boot, so
if you make any changes to your
.env file, make sure you remove the configuration directory
before starting your containers again.
||Directory where all configuration will be stored||/opt/jitsi-meet-cfg|
||System Time Zone||Europe/Amsterdam|
||Exposed port for HTTP traffic||8000|
||Exposed port for HTTPS traffic||8443|
||IP address of the Docker host, needed for LAN environments||192.168.1.1|
NOTE: The mobile apps won't work with self-signed certificates (the default) see below for instructions on how to obtain a proper certificate with Let's Encrypt.
Let's Encrypt configuration
If you plan on exposing this container setup to the outside traffic directly and want a proper TLS certificate, you are in luck because Let's Encrypt support is built right in. Here are the required options:
||Enable Let's Encrypt certificate generation||1|
||Domain for which to generate the certificate||meet.example.com|
||E-Mail for receiving important account notifications (mandatory)||email@example.com|
In addition, you will need to set
HTTP_PORT to 80 and
HTTPS_PORT to 443.
SIP gateway configuration
If you want to enable the SIP gateway, these options are required:
||SIP URI for incoming / outgoing firstname.lastname@example.org|
||Password for the specified SIP account||passw0rd|
||SIP server (use the SIP account domain if in doubt)||sip2sip.info|
||SIP server port||5060|
Authentication can be controlled with the environment variables below. If guest access is enabled, unauthenticated users will need to wait until a user authenticates before they can join a room. If guest access is not enabled, every user will need to authenticate before they can join.
||Enable guest access||1|
Users must be created with the
prosodyctl utility in the
In order to do that, first execute a shell in the corresponding container:
docker-compose exec prosody /bin/bash
Once in the container, run the following command to create a user:
prosodyctl --config /config/prosody.cfg.lua register user meet.jitsi password
These configuration options are already set and generally don't need to be changed.
||Internal XMPP domain||meet.jitsi|
||Internal XMPP domain for authenticated services||auth.meet.jitsi|
||XMPP domain for the MUC||muc.meet.jitsi|
||XMPP domain for the internal MUC||internal-muc.meet.jitsi|
||XMPP domain for unauthenticated users||guest.meet.jitsi|
||Custom Prosody modules for XMPP_DOMAIN (comma separated)||mod_info,mod_alert|
||Custom Prosody modules for MUC component (comma separated)||mod_info,mod_alert|
||Custom Prosody modules for internal MUC component (comma separated)||mod_info,mod_alert|
||XMPP component password for Jicofo||s3cr37|
||XMPP user for Jicofo client connections||focus|
||XMPP password for Jicofo client connections||passw0rd|
||XMPP user for JVB MUC client connections||jvb|
||XMPP password for JVB MUC client connections||passw0rd|
||STUN servers used to discover the server's public IP||stun.l.google.com:19302, stun1.l.google.com:19302, stun2.l.google.com:19302|
||UDP port for media used by Jitsi Videobridge||10000|
||Disable the additional harvester which allows video over TCP (rather than just UDP)||true|
||TCP port for media used by Jitsi Videobridge when the TCP Harvester is enabled||4443|
||MUC name for the JVB pool||jvbbrewery|
||Comma separated list of JVB APIs to enable||none|
||XMPP user for Jigasi MUC client connections||jigasi|
||XMPP password for Jigasi MUC client connections||passw0rd|
||MUC name for the Jigasi pool||jigasibrewery|
||Minimum port for media used by Jigasi||20000|
||Maximum port for media used by Jigasi||20050|
||Disable HTTPS, this can be useful if TLS connections are going to be handled outside of this setup||1|
||Redirects HTTP traffic to HTTPS||1|
Running on a LAN environment
If running in a LAN environment (as well as on the public Internet, via NAT) is a requirement,
DOCKER_HOST_ADDRESS should be set. This way, the Videobridge will advertise the IP address
of the host running Docker instead of the internal IP address that Docker assigned it, thus making ICE
The public IP address is discovered via STUN. STUN servers can be specified with the
- Support container replicas (where applicable).
- Docker Swarm mode.
- More services:
- TURN server.