Skip to main content

Cloud Server with Jitsi Meet

Last update:

Jitsi Meet is a fully encrypted, open source video conferencing solution.

You can create a cloud server with a ready-made Jitsi Meet application.In Russia, the application runs on a cloud server with a customized SelectOS 1.1 operating system .In other countries — Ubuntu 22.04.

Create a cloud server with Jitsi Meet

To configure Jitsi Meet, you must specify user data — custom operating system configuration parameters — when creating the server. You can specify two sets of variables:

  • to access Jitsi Meet from the Internet;
  • to access Jitsi Meet on a private subnet only.

For a server with access from the Internet, you will need to configure mandatory authorization and create users with the ability to create a conference.For a server in a private subnet, authorization can be disabled — access to Jitsi Meet will be available by domain name.

  1. Create a public IP address.

  2. Create a cloud server with Jitsi Meet.

1.Create a public IP address

Create a public IP address so that the cloud server with Jitsi Meet can be accessed from the internet.

Use the Create a Public IP Address subsection of the Public IP Addresses instruction.

2. Create a cloud server with Jitsi Meet

  1. In the Dashboard, on the top menu, click Products and select Cloud Servers.

  2. Click Create Server.

  3. Fill in the blocks:

  4. Check the price of the cloud server.

  5. Click Create.

Name and location

  1. Enter the server name. This will be set as the host name in the operating system.

  2. Select the region and pool segment in which the server will be created.The list of available server configurations and resource costs depends on the pool segment.Once the server is created, you cannot change the pool segment.

Source

  1. Open the Applications tab.

  2. Select Cloud Jitsi Meet.

  3. Optional: if you need another current or archived version of the application, select the desired version in the Version field.

Configuration

Select a configuration from 4 vCPU, RAM от 8 ГБ and размером загрузочного диска от 10 ГБ.Two types of configurations are available for the server:

The configurations use different processors depending on the line and pool segment.After the server is created, you can change the configuration.

  1. Click Fixed.

  2. Open the tab with the desired ruler.

  3. Select a configuration.

  4. If both local and network disks are available in the selected configuration, select the disk to be used as the boot disk:

    • local disk — check the box Local SSD NVMe disk. A server with a local disk can only be created from images and applications;
    • network drive — do not check the checkbox.

    The amount of RAM allocated to the server may be less than the amount specified in the configuration — the operating system kernel reserves some RAM depending on the kernel version and distribution. You can check the allocated amount on the server with sudo dmesg | grep Memory.

Disks

  1. If you did not check the Local SSD NVMe disk checkbox when setting up the configuration. the first specified network drive will be used as the server boot disk.To configure it:

    1.1 Select the type of network boot disk.

    1.2 Specify the size of the network boot disk in GB or TB. Observe the maximum size limits of network disks.

    1.3 If you selected the Universal v2 disk type, specify the total number of read and write operations in IOPS. After creating a disk, you can change the number of IOPS — decrease or increase.The number of IOPS changes is unlimited.

  2. Опционально: добавьте дополнительный network disk server :

    2.1 Click Add.

    2.2 Select the type of network drive.

    2.3. Укажите размер сетевого диска в ГБ или ТБ. consider the maximum size limits of network drives.

    2.4 If you selected the Universal v2 disk type, specify the total number of read and write operations in IOPS. After creating a disk, you can change the number of IOPS — decrease or increase. There is no limit to the number of IOPS changes.

    After the server is created, you can connect new additional disks.

Network

The server can be added to a new private subnet or to an existing one.

Private — A subnet without access from the Internet or with a single static public IP address.The public IP address connects to a server that will be accessible from the Internet.

  1. Click Private Subnet.

  2. In the Public IP address for Internet access field, select the public IP address you created earlier or create a new one.

  3. Expand the block with private subnet settings.

  4. In the Subnet field, select an existing subnet.

  5. In the Private IP field, specify the private IP address of the server. The public IP address will be automatically connected to the private address.

Safety

Select security groups to filter traffic on server ports. Without security groups, traffic will not be allowed. If there is no block, port security is disabled on the server network . With traffic filtering disabled, all traffic will be allowed.

Access

  1. Place an SSH key for the project on the server for secure connection:

    1.1 If the SSH key for the project is not added to the cloud platform, click Add SSH Key, enter the key name, insert the public key in OpenSSH format, and click Add.

    1.2. If an SSH key for the project is added to the cloud platform. select the existing key in the SSH key field.SSH key is available only in the pool in which it is hosted.

  2. Optional: in the Password field for "root":

    2.1 Copy the password of the root user — a user with unlimited rights to all actions on the system.

    2.2 Save the password in a safe place and do not transmit it in public.

Additional settings

  1. If you plan to create multiple servers and want to improve the fault tolerance of your infrastructure, add the server to a placement group:

    1.1 To create a new group, in the Placement Group field, click New.

    1.2. Select New Group and enter a group name.

    1.3 Select a policy for hosting on different hosts:

    • preferably soft-anti-affinity. The system will try to place servers on different hosts. If there is no suitable host when creating a server, it will be created on the same host;
    • anti-affinity is mandatory. Servers in a group must be located on different hosts. If there is no suitable host when creating a server, the server will not be created.

    1.4 If a group has been created, select the placement group in the Placement Group field.

  2. To add additional information or filter servers in the list, add server tags. Operating system and configuration tags are automatically added. To add a new tag, enter a tag in the Tags field.

  3. To add a script that will be executed by the cloud-init agent when the operating system first starts up, in the Automation block in the User data field:

    • open the Text tab and paste the script with text;
    • or open the File tab and upload the file with the script.
#cloud-config

write_files:
- path: "/opt/gomplate/values/user-values.yml"
  permissions: "0644"
  content: |
    jitsi_HTTP_PORT: "80"
    jitsi_HTTPS_PORT: "443"
    jitsi_TZ: "<time_zone>"
    jitsi_PUBLIC_URL: "<jitsi_meet_public_url>"
    jitsi_IP: "<public_ip_address>"
    letsencrypt:
      enable: true
      letsencryptDomain: "<example.com>"
      letsencryptEmail: "<root@example.com>"
    auth:
      enable: true

Specify:

  • <time_zone> — time zone, e.g. UTC;
  • <jitsi_meet_public_url> — Jitsi Meet public URL in the format jitsi.example.com;
  • <public_ip_address> — The public IP address that you specified in step 10. You can view it in the control panel in the top menu, click Products → Cloud Servers → Network → tab Public IP addresses;
  • letsencrypt: enable: true — parameter to automatically issue a TLS certificate from Let's Encrypt®;
  • <example.com> — domain to access the Jitsi Meet you added earlier;
  • auth: enable: true — parameter to enable mandatory authorization for conference creation.

Create a user with the ability to create a conference

If the cloud server with Jitsi Meet has access from the internet, create users who can create video conferences.

  1. Connect to the cloud server.

  2. Log in as root user.

  3. Create a user with the ability to create a conference:

    docker exec jitsi-prosody-1 prosodyctl --config /config/prosody.cfg.lua register <username> meet.jitsi <password>

    Specify:

    • <username> — login of the new user;
    • <password> — password for the new user.

Access Jitsi Meet

If the cloud server with Jitsi Meet does not have access from the internet, you can access Jitsi Meet by domain name. To do this:

  • create an A-record on the local DNS server for the Jitsi Meet private URL in the format https://meet.local;
  • or add an A-record to the hosts file on the clients.

Add a custom certificate

A custom certificate can be added to a cloud server with Jitsi Meet.

  1. If you are using a full certificate chain and private key in .pem format, rename them to cert.crt and cert.key.

  2. Connect to the cloud server.

  3. Log in as root user.

  4. Copy the cert.crt and cert.key files to the /opt/jitsi/data/.jitsi-meet-cfg/web/keys folder

  5. Perform a programmatic reboot the cloud server.