Product docs and API reference are now on Akamai TechDocs.
Search product docs.
Search for “” in product docs.
Search API reference.
Search for “” in API reference.
Search Results
 results matching 
 results
No Results
Filters
Deploy Jitsi through the Linode Marketplace
Quickly deploy a Compute Instance with many various software applications pre-installed and ready to use.
Deploying a Marketplace App
The Linode Marketplace lets you easily deploy software on a Compute Instance using Cloud Manager. See Get Started with Marketplace Apps for complete steps.
Log in to Cloud Manager and select the Marketplace link from the left navigation menu. This displays the Linode Create page with the Marketplace tab pre-selected.
Under the Select App section, select the app you would like to deploy.
Complete the form by following the steps and advice within the Creating a Compute Instance guide. Depending on the Marketplace App you selected, there may be additional configuration options available. See the Configuration Options section below for compatible distributions, recommended plans, and any additional configuration options available for this Marketplace App.
Click the Create Linode button. Once the Compute Instance has been provisioned and has fully powered on, wait for the software installation to complete. If the instance is powered off or restarted before this time, the software installation will likely fail.
To verify that the app has been fully installed, see Get Started with Marketplace Apps > Verify Installation . Once installed, follow the instructions within the Getting Started After Deployment section to access the application and start using it.
Configuration Options
- Supported distributions: Ubuntu 22.04 LTS
- Suggested minimum plan: All plan types and sizes can be used. For best results, use a 8GB Dedicated CPU or Shared Compute Instance when hosting large meetings or multiple simultaneous meetings.
Jitsi Options
Custom Domain (Optional)
If you wish to automatically configure a custom domain, you first need to configure your domain to use Linode’s name servers. This is typically accomplished directly through your registrar. See Use Linode’s Name Servers with Your Domain . Once that is finished, you can fill out the following fields for the Marketplace App:
Linode API Token: If you wish to use the Linode’s DNS Manager to manage DNS records for your custom domain, create a Linode API Personal Access Token on your account with Read/Write access to Domains. If this is provided along with the subdomain and domain fields (outlined below), the installation attempts to create DNS records via the Linode API. See Get an API Access Token . If you do not provide this field, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance.
Subdomain: The subdomain you wish to use, such as www for
www.example.com
.Domain: The domain name you wish to use, such as example.com.
Admin Email for the Jitsi server
Limited Sudo User
You need to fill out the following fields to automatically create a limited sudo user, with a strong generated password for your new Compute Instance. This account will be assigned to the sudo group, which provides elevated permissions when running commands with the sudo
prefix.
Limited sudo user: Enter your preferred username for the limited user. No Capital Letters, Spaces, or Special Characters.
Locating The Generated Sudo Password A password is generated for the limited user and stored in a
.credentials
file in their home directory, along with application specific passwords. This can be viewed by running:cat /home/$USERNAME/.credentials
For best results, add an account SSH key for the Cloud Manager user that is deploying the instance, and select that user as an
authorized_user
in the API or by selecting that option in Cloud Manager. Their SSH pubkey will be assigned to both root and the limited user.Disable root access over SSH: To block the root user from logging in over SSH, select Yes. You can still switch to the root user once logged in, and you can also log in as root through Lish .
Accessing The Instance Without SSH If you disable root access for your deployment and do not provide a valid Account SSH Key assigned to theauthorized_user
, you will need to login as the root user via the Lish console and runcat /home/$USERNAME/.credentials
to view the generated password for the limited user.
"
) within any of the App-specific configuration fields, including user and database password fields. This special character may cause issues during deployment.Getting Started After Deployment
Jitsi is now installed and ready to use.
Before you go to your app, if you filled out the optional Jitsi configuration fields:
- In Cloud Manager’s DNS Manager
there is now an entry for your domain with two
A/AAAA
records pointing to your new server. One for the domain name and one for the hostname. - Configure the rDNS on your Linode.
- In Cloud Manager’s DNS Manager
there is now an entry for your domain with two
If you didn’t setup a domain, navigate to the rDNS address of the Linode in your browser. You can find the rDNS address in the Networking tab for your Linode in Cloud Manager . If you did setup a domain, navigate to the address as described in the Jitsi Options section above.
Jitsi prompts you to start a meeting.
Software Included
The Jitsi Marketplace App installs the following software on your Linode:
Software | Description |
---|---|
Jitsi Meet | The WebRTC compatible JavaScript application that enables the video conferencing. |
Jitsi Videobridge (jvb) | WebRTC compatible server that routes the video streams between participants in the conference. |
Jitsi Conference Focus (jicofo) | The server-side focus component that manages sessions between participants. |
Prosody | XMPP server for signalling. |
More Information
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on