Configuration

MikroMeet works out of the box with zero configuration, but you can customize it for production deployments.

Configuration Files

MikroMeet uses two configuration approaches:

1. Frontend Config - config.json in the extracted app archive (runtime)
2. Server Config - .env file (environment variables)

Frontend Configuration

Edit config.json in the extracted app archive to configure the client. mikromeet.config.json remains available as a legacy alias:

{
  "apiUrl": "wss://api.yourdomain.com/ws",
  "iceServers": [
    { "urls": "stun:stun.cloudflare.com:3478" },
    {
      "urls": "turn:turn.yourdomain.com:3478",
      "username": "your-username",
      "credential": "your-password"
    }
  ]
}

Options

apiUrl (required)

WebSocket URL for the signaling server.

• Local testing: ws://127.0.0.1:3000/ws
• Production (HTTPS): wss://yourdomain.com/ws
• Separate API server: wss://api.yourdomain.com/ws

Tip

Use ws:// for HTTP and wss:// for HTTPS. Mismatched protocols will fail.

iceServers (optional)

Array of STUN/TURN servers for WebRTC connectivity.

Default (if omitted):

[{ "urls": "stun:stun.cloudflare.com:3478" }]

With TURN (recommended for production):

[
  { "urls": "stun:stun.cloudflare.com:3478" },
  {
    "urls": "turn:turn.yourdomain.com:3478",
    "username": "mikromeet",
    "credential": "your-secure-password"
  }
]

Server Configuration

Create a .env file in the project root:

# Server port
MIKROMEET_PORT=3000

# HTTPS (optional)
USE_HTTPS=false
SSL_CERT_PATH=/path/to/cert.pem
SSL_KEY_PATH=/path/to/key.pem

# TURN server (recommended for production)
TURN_SERVER_URL=turn:turn.yourdomain.com:3478
TURN_SERVER_USERNAME=mikromeet
TURN_SERVER_CREDENTIAL=your-password

# Room management
MAX_LATENT_ROOMS=10
LATENT_ROOM_MAX_AGE_HOURS=24

Server Options

MIKROMEET_PORT

Server port (default: 3000). PORT is also supported as a generic fallback.

MIKROMEET_PORT=8080

USE_HTTPS

Enable HTTPS server (default: false)

USE_HTTPS=true
SSL_CERT_PATH=/etc/letsencrypt/live/yourdomain.com/fullchain.pem
SSL_KEY_PATH=/etc/letsencrypt/live/yourdomain.com/privkey.pem

Caution

When USE_HTTPS=true, both certificate paths are required.

TURN Server

Configure TURN for users behind strict NAT/firewalls:

TURN_SERVER_URL=turn:turn.example.com:3478
TURN_SERVER_USERNAME=username
TURN_SERVER_CREDENTIAL=password

Tip

When the frontend can reach the MikroMeet API, configure TURN on the server and the app will load ICE servers from /config. Static-only deployments can still provide iceServers directly in config.json.

Room Management

Control room lifecycle:

MAX_LATENT_ROOMS=20           # Max pre-created empty rooms
LATENT_ROOM_MAX_AGE_HOURS=48  # Hours before cleanup

HTTPS Setup

HTTPS is required for:

• Camera/microphone access in browsers
• Production deployments
• Secure WebSocket connections (WSS)

Option 1: Let’s Encrypt (Recommended)

# Install Certbot
sudo apt install certbot

# Get certificate
sudo certbot certonly --standalone -d yourdomain.com

# Configure MikroMeet
USE_HTTPS=true
SSL_CERT_PATH=/etc/letsencrypt/live/yourdomain.com/fullchain.pem
SSL_KEY_PATH=/etc/letsencrypt/live/yourdomain.com/privkey.pem

Option 2: Reverse Proxy (Easier)

Use Caddy or Nginx for SSL termination. Run MikroMeet on HTTP internally.

Caddy Example (auto-HTTPS):

yourdomain.com {
    reverse_proxy 127.0.0.1:3000
}

Nginx Example:

server {
    listen 443 ssl http2;
    server_name yourdomain.com;

    ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;

    # WebSocket upgrade for /ws
    location /ws {
        proxy_pass http://127.0.0.1:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }

    # Proxy other requests
    location / {
        proxy_pass http://127.0.0.1:3000;
    }
}

TURN Server Setup

TURN servers ensure connectivity for users behind strict firewalls.

Self-Hosted with Coturn

Install and configure Coturn:

# Install (Ubuntu/Debian)
sudo apt install coturn

# Edit /etc/turnserver.conf
listening-port=3478
realm=yourdomain.com
server-name=turn.yourdomain.com
lt-cred-mech
user=mikromeet:your-secure-password
fingerprint

# Start Coturn
sudo systemctl enable coturn
sudo systemctl start coturn

# Allow firewall
sudo ufw allow 3478/tcp
sudo ufw allow 3478/udp
sudo ufw allow 49152:65535/udp

Update both configs:

Server (.env):

TURN_SERVER_URL=turn:turn.yourdomain.com:3478
TURN_SERVER_USERNAME=mikromeet
TURN_SERVER_CREDENTIAL=your-secure-password

Frontend (config.json):

{
  "iceServers": [
    { "urls": "stun:stun.cloudflare.com:3478" },
    {
      "urls": "turn:turn.yourdomain.com:3478",
      "username": "mikromeet",
      "credential": "your-secure-password"
    }
  ]
}

Managed TURN Services

Alternatively, use a managed service:

• Twilio - Get credentials
• Metered.ca - Free tier available
• Xirsys - WebRTC infrastructure

Environment Examples

Local Testing

.env

MIKROMEET_PORT=3000

config.json

{
  "apiUrl": "ws://127.0.0.1:3000/ws"
}

Production

.env

MIKROMEET_PORT=3000
TURN_SERVER_URL=turn:turn.yourdomain.com:3478
TURN_SERVER_USERNAME=mikromeet
TURN_SERVER_CREDENTIAL=strong-password
MAX_LATENT_ROOMS=20

config.json

{
  "apiUrl": "wss://yourdomain.com/ws",
  "iceServers": [
    { "urls": "stun:stun.cloudflare.com:3478" },
    {
      "urls": "turn:turn.yourdomain.com:3478",
      "username": "mikromeet",
      "credential": "strong-password"
    }
  ]
}

Next Steps

• Deployment Guide - Deploy to production
• Server Options - All configuration options