> Source: https://meetrix.io/blogs/plugnmeet-developer-guide/
> Markdown copy of that page. Cite the URL above, not this file.

Development

# LiveKit Pro - Developer Guide

[By Binuka Ranatunga](https://meetrix.io/blogs/authors/binuka-ranatunga/) • November 19, 2026 • 18 min read

Learn how to deploy LiveKit Pro on AWS with our step-by-step guide. It walks you through launching the Meetrix LiveKit Pro AMI with CloudFormation, pointing your domain and its TURN name at the server, signing in to the meetings page, running and recording your first meeting, and keeping the server healthy once it runs.

LiveKit Pro is a self-hosted video conferencing platform with recording, built on [plugNmeet](https://www.plugnmeet.org/) and the [LiveKit](https://docs.livekit.io/) WebRTC media server. Hosts and guests meet in the browser with HD video, screen sharing and chat, and the host can record the meeting, draw on a shared whiteboard, take shared notes, run polls, split people into breakout rooms and stream out over RTMP. A Meetrix meetings page in front of it lets you sign in as the admin, create meetings and share guest links. On AWS Marketplace it is listed as [LiveKit Based Video Conferencing with Recording, Whiteboard and Polls](https://aws.amazon.com/marketplace/pp/prodview-m3cuujz3dtnak).

The Meetrix image runs plugNmeet server 2.5.3, web client 2.5.4, recorder 2.3.1 and LiveKit server 1.13.11 on Ubuntu 26.04, behind HAProxy with Let's Encrypt SSL and built-in TURN on port 443. If you only need meetings without recording, [LiveKit Lite](https://meetrix.io/blogs/livekit-lite-developer-guide/) runs on a smaller instance. If you are moving off Jitsi, our look at [plugNmeet as a Jitsi and Jibri replacement](https://meetrix.io/blogs/plugnmeet-jitsi-jibri-replacement/) covers what changes, and [LiveKit vs Jitsi](https://meetrix.io/blogs/livekit-vs-jitsi/) compares the two media servers.

Prerequisites

Before you get started with the LiveKit Pro AMI, ensure you have the following prerequisites:

-   Basic knowledge of AWS services, including EC2 instances and CloudFormation.
-   An active AWS account with appropriate permissions.
-   An EC2 key pair in the region you will deploy to.
-   A domain name where you can create two A records, such as meet.example.com and turn.meet.example.com. Browsers only allow camera and microphone access over HTTPS, so meetings need a domain with a valid certificate.
-   If you encounter a vCPU quota error when launching the stack, follow [https://meetrix.io/blogs/increase-aws-vcpu-quota/](https://meetrix.io/blogs/increase-aws-vcpu-quota/) to increase your vCPU limit.

## Launching the AMI

### Step 1: Find and Select LiveKit Pro AMI

1.  Log in to your AWS Management Console.
2.  Navigate to '[LiveKit Based Video Conferencing](https://aws.amazon.com/marketplace/pp/prodview-m3cuujz3dtnak)' in AWS Marketplace.

### Step 2: Initial Setup & Configuration

1.  Click the **"Continue to Subscribe"** button.
2.  After subscribing, accept the terms and click **"Accept Terms"**.
3.  Wait a few minutes until processing completes, then click **"Continue to Configuration"**.
4.  Select the **CloudFormation** fulfillment option and choose your region. Click **"Continue to Launch"**.
5.  From the "Choose Action" dropdown, select **"Launch CloudFormation"** and click **"Launch"**.

## Create CloudFormation Stack

### Step 1: Create a stack

1.  Ensure the **"Template is ready"** option is selected under "Prepare template".
2.  Click "Next".

### Step 2: Specify stack options

1.  Provide a unique **"Stack name"**.
2.  Enter the **"AdminEmail"** used for SSL certificate generation. Let's Encrypt sends its expiry notices here.
3.  Enter an **"AdminPassword"** for the meetings page sign-in. It must be 8 to 64 characters long and can use letters, digits and the characters **\_ @ # % + = . -** only.
4.  Enter an **"AdminUsername"** for the meetings page sign-in, or keep **admin**. It must be 3 to 40 letters, digits or **. \_ @ -** characters.
5.  Leave **"AmiId"** as filled in by AWS Marketplace.
6.  Enter a value for **"DeploymentName"**, or keep **prod**. It goes into the names of the stack's resources, so use a different one for each stack.
7.  Set **"DiskSize"** in GB (default **50**, minimum 30). Recordings are stored on this disk, so size it for how much you plan to record.
8.  Provide a lowercase public domain for **"DomainName"**, such as meet.example.com. This is the address hosts and guests will open, and TURN uses **turn.<your domain>**.
9.  Choose an instance type **"InstanceType"** (Default: **c6i.large**). One 1080p cloud recording uses about 1.5 vCPU, so choose **c6i.xlarge** or larger if you record often.
10.  Select your preferred **"KeyName"**.
11.  Set **"SSHLocation"** to your own IP range, such as 203.0.113.10/32, or 0.0.0.0/0 to allow SSH from anywhere.
12.  Keep **"SubnetCidrBlock"** as 10.0.0.0/24.
13.  Keep **"VpcCidrBlock"** as 10.0.0.0/16.
14.  Click "Next".

### Step 3: Configure stack options

1.  Choose "Roll back all stack resources" and "Delete all newly created resources" under "Stack failure options".
2.  Click "Next".

### Step 4: Review

Review and verify the parameters you've entered, then click **"Submit"**.

![CloudFormation Parameters tab for the LiveKit Pro stack showing AdminEmail, AdminPassword, AdminUsername, AmiId, DeploymentName, DiskSize set to 50, DomainName, InstanceType set to c6i.large, KeyName, SSHLocation and the CIDR blocks](https://meetrix.io/blog-images/paas-dev-guides/plugnmeet/plugnmeet-01.png)

Afterward, you'll be directed to the CloudFormation stacks page. Wait until the stack status shows **CREATE\_COMPLETE**, usually within a few minutes. The server keeps setting itself up for a few minutes after that: on first boot it generates new secrets for this server only (the LiveKit and plugNmeet API keys, the database password and the NATS keys), writes your domain and turn.<your domain> into the configuration, creates the admin login you entered, starts every service and starts trying to issue the SSL certificate.

The stack creates a VPC with a public subnet, internet gateway and route table, a security group, an Elastic IP, and the EC2 instance with a gp3 root volume of the DiskSize you chose.

### Ports the stack opens

Video meetings need more than HTTPS. The security group opens these ports, and if you replace it or add a firewall in front of the server, keep them open:

| Port | Protocol | Purpose |
| --- | --- | --- |
| 22 | TCP | SSH, from SSHLocation only |
| 80 | TCP | Certificate issuance and the redirect to HTTPS |
| 443 | TCP | The web app, signalling, and TURN over TLS on turn.<your domain> |
| 443 | UDP | TURN over UDP |
| 7881 | TCP | WebRTC over TCP |
| 50000-60000 | UDP | WebRTC audio and video |
| 1935 | TCP | RTMP ingest, for streaming a source such as OBS into a meeting |

Without the UDP range, participants can join a meeting but nobody gets audio or video. The SIP ports for phone dial-in stay closed until you turn that feature on (see **Optional Features** below).

## Update DNS

### Step 1: Copy IP Address

Copy the public IP labeled **"PublicIp"** in the **"Outputs"** tab. The **DnsRecords** output lists the two names to point at it, and the tab also shows the **MeetingsUrl**, how to sign in, and where the server details are.

![LiveKit Pro CloudFormation stack Outputs tab listing AdminLogin, DnsRecords with the two A records to create, MeetingsUrl, PublicIp and ServerDetails](https://meetrix.io/blog-images/paas-dev-guides/plugnmeet/plugnmeet-03.png)

### Step 2: Create two A records

1.  Go to AWS Route 53 and navigate to "Hosted Zones", then open your domain's zone.
2.  Click **Create record**.
3.  Add a **record name** matching the DomainName you entered, keep the record type as **A**, and paste the copied **PublicIp** into the **value** textbox.
4.  Click **"Add another record"** and create a second A record for **turn.<your domain>** with the same PublicIp.
5.  Click **"Create records"**.

![Route 53 Quick create record form for an A record in the hosted zone, with Record name, Value, TTL and the Add another record button](https://meetrix.io/blog-images/paas-dev-guides/plugnmeet/plugnmeet-04.png)

If your domain is hosted with another DNS provider, create the same two A records there.

## SSL Certificate

You don't need to run anything to get the certificate. Every 10 minutes, LiveKit Pro checks whether your domain points at the server, and as soon as it does, it requests a Let's Encrypt certificate covering both your domain and turn.<your domain>. Until then, HAProxy serves a temporary certificate and your browser warns that the connection is not private. The certificate renews automatically.

To issue it right away instead of waiting, follow these steps.

### Step 1: Check that DNS resolves

From your own machine, check that both names return the PublicIp from the Outputs tab:

```bash
nslookup <your domain>
nslookup turn.<your domain>
```

### Step 2: Log in to the server

1.  Open the terminal and go to the directory where your private key is located.
2.  Run the following command, replacing the key name and IP address.
3.  Type "yes" and press Enter to confirm.

```bash
ssh -i <your key name> ubuntu@<Public IP address>
```

![Terminal connecting to the server over SSH and confirming the host fingerprint](https://meetrix.io/blog-images/paas-dev-guides/plugnmeet/plugnmeet-06.png)

### Step 3: Issue the certificate

```bash
sudo meetrix-cert
```

When both names resolve, it prints **Certificate covers <your domain> and turn.<your domain>**. If only your main domain points at the server so far, the certificate is issued for that name alone: meetings work, but TURN over TLS stays off until the turn record resolves, and the certificate is extended to cover it automatically within 10 minutes after that. If neither name resolves yet, the command tells you which record is missing.

## Access LiveKit Pro

Open the **"MeetingsUrl"** from the Outputs tab, https://<your domain>, in your browser.

Use your domain, not the IP address

Browsers block the camera and microphone on pages that are not served over HTTPS with a valid certificate, so a call cannot start from http://<Public IP> or past a certificate warning. Always use the HTTPS domain.

Note

If you receive a "503 Service Unavailable" or "502 Bad Gateway" error, wait approximately **5 minutes** and refresh the page. The server may still be finishing its first boot.

Sign in with the **AdminUsername** and **AdminPassword** you set in the stack parameters. After 5 wrong attempts from the same IP address, sign-in is blocked for 10 minutes.

![LiveKit Pro Admin sign in page on its own domain with Username and Password fields and the Sign in button](https://meetrix.io/blog-images/paas-dev-guides/plugnmeet/plugnmeet-05.png)

### Create and start your first meeting

1.  Under **"New meeting"**, enter a **Meeting title**. Leave **"Guests wait in a waiting room until you let them in"** ticked if you want to admit each guest yourself, or untick it to let guests straight in.
2.  Click **"Create meeting"**. The meeting appears under **"Your meetings"**.
3.  Click **"Copy guest link"** and send the link to your guests.
4.  Click **"Start"** to open the meeting as host, and allow camera and microphone access when the browser asks. The name other participants see comes from the **"Your name in meetings"** field.

While a meeting is running, it shows as **Live now** and its button changes to **Join**. **Delete** removes the meeting, ends it if it is live, and stops its guest link from working.

Guests open the link, enter their name and click **"Join"**. No account or app is needed. If the meeting has not started yet, they see a message saying so and join automatically when you start it. With the waiting room on, you admit them from inside the meeting.

Inside the meeting, participants can share their screen, chat and share files, raise a hand and react. The host also has the whiteboard, shared notes, polls, breakout rooms (up to 6), an external media player, RTMP broadcasting to a service such as YouTube Live, and ingest of an RTMP or WHIP source into the meeting.

## Use the Whiteboard and Shared Notes

### Whiteboard

The whiteboard is built on Excalidraw, and everyone in the meeting sees what is drawn on it.

1.  In the meeting, click the **Whiteboard** icon in the control bar at the bottom of the screen.
2.  Draw freehand with the pen, or add shapes, arrows and text, with your choice of colours and stroke styles.
3.  To add an image (JPG or PNG), drag it onto the board, paste it with Ctrl+V (Cmd+V on a Mac), or use the **Image** icon in the whiteboard toolbar.
4.  To present a PDF, Word document or PowerPoint presentation, click the **Files** icon, upload the file, then select it to show it on the board. This uploader is for documents only, so add images with the Image icon. On this server, each whiteboard file can be up to 30 MB.

As the host, you can give a participant permission to draw on the board, and the meeting's lock settings let you lock whiteboard sharing for attendees.

Export the board before the meeting ends

You can export the whole whiteboard as a PNG or SVG file at any time. Files uploaded to the whiteboard and the chat are deleted from the server when the session ends, so export anything you want to keep first. To keep uploads instead, set **keep\_forever: true** under **upload\_file\_settings** in /opt/plugNmeet/config.yaml and run **sudo systemctl restart plugnmeet**.

### Shared notes

Open the **More Options** menu (...) in the control bar and select **Enable shared notepad**. Everyone in the meeting can then write and edit the same notes in real time, and you can format the text and import or export it. The [plugNmeet moderator guide](https://www.plugnmeet.org/docs/user-guide/moderator) covers the rest of the host controls.

## Record Meetings

Only hosts can record. Start a cloud recording with the **Record** button in the meeting, and stop it there or by ending the meeting. Each recording is saved as an MP4 file on the server's disk:

```bash
/opt/plugNmeet/recording_files/node_01/<meeting id>/<recording id>.mp4
```

The meeting id is the **m-xxxxxxxxxx** part of the guest link. One 1080p recording uses about 1.5 vCPU while it runs, so on the default c6i.large, keep to one recording at a time or move up to c6i.xlarge.

### Download recordings over SSH

From your own machine, copy every recording into a local folder:

```bash
scp -i <your key name> -r ubuntu@<Public IP address>:/opt/plugNmeet/recording_files/node_01/ ./recordings/
```

### Download recordings through the API

To automate downloads, use the [plugNmeet API](https://www.plugnmeet.org/docs/api/intro) with the API key and secret from the server details file (see the next section). Every call is a POST to https://<your domain>/auth/<method>, signed with an HMAC-SHA256 of the request body:

```bash
KEY=<API key>; SECRET=<API secret>; HOST=https://meet.example.com
call() { sig=$(printf '%s' "$2" | openssl dgst -sha256 -hmac "$SECRET" | sed 's/^.* //');
         curl -s -X POST "$HOST/auth/$1" -H "Content-Type: application/json" \
              -H "API-KEY: $KEY" -H "HASH-SIGNATURE: $sig" -d "$2"; }

# List a meeting's recordings
call recording/fetch '{"room_ids":["m-xxxxxxxxxx"],"from":0,"limit":20,"order_by":"DESC"}'

# Get a download token for one of them
call recording/getDownloadToken '{"record_id":"<record_id from fetch>"}'
```

Download the file from https://<your domain>/download/recording/<token>. The token is valid for 30 minutes.

Recordings are not deleted automatically

Every recording stays on the server's disk until you remove it. Check free space now and then with **df -h /**, and either grow the EBS volume or move old recordings off the server.

## Server Credentials and API Keys

On first boot, the server writes its details to a file in the ubuntu user's home directory: the meetings URL, the admin username, the two DNS names, the plugNmeet API key and secret, the recordings folder and the settings file.

```bash
cat ~/plugnmeet-credentials.txt
```

You don't need the API key and secret to run meetings from the meetings page. They are for your own integrations, such as recording downloads or creating rooms from your application with the plugNmeet API. Keep the secret private, because anyone who has it can control your server's meetings.

## Change the Admin Login

On the meetings page, click **"Change password"**. Enter your current password and the new one, and optionally a new username, then click **"Save"**. Saving signs you out on every device, so sign in again with the new details.

If you have forgotten the password, log in to the server and set a new one. The command asks for the username, then the new password twice:

```bash
sudo meetrix-admin-reset
```

## Optional Features: Transcription, AI Assistant and Phone Dial-In

Live transcription and translation, an AI meeting assistant with summaries, and SIP phone dial-in are built in but turned off, because they need your own provider accounts. The providers bill you directly. All three are set in one file:

```bash
sudo nano /opt/plugNmeet/config.yaml

sudo systemctl restart plugnmeet
```

Meetings started after the restart get the feature, and the meetings page turns the matching buttons on automatically.

### Live transcription and translation (Microsoft Azure)

You need an Azure **Speech** resource (a key and its region, such as eastus) and an Azure **Translator** resource (a key, region global). In the **insights** section, set **enabled** to true and fill in the Azure credentials:

```yaml
insights:
  enabled: true
  providers:
    azure:
      - id: "eastus_standard"
        credentials:
          api_key: "<Azure Speech key>"
          region: "eastus"
      - id: "transGlobal"
        credentials:
          api_key: "<Azure Translator key>"
          region: "global"
```

### AI chat assistant and meeting summaries (Google Gemini)

You need a Gemini API key from Google AI Studio. Add it under the same **insights.providers** section:

```yaml
insights:
  enabled: true
  providers:
    google:
      - id: "default-gemini-creds"
        credentials:
          api_key: "<Gemini API key>"
```

If you use both providers, keep **azure** and **google** under one **providers** block. If you only use one, leave the other provider's placeholder key in place; only its features fail when someone tries them.

### Phone dial-in (SIP)

You need a SIP trunk provider, such as Twilio or Telnyx, with a phone number pointed at sip:<your domain>:5060.

1.  Turn SIP on in config.yaml with your numbers as callers dial them. If your provider uses trunk authentication, also add **auth\_username** and **auth\_password**.
2.  Open these ports in the stack's security group: **5060-5061 TCP and UDP**, and **10000-20000 UDP**.
3.  Restart plugNmeet with **sudo systemctl restart plugnmeet**.

```yaml
livekit_sip_info:
  enabled: true
  trunk_name: "pnm-inbound-trunk"
  phone_numbers: ["+1XXXXXXXXXX"]
```

## Check Server Logs

### Step 1: Log in to the server

```bash
ssh -i <your key name> ubuntu@<Public IP address>
```

![Terminal connecting to the server over SSH with a private key](https://meetrix.io/blog-images/paas-dev-guides/plugnmeet/plugnmeet-07.png)

### Step 2: Check the logs

LiveKit Pro runs as these services: **plugnmeet** (a Docker Compose stack with LiveKit, Ingress, SIP, NATS and plugnmeet-server), **plugnmeet-recorder**, **meetrix-portal** (the meetings page), **haproxy**, **mariadb** and **redis-server**. Check that they are running, then follow the logs of the first three:

```bash
sudo systemctl status plugnmeet plugnmeet-recorder meetrix-portal haproxy

sudo journalctl -u plugnmeet -u plugnmeet-recorder -u meetrix-portal -f
```

Press **Ctrl+C** to stop following the logs. plugNmeet also writes its own logs to /opt/plugNmeet/log/, and the first boot is logged in /var/log/plugnmeet-firstboot.log:

```bash
sudo cat /var/log/plugnmeet-firstboot.log
```

To restart everything that serves meetings:

```bash
sudo systemctl restart plugnmeet plugnmeet-recorder meetrix-portal
```

## Shutting Down LiveKit Pro

1.  In CloudFormation, open the **"Resources"** tab and click the physical ID of the EC2 instance (**plugnmeetInstance**).
2.  Stop the LiveKit Pro instance from the **Instance state** dropdown. You can restart it later as needed.

![CloudFormation Resources tab with the EC2 Instance physical ID link](https://meetrix.io/blog-images/paas-dev-guides/plugnmeet/plugnmeet-08.png) ![EC2 Instance state dropdown with the Stop instance option](https://meetrix.io/blog-images/paas-dev-guides/plugnmeet/plugnmeet-09.png)

The Elastic IP stays attached and your recordings stay on the disk while the instance is stopped, so everything is where you left it when you start it again. Any meeting in progress ends when the instance stops.

## Remove LiveKit Pro

Copy your recordings first

Deleting the stack deletes the instance and its disk, and every recording on it. Download the recordings you want to keep before you delete the stack.

Delete the CloudFormation stack from the AWS Management Console under "CloudFormation Stacks" by clicking "Delete". Remove both Route 53 records you created as well.

## Upgrades

When a new version is available in AWS Marketplace, launch a new stack with it and move across:

1.  Copy the recordings from the old server, as shown in **Download recordings over SSH**.
2.  To keep your existing meetings and guest links, copy /var/lib/meetrix-portal/meetings.json from the old server to the same path on the new one. It is readable by root only, so use sudo on both sides, then run **sudo systemctl restart meetrix-portal** on the new server.
3.  Point both A records at the new PublicIp. The certificate is issued automatically, or run **sudo meetrix-cert**.
4.  The new server generates its own API key and secret. Update any integration with the values from the new ~/plugnmeet-credentials.txt.

Once you've checked the new server, remove the old stack.

## Troubleshoot

If you face vCPU quota limits, request an increase: [How to increase AWS quota](https://meetrix.io/blogs/increase-aws-vcpu-quota/).

![CloudFormation event showing CREATE\_FAILED with a VcpuLimitExceeded error](https://meetrix.io/blog-images/paas-dev-guides/plugnmeet/plugnmeet-10.png)

If you face _insufficient capacity_ errors while creating the stack, try another region or time.

![CloudFormation event showing CREATE\_FAILED with an InsufficientInstanceCapacity error](https://meetrix.io/blog-images/paas-dev-guides/plugnmeet/plugnmeet-11.png)

If the page shows **503 Service Unavailable**, HAProxy is running but the service behind it is not answering. Right after launch, wait a few minutes and retry. Otherwise check the services and logs as shown above.

If the browser shows a certificate warning, or does not ask for camera and microphone access, the Let's Encrypt certificate has not been issued yet. Check that your domain resolves to the PublicIp, then run **sudo meetrix-cert**, which tells you what is missing.

If participants join but see or hear nobody, check that the UDP range in **Ports the stack opens** is still open in the security group. If only participants on a strict office or hotel network are affected, their network probably blocks UDP, and they connect through TURN over TLS on turn.<your domain>. That needs the turn A record and a certificate that covers it, so check the names on the certificate:

```bash
sudo openssl x509 -in /etc/letsencrypt/live/<your domain>/fullchain.pem -noout -ext subjectAltName
```

If turn.<your domain> is not listed, create its A record and run **sudo meetrix-cert**. Our [WebRTC troubleshooting guide](https://meetrix.io/blogs/debugging-webrtc-applications/) shows how to inspect a call from the browser side.

If a recording does not start or never appears in the recordings folder, check that the recorder is running and read its log:

```bash
systemctl is-active plugnmeet-recorder

sudo journalctl -u plugnmeet-recorder -n 100
```

Check whether the instance storage is full. Log into the server and run:

```bash
df -h
```

![df -h output showing usage of the root filesystem](https://meetrix.io/blog-images/paas-dev-guides/plugnmeet/plugnmeet-13.png)

If the root volume is between 90-100%, move old recordings off the server or [resize the EBS volume](https://docs.aws.amazon.com/ebs/latest/userguide/requesting-ebs-volume-modifications.html), then reboot and restart the services.

## Conclusion

The Meetrix LiveKit Pro Deployment Guide helps you run recorded video meetings, virtual classrooms and webinars in your AWS environment, on your own domain, with no per-user fees and your recordings on your own disk. Whether you're teaching online classes, running training sessions or holding telehealth calls, this guide provides step-by-step instructions for a secure setup. See the [LiveKit Pro store page](https://meetrix.io/store/livekit-pro/) for what the Meetrix image includes. If you would rather build a LiveKit server by hand, see [how to self-host LiveKit on AWS](https://meetrix.io/blogs/self-host-livekit-aws/). If you are comparing recording stacks, our [Jitsi Meet with recordings developer guide](https://meetrix.io/blogs/setup-jitsi-meet-with-recordings-developer-guide/) covers the Jitsi route, and our roundup of [LiveKit alternatives](https://meetrix.io/blogs/livekit-alternatives/) takes a wider look at the field.

## Technical Support

Reach out to Meetrix Support ([aws@meetrix.io](mailto:aws@meetrix.io)) for assistance with LiveKit Pro issues.

## Frequently Asked Questions

What is LiveKit Pro?

LiveKit Pro is a self-hosted video conferencing platform from Meetrix, built on open-source plugNmeet and the LiveKit WebRTC media server. It runs on a single EC2 instance under your own domain, with cloud recording, a collaborative whiteboard, shared notes, polls, breakout rooms, a waiting room and RTMP streaming. On AWS Marketplace it is listed as LiveKit Based Video Conferencing with Recording, Whiteboard and Polls.

How is LiveKit Pro different from LiveKit Lite?

LiveKit Lite is for meetings only: camera, microphone, screen sharing and chat, with nothing recorded, on a small instance. LiveKit Pro adds cloud recording and the plugNmeet collaboration tools (whiteboard, shared notes, polls, breakout rooms, waiting room and streaming), so it needs a larger instance. See the [LiveKit Lite developer guide](/blogs/livekit-lite-developer-guide/) if you don't need recordings.

Why do the camera and microphone not work?

Browsers only allow camera and microphone access on a secure HTTPS page. Open LiveKit Pro on your domain, such as https://meet.example.com, after the Let's Encrypt certificate has been issued. If the browser shows a certificate warning, the certificate is not there yet: check that your A record points at the server, then wait up to 10 minutes or run sudo meetrix-cert.

Do guests need an account or an app?

No. Guests open the guest link in a modern browser, enter their name and join. Only the admin signs in, with the AdminUsername and AdminPassword set when the stack was created. Guests who arrive before the meeting starts wait and join automatically when the host starts it, and if the waiting room is on, the host admits them.

Where are recordings stored, and which instance type do I need?

Recordings are saved as MP4 files on the server's own disk, under /opt/plugNmeet/recording\_files/node\_01/<meeting id>/. Nothing is sent to third-party storage, and nothing is deleted automatically. One 1080p recording uses about 1.5 vCPU, so the default c6i.large suits occasional recording, and c6i.xlarge or larger suits teams that record often.

Why does LiveKit Pro need a second DNS record for turn.<your domain>?

The turn. name carries TURN over TLS on port 443, which keeps calls working for participants on office, hotel or school networks that block UDP. Meetings work without it, but those participants cannot connect. Point both A records at the Elastic IP and the certificate covers both names automatically.

How do I get technical support?

Reach out to Meetrix Support at [aws@meetrix.io](mailto:aws@meetrix.io) for assistance with LiveKit Pro issues.

## Ready to Deploy Your Own LiveKit Pro?

Get started in minutes with our pre-configured AMI and host recorded video meetings, classes and webinars on your own domain.

[Deploy LiveKit Pro from AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-m3cuujz3dtnak)

Meetrix Store

LiveKit Pro

Video meetings with cloud recording, whiteboard and polls, self-hosted

[Deploy it](https://meetrix.io/store/livekit-pro/)

Meetrix Store New

Deploy what this guide covers, pre-configured.

-    [LiveKit Pro Video meetings with cloud recording, whiteboard and polls, self-hosted](https://meetrix.io/store/livekit-pro/)
-    [LiveKit Lite Private video meetings on your own domain, no recording](https://meetrix.io/store/livekit-lite/)
-    [Jitsi Meet Self-hosted video calls for 50 to 500 users](https://meetrix.io/store/jitsi-meet/)
-    [RustDesk Remote desktop AMI, a TeamViewer alternative](https://meetrix.io/store/rustdesk/)
-    [Coturn TURN/STUN for WebRTC, no per-minute relay fees](https://meetrix.io/store/coturn/)
-    [OpenVPN Encrypted remote access, no per-user fees](https://meetrix.io/store/openvpn/)

[Browse all products](https://meetrix.io/store/)
