Your Meetings

Video conferencing in your infrastructure

“Your Meetings” is a ready-to-use Jitsi Meet service running on your VM and domain. On first boot, the image automatically obtains a Let’s Encrypt certificate and enables HTTPS, a TURN server, a guest lobby, and an LLDAP-based web panel for user management. The service is ready within a few minutes after the VM starts.

Only moderators with an account can create meetings (secure domain mode); guests join using a link without registration. The moderator decides who to admit: the room remains closed until a moderator joins, and the lobby allows guests to be admitted individually. The built-in TURN server (coturn) helps users connect from networks where UDP is restricted.

The core components run on your VM: user accounts, configuration, and group meeting media traffic are processed there. No additional cloud video conferencing service is required.

Participant features

• browser-based video meetings without installing applications or plugins;
• official Jitsi Meet applications for Android and iOS (specify your server address in the application settings);
• chat, screen sharing, hand raising, and reactions;
• adaptive audio and video quality and background blur;
• local meeting recording: video and audio are saved as a WebM file on the participant’s computer, and the other participants are notified; supported in Chromium-based desktop browsers (Chrome and Edge).

The availability of individual client features depends on the browser, operating system, and mobile application version.

Management and security

• secure domain mode: only an authenticated moderator can create a room; a guest cannot start a room on your server;
• lobby and participant management: the lobby is enabled automatically for every room, and the moderator admits guests individually;
• a web panel for managing users and moderator permissions, with per-IP login attempt rate limiting;
• HTTPS with automatic Let’s Encrypt certificate issuance and renewal;
• automatic A record creation if the DNS zone is hosted in Yandex Cloud and a service account with the dns.editor role is attached to the VM;
• built-in coturn: TURN over UDP/TCP 3478 and TURN over TLS on TCP 443 for networks where UDP is blocked.

Not included in the image

• server-side meeting recording and streaming (Jibri): recording is available only locally in a participant’s browser;
• telephone access to meetings (Jigasi, SIP/dial-in);
• calendar integrations;
• a multi-videobridge cluster: all components run on a single VM.

Intended users

• teams and small businesses that need their own video meeting service on their domain instead of a public service;
• organizations that need direct control over their infrastructure, configuration, and user accounts;
• educational projects, consultations, and internal meetings where an authenticated moderator controls guest admission.

Self-hosting provides control over infrastructure and data, but does not by itself demonstrate compliance with Russian Federal Law No. 152-FZ or other requirements. Organizational measures, access permissions, and data processing remain the responsibility of the information system owner.

Components and licenses

Outbound traffic and cost

The total cost consists of the product price shown in the Marketplace listing and the Yandex Cloud resources used: the VM, disk, public IP address, and outbound traffic.

In a group meeting, the videobridge (Jitsi Videobridge) sends multiple video streams to each participant, so outbound traffic may cost more than the VM during active meetings. In a two-person meeting, when a direct P2P connection is available, media traffic usually flows directly between the participants and consumes almost no outbound VM traffic.

For the current price per gigabyte and the free monthly allowance, see the Yandex Cloud pricing policy.

Reducing traffic. You can reduce outbound video traffic using two parameters in config.js: channelLastN, which controls how many video streams each participant receives simultaneously, and the maximum resolution in constraints. For most business meetings, 5–6 video streams and 720p are sufficient. By default, channelLastN is -1, which means that the number of received video streams is unlimited. The /opt/jitsi-meet-cfg/web/config.js file is created automatically when the container starts. For persistent settings, create /opt/jitsi-meet-cfg/web/custom-config.js.

Setup usually takes 5–10 minutes after the VM starts. Prepare a domain, static public IP address, and security group in advance.

Step 1. Domain and static IP address

• Choose the fully qualified domain name for the service, for example, meet.example.com.
• Reserve a static public IPv4 address in the availability zone where the VM will be created.
• If DNS is managed by a third-party provider, create an A record pointing the domain to the reserved IP address.
• If the public DNS zone is hosted in Yandex Cloud, create a service account with the dns.editor role. You will attach it to the VM in step 3. The image automatically creates a missing A record but does not modify an existing record.

Step 2. Network and security group

Create a security group or add the following inbound rules to an existing one:

For ports 22 and 9443, specify only administrator addresses as the source, rather than 0.0.0.0/0: meeting participants do not need access to SSH or the user management panel. Allow outbound internet connections from the VM; they are required for Let’s Encrypt certificate issuance, media traffic, and emergency re-downloads of container images.

During a normal first boot, container images are loaded from a local archive. If the archive is damaged or missing, the image downloads the Jitsi and LLDAP containers from their official repositories. The image does not configure a local firewall. If you enable one yourself, open the same ports as in the security group.

Step 3. Creating the VM and configuring metadata

• In Marketplace, select “Your Meetings” and create the VM in the availability zone where the IP address is reserved.
• Assign the static IP address and security group prepared in steps 1 and 2.
• Under Access, specify the VM administrator username and a public SSH key.
• If the DNS zone is hosted in Yandex Cloud, attach a service account with the dns.editor role under Additional. A service account is not required for external DNS.
• Under Metadata, add the following four required first-boot parameters:

The password remains in the VM metadata and is visible to anyone who has access to the VM in the management console, as well as to processes running inside the VM. Change it after setup (step 5).

Step 4. First boot

After the VM starts, the image checks that the A record points to the VM’s public IP address and only then requests a Let’s Encrypt certificate. Until setup is complete, https://meet.example.com will not open; this is expected.

When setup is complete, open https://meet.example.com. If the service is unavailable after 10–15 minutes, check the service status and logs:

sudo systemctl status first-boot.service --no-pager
sudo journalctl -u first-boot.service -f

The most common cause is that the A record does not yet point to the VM’s IP address or port 80 is not open. After correcting the issue, make sure that the record has been updated (dig +short meet.example.com) and restart setup:

sudo systemctl restart first-boot.service

Step 5. Changing the password and signing in for the first time

Open the user management panel at https://meet.example.com:9443/, sign in using jitsi_admin_user and jitsi_admin_password, and immediately change the administrator password. The initial administrator already belongs to the lldap_admin (directory management) and jitsi_moderators (permission to create meetings) groups.

User management and joining a conference

To add a moderator:

1. Open Users in the panel and click Create a user.
2. Enter User name, Email, Password, and Confirm password, and save the user. User name is used to sign in to Jitsi; the email address is not used for authentication. A password is technically optional in LLDAP, but a user without one cannot sign in to Jitsi.
3. Open Groups, select the jitsi_moderators group, select the user at the bottom of the page, and click Add to group.
4. Give the user the service address, their User name, and password.

A moderator opens the room URL, selects the host sign-in option, and enters their User name and password. A user outside the jitsi_moderators group cannot sign in as a moderator. Guests open the room link without an account.

To revoke permission to create meetings, remove the user from the jitsi_moderators group. Do not delete the jitsi-bind system user or modify its groups. Do not remove the last administrator from the lldap_admin group, or directory management will become unavailable.

“Your Meetings” already helps:

• small and medium-sized businesses — host meetings on their own domain without relying on public services;
• project teams — organize business meetings, presentations, and consultations within their own infrastructure;
• educational organizations — conduct secure classes with moderator authentication and guest admission;
• employees and clients — join video meetings from a browser or mobile application.

For questions about the image, contact support_meet@kodep.ru. Configuration of third-party DNS services, domains, and network environments remains the customer’s responsibility.