Jitsi is an open source video conferencing platform. The software is installed on the server, while the platform is accessible through a browser and a mobile application.
Jitsi features include:
- HD video with webcam background replacement capability;
- screen sharing;
- text chat;
- “raising hand” and reactions;
- polls;
- conference password protection if necessary.
Beget VPS/VDS with pre-installed Jitsi is the current version of the platform installed on your virtual server with the domain name of your choice and an automatically renewed SSL certificate. Install Jitsi Meet for audio and video conferencing, webinars, and meetings right in your browser.
Installation package information
- Jitsi 2.0.10008
- Ubuntu 22.04
- Docker, latest
Jitsi installation
When installing a server, in addition to the standard parameters you will be asked to specify:
- Domain name by which Jitsi will be accessible. You can either choose your domain or register a new one. Alternatively, you can use the free
.beget.appdomain. A free SSL certificate will be issued for this domain. - Admin Email. This email will be used to access Jitsi as an administrator.
- Admin Password. This password will be used to access Jitsi as an administrator.
It takes about 5 minutes to install and deploy the Jitsi Meet system. After that, you can start using Jitsi.
Using Jitsi
To navigate to the Jitsi web interface, follow the link: https://mydomain.beget.app in your browser, where mydomain.beget.app is the domain name selected during the installation process.
To create a conference, enter the URL that will be used to access it, then click “Create Conference”, after which you will be redirected to the meeting page.
Here you can join the Jitsi meeting as a regular user or as an organizer.
To do this, after clicking “Join a meeting”, select “Log-in” and enter the moderator username (by default admin user is created) and the corresponding password.
Having joined as a moderator, you will be able to manage the meeting itself: set a password used to access it, configure the access policy, and much more.
We wish you successful work with the Jitsi server!
FAQ
- Connect to the server via SSH.
After connecting to the server, connect to thejitsi-prosody-1 container:docker exec -it jitsi-prosody-1 /bin/bash - Inside the container, execute the command:
prosodyctl --config /config/prosody.cfg.lua register TheDesiredUsername meet.jitsi TheDesiredPassword
Where TheDesiredUsername is the username you selected and TheDesiredPassword is the password for the user being created.
- Connect to the server via SSH.
- After connecting to the server, connect to the
jitsi-prosody-1 container:docker exec -it jitsi-prosody-1 /bin/bash - In the container, execute the command:
prosodyctl --config /config/prosody.cfg.lua unregister TheDesiredUsername meet.jitsi
Where TheDesiredUsername is the name of the user to be unregistered.
- Connect to the server via SSH.
- After connecting to the server, connect to the
jitsi-prosody-1 container:docker exec -it jitsi-prosody-1 /bin/bash
- In the container, execute the command:
find /config/data/meet%2ejitsi/accounts -type f -exec basename {} .dat \;
Since the solution is installed as Docker containers, it is configured via environment variables in the /opt/beget/jitsi/.env file.
- Container configuration:
/opt/beget/jitsi/docker-compose.yml - Environment variables file:
/opt/beget/jitsi/.env
By default, logs are sent to the standard service container output stream, they are available using the docker logs -t -f <service_name> command, where <service_name> is the name of the service you need (jitsi-web-1, jitsi-jvb-1, jitsi-jicofo-1, jitsi-prosody-1 are available)
Follow the steps below to restart all services:
- Connect to your virtual server via SSH:
ssh root@my-ip, wheremy-ipis the IP address of your server - Navigate to the configuration directory:
cd /opt/beget/jitsi - Run the command:
docker-compose restart
The recordings are not saved by default, you will need to configure the Jibri service manually. The service can be located either on the same server as Jitsi or on a separate server. Detailed configuration is described in the Jitsi documentation.
