Jitsi (cluster)

Deploy Jitsi, a suite of open source projects, to host your own virtual video conferences.

📘
Cluster deployment
The app is deployed with four, five, or seven Linode instances to create a highly available Jitsi cluster, each with the plan type and size you select.
Each of these Linode instance will appear on your invoice as separate items. To deploy Jitsi on a single instance, see the Jitsi guide.

1. Deploy Jitsi `cluster`

Estimated deployment time: 5–10 minutes

Follow the deployment instructions from the Get started section to configure the app, deploy it, and verify software installation.

For information on the app-specific configurations, see the Configuration options section.

Software included

Software installed on your Linode when deploying the app.

Package	Description
Jitsi Meet	A WebRTC compatible JavaScript application that enables the video conferencing.
Jitsi Videobridge (jvb)	A WebRTC compatible server that routes the video streams between participants in the conference.
Jitsi Conference Focus (jicofo)	A server-side focus component that manages sessions between participants.
Prosody	An XMPP server for signaling.

Base distribution and plan

Supported distribution: Ubuntu 24.04 LTS
Recommended plan: All plan types and sizes can be used. For optimal audio and video performance when hosting large meetings or multiple simultaneous meetings, use an 8GB Dedicated CPU or Shared Compute instance.

Configuration options

Configure the required options to deploy your instance. For additional customization, add advanced options.

The table maps the Cloud Manager UI fields to their corresponding API/CLI keys (stackscript_data) required for automated deployments.

StackScript ID: 1350733

UI field	API/CLI key	Description
Required options
Limited sudo user	`username`	Your preferred username for the limited sudo user entered without any capital letters, spaces, or special characters. When adding a limited sudo user, the user is created with a strong generated password for your new Linode instance, and the account is assigned to the `sudo` group, which provides elevated permissions when running commands with the `sudo` prefix. Note: For easier and more secure access with the sudo user, add an account SSH key for the Cloud Manager user during deployment and select that user as an `authorized_user`. Their SSH pubkey will be assigned to both the root and limited sudo users.
Add Account SSH Keys to All Nodes	`add_ssh_keys`	When set to yes, it adds account SSH keys to all nodes. Possible values are: yes or no.
Linode API token	`token_password`	Applies to a custom domain. The Linode API token if you want to use Linode's DNS Manager to manage DNS records for your custom domain. Follow Manage personal access tokens to get your token on your account with `Read/Write` access to `Domains`. If you provide the token along with the subdomain and domain, the installation attempts to create DNS records via the Linode API. If you don't provide the token, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance.
Admin Email for Let's Encrypt SSL certificate	`soa_email_address`	An admin email address to set for the Let's Encrypt SSL certificate.
Advanced options
Disable root access over SSH	`disable_root`	Applies to a limited sudo user. To block the root user from logging in over SSH, select Yes. Defaults to No. Note: When you disable the root user from logging in over SSH and don't provide a valid Account SSH Key assigned to the `authorized_user`, you can still switch to the root user. To do that, log in as root via the Lish console and run `cat /home/$USERNAME/.credentials` to view the generated password for the limited sudo user.
Subdomain	`subdomain`	Applies to a custom domain. The subdomain you want to use, like `blog` for `blog.example.com`. Use it only if you specify a Domain.
Domain	`domain`	Applies to a custom domain. The domain name you want to use, like `example.com`. Use it only if you specify a Linode API token.
Jitsi cluster size	`cluster_size`	The number of Linode instances that are created as part of this cluster. Possible values are: 4 (default) 5 7

Notes:

After the app deployment completes, the password for your limited sudo user is generated and stored in the .credentials file in the home directory, along with application-specific passwords. Log in to your instance as root through the Lish console or SSH, then run cat /home/$USERNAME/.credentials to view its contents.

You can automatically configure a custom domain (optional) during deployment. To do that:

First, configure your domain to use Linode’s name servers via your registrar. See Configure your domain's authoritative name servers for details.

Once you complete that, specify the Linode API token, subdomain, and domain for the app in Cloud Manager or via API/CLI/Terraform.

Use API, CLI, or Terraform

In addition to deploying the app to a new Linode instance via Cloud Manager, you can also use the Linode API, CLI, or Terraform. When running the operation, you need to provide the StackScript ID, supported Linux distribution, and app-specific fields along with the standard Linode deployment configurations.

Note: Generate a personal access token to authenticate your API, CLI, or Terraform requests.

curl --location 'https://api.linode.com/v4/linode/instances' \
    --header 'Content-Type: application/json' \
    --header 'Accept: application/json' \
    --header 'Authorization: Bearer abc123def456hij789klm' \
    --data-raw '{
        "region": "us-east",
        "type": "g6-standard-2",
        "image": "linode/ubuntu24.04",
        "label": "my-jitsi-cluster-one-click-app",
        "root_pass": "@C0mpl3x#P@ssw0rd",
        "stackscript_id": 1350733,
        "stackscript_data": {
            "username":"jsmith",
            "add_ssh_keys": "no",
            "token_password": "abc123def456hij789klm",
            "soa_email_address": "jsmith@example.com"
        }
    }'

linode-cli linodes create \
    --region us-east \
    --type g6-standard-2 \
    --label my-jitsi-cluster-one-click-app \
    --image linode/ubuntu24.04 \
    --root_pass @C0mpl3x#P@ssw0rd \
    --stackscript_id 1350733 \
    --stackscript_data '{"username":"jsmith", "add_ssh_keys":"no", "token_password":"abc123def456hij789klm", "soa_email_address":"jsmith@example.com"}'

resource "linode_instance" "my-linode" {
    region         = "us-east"
    type           = "g6-standard-2"
    label          = "my-jitsi-cluster-one-click-app"
    image          = "linode/ubuntu24.04"
    root_pass      = "@C0mpl3x#P@ssw0rd"
    stackscript_id = 1350733
    stackscript_data = {
        "username"          = "jsmith"
        "add_ssh_keys"      = "no"
        "token_password"    = "abc123def456hij789klm"
        "soa_email_address" = "jsmith@example.com"
    }
}

2. Access Jitsi

Before you go to your app:
- If you filled out the optional Jitsi configuration fields, you can find an entry for your domain with two DNS records, A and AAA, pointing to your new server in Cloud Manager’s DNS Manager, one for the domain name and one for the hostname. Then configure the rDNS on your Linode.
- If you didn’t set up a domain, navigate to the Linode's rDNS address in your browser. You can find it in the Networking tab for your Linode in Cloud Manager. If you did set up a domain, navigate to the address as described in the Configuration options section.
Jitsi prompts you to start a meeting.

Additional resources

For more information about the installed packages, see their official documentation.

📘
Note that we can't vouch for the accuracy or timeliness of externally hosted resources.

Cluster deployment

1. Deploy Jitsi cluster

Software included

Base distribution and plan

Configuration options

Use API, CLI, or Terraform

2. Access Jitsi

Additional resources

1. Deploy Jitsi `cluster`