This is a quick-wiki for quick reference for my occasional Jitsi Meet installations.
Table of Content
- Limit RAM usage
- Restart setup
- Check installation version
- Log files
- Interface changes
- RTMP stream and record setup
- Quick links
Limit RAM usage
Both jicofo and jvb are configured to take by default up to 3 GB of RAM each. On a machine with running both by default almost ~8 GB RAM is required. Memory hog keeps on building due to not so aggressive garbage collection, but it can be instructed to use less 1.
For jvb, add the following line in
For jicofo, add the following line in
if [ -z "$JICOFO_MAX_MEMORY" ]; then JICOFO_MAX_MEMORY=320m; fi
Change the memory size as you want and do a restart for applying new changed configs.
I host a personal instance for friends and family on 1 GB EC2, 320 MB each for jvb and jicofo is fine for 5-6 folks with videos on.
sudo /etc/init.d/prosody restart sudo /etc/init.d/jicofo restart sudo /etc/init.d/jitsi-videobridge2 restart
or a copy-paste one liner for above:
sudo /etc/init.d/prosody restart && sudo /etc/init.d/jicofo restart && sudo /etc/init.d/jitsi-videobridge2 restart
Check installation version
dpkg -l | grep jitsi
Returns versions of all the components installed with description.
- jvb -
- jicofo -
- prosody -
- fail2ban -
- unattended upgrades -
The UI can be customized by making changes in
Following are some handy variables to change:
APP_NAME- change title.
DEFAULT_LOCAL_DISPLAY_NAME- changes default name for self (before name is set, default is “me”).
DEFAULT_LOGO_URL- to change away from default Jitsi logo in meeting.
DEFAULT_REMOTE_DISPLAY_NAME- change default name for everyone else (default is “Fellow Jitster”).
DEFAULT_WELCOME_PAGE_LOGO_URL- main page logo.
DISABLE_JOIN_LEAVE_NOTIFICATIONS- set it to true to disable notification pop ups on every join/leave.
JITSI_WATERMARK_LINK- change where should the logo redirect on click, in meeting screen.
RTMP stream and record setup
Note - For self-hosted Jitsi Meet instances, additional Jibri setup is required. meet.jit.si has a Jibri instance running, so that can be used.
This setup allows you to record stream on server (without default Dropbox) as well as stream meeting (without default YouTube). Steps:
- Setup a RTMP server (see this link for a basic RTMP server setup).
- From Jitsi click “Start a live stream”.
- Put URL in following format
rtmp://<server-ip-or-domain>/live/STREAM-KEYin “Live stream key”.
- The same URL would be used for viewing the stream.
Prosody - XMPP server. Jitsi uses XMPP for signalling.
Jitsi Conference Focus (jicofo) - server side focus component that manages media sessions between each participant and the videobridge.
Jitsi Videobridge (jvb) - video router.
Jitsi Gateway to SIP (Jigasi) - server-side application that allows regular SIP clients to join Jitsi Meet calls.
Jibri - broadcasting and recording. It works by launching a headless Chrome instance rendered in a virtual framebuffer and capturing and encoding the output with ffmpeg.
STUN (Session Traversal Utilites for NAT) - Standard set of methods for traversal of Network Address Translator (NAT) gateways in applications of realtime voice, video, messaging and other interactive communications. Public IP is discovered via STUN server and type of NAT, usually during session start. Doesn’t provide a complete solution. Originally was “Simple Traversal of User Datagram Protocol (UDP) through Network Address Translators” but updated in RFC 5389.
TURN (Traversal Using Relay NAT) - The TURN Server is a VoIP media traffic NAT traversal server and gateway. It can be used as a general-purpose network traffic server and gateway, too. Resource intensive so used as last resort in Jitsi.
- Self hosting guide for Debian/Ubuntu server
- Network diagram for setup
- Limit the number of participants
- Enable authentication for new meeting creation