MiroTalk Self-Hosted Video

Prerequisites

1 Deploy MiroTalk P2P with Docker

Run the following command on your server. Replace your-strong-random-key with a strong secret — you will enter this key into Tymeslot later:

docker run -d \
  --name mirotalk \
  -p 3000:3000 \
  -e API_KEY_SECRET=your-strong-random-key \
  --restart unless-stopped \
  mirotalk/p2p:latest

To generate a secure API key:

openssl rand -hex 32

Expected result: after the container starts, open http://your-server:3000 in a browser — you should see the MiroTalk P2P landing page.

2 Set Up a Reverse Proxy with HTTPS

Browsers require HTTPS to access the camera and microphone — WebRTC will not work over plain HTTP. Set up a reverse proxy in front of MiroTalk's port 3000. Caddy handles TLS certificates automatically:

meet.yourdomain.com {
    reverse_proxy localhost:3000
}

After reloading Caddy, open https://meet.yourdomain.com — the MiroTalk landing page should load over a secure connection.

3 Test MiroTalk Manually

Verify MiroTalk works independently before connecting it to Tymeslot:

1. Navigate to https://meet.yourdomain.com
2. Enter any room name and click Join
3. The browser should prompt for camera and microphone permissions
4. Grant permissions — the video room should open

If the room loads and the camera permission prompt appears, MiroTalk is working correctly. Move on to Step 4.

4 Connect MiroTalk in Tymeslot

Now register your MiroTalk instance with Tymeslot:

1. Navigate to Dashboard → Settings → Integrations
2. Find the MiroTalk row and click Configure
3. Enter your MiroTalk URL — for example, https://meet.yourdomain.com
4. Enter the API key you set in API_KEY_SECRET
5. Click Save

Expected result: the MiroTalk row shows a connected status. Tymeslot will now generate room links using your instance for every booking.

5 Enable MiroTalk on Meeting Types

MiroTalk is enabled per meeting type. Repeat for each meeting type where you want self-hosted video:

1. Navigate to Dashboard → Meeting Types
2. Click Edit on the meeting type you want to update
3. Go to the Location tab
4. Select MiroTalk from the location options
5. Click Save

Expected result: each new booking for this meeting type will include a unique MiroTalk room URL. No manual room management is required — Tymeslot generates a fresh room link per booking.

Resource Requirements

Because MiroTalk P2P is peer-to-peer, your server only handles WebRTC signaling — it does not relay video or audio streams. Signaling traffic is minimal. A basic VPS with 1 GB RAM comfortably handles hundreds of concurrent meetings. Video bandwidth goes directly between participants' browsers, not through your server. Resource requirements only increase significantly if you later add a TURN server for corporate network traversal.

TURN Server Setup (Optional)

Peer-to-peer WebRTC works for most home and mobile connections. However, participants on strict corporate or institutional networks may have their P2P connections blocked by firewalls or NAT. A TURN server relays media traffic for those users.

Coturn is the standard open-source TURN server:

apt install coturn
# Edit /etc/turnserver.conf — set your domain and credentials
# Then restart: systemctl restart coturn

After installing Coturn, add the TURN server credentials to MiroTalk's environment config and restart the container.

❓ Frequently Asked Questions

Verification Checklist

• A MiroTalk room URL appears under Location in Dashboard → Meetings → meeting detail
• The booking confirmation email contains the same MiroTalk room link
• Opening the room link in a browser loads the MiroTalk P2P interface and prompts for camera and microphone permissions
• Joining the room from two separate browser tabs shows live video in both