Skip to content
Klutch.sh Docs

Deploying a Jitsi App

Introduction

Jitsi Meet is an open-source video conferencing platform composed of web, signaling, and media components. Deploying Jitsi with a Dockerfile on Klutch.sh gives you reproducible builds, managed secrets, and persistent storage for configs and recordings—all managed from klutch.sh/app. This guide covers installation, repository prep, a production-ready Dockerfile, deployment steps, Nixpacks overrides, and best practices for reliable meetings.

Prerequisites

  • A Klutch.sh account (create one)
  • A GitHub repository containing your Jitsi deployment files (GitHub is the only supported git source)
  • Docker familiarity and knowledge of Jitsi components (web, prosody, jicofo, jvb)
  • Domain configured for your Jitsi host
  • Storage for configs and optional recordings

Review platform setup in the Quick Start.

Architecture and ports

  • Jitsi web serves HTTP; set the internal container port to 8080 in Klutch.sh.
  • JVB (media bridge) typically uses UDP and TCP 4443; for Klutch.sh, use TCP apps for JVB signaling on internal port 4443, externally mapped to 8000.
  • Prosody/Jicofo run internally; expose only what you need via HTTP/TCP apps.
  • Persistent storage is recommended for configuration, letsencrypt, and recordings.

Repository layout

jitsi/
├── web/                    # Jitsi web assets/config
├── prosody/                # Prosody configs
├── jicofo/                 # Jicofo configs
├── jvb/                    # JVB configs
├── recordings/             # Optional recordings (mount as volume)
├── Dockerfile              # Must be at repo root for auto-detection
└── .env.example            # Template only; no secrets

Keep secrets out of Git; store them in Klutch.sh environment variables.

Installation (local) and starter commands

Quick local test (monolithic container):

Terminal window
docker run --rm -p 8080:8080 -p 4443:4443 \
  -e PUBLIC_URL=https://meet.example.com \
  jitsi/web:stable-9044

Optional helper start.sh for portability and Nixpacks fallback:

#!/usr/bin/env bash
set -euo pipefail
PUBLIC_URL=${PUBLIC_URL:-https://example-app.klutch.sh}
exec /init

Make it executable with chmod +x start.sh.

Dockerfile for Jitsi (production-ready)

Place this Dockerfile at the repo root; Klutch.sh auto-detects it (no Docker selection in the UI):

FROM jitsi/web:stable-9044


WORKDIR /app


# Copy custom configs (optional)
COPY web/ /config/web/
COPY prosody/ /config/prosody/
COPY jicofo/ /config/jicofo/
COPY jvb/ /config/jvb/


EXPOSE 8080
CMD ["/init"]

Notes:

  • Pin the Jitsi image tag to match your Jibri or other companion services.
  • If you split services, create separate Dockerfiles/apps per component, each with its port.

Environment variables (Klutch.sh)

Set these in the Klutch.sh app settings (Secrets tab) before deploying:

  • PUBLIC_URL=https://example-app.klutch.sh
  • XMPP_DOMAIN=meet.example.com
  • XMPP_AUTH_DOMAIN=auth.meet.example.com
  • XMPP_MUC_DOMAIN=conference.meet.example.com
  • XMPP_INTERNAL_MUC_DOMAIN=internal.auth.meet.example.com
  • JICOFO_COMPONENT_SECRET=<strong-secret>
  • JICOFO_AUTH_USER=focus
  • JICOFO_AUTH_PASSWORD=<strong-password>
  • JVB_AUTH_USER=jvb
  • JVB_AUTH_PASSWORD=<strong-password>
  • JVB_BREWERY_MUC=jvbbrewery
  • JVB_PORT=4443
  • PORT=8080

If you deploy without the Dockerfile and need Nixpacks overrides:

  • NIXPACKS_BUILD_CMD="echo Jitsi uses prebuilt images"
  • NIXPACKS_START_CMD=/init
  • NIXPACKS_JDK_VERSION=11

These keep Jitsi compatible with Nixpacks defaults when a Dockerfile is absent.

Attach persistent volumes

In Klutch.sh storage settings, add mount paths and sizes (no names required):

  • /config — for web, prosody, jicofo, and jvb configs.
  • /recordings — optional if you store recordings locally.

Ensure these paths are writable inside the container.

Deploy Jitsi on Klutch.sh (Dockerfile workflow)

  1. Push your repository (with the Dockerfile at the root) to GitHub.
  2. Open klutch.sh/app, create a project, and add an app.
  1. Connect the GitHub repository; Klutch.sh automatically detects the Dockerfile.
  2. Choose HTTP traffic for the web component and set the internal port to 8080.
  3. Add the environment variables above (XMPP domains, Jicofo/JVB credentials, and any NIXPACKS_* overrides if you temporarily deploy without the Dockerfile).
  4. Attach persistent volumes for /config (and /recordings if used), selecting sizes that fit your retention policy.
  5. Deploy. Your Jitsi web will be reachable at https://example-app.klutch.sh; attach a custom domain if desired.

For JVB TCP signaling, create a separate Klutch.sh TCP app with internal port 4443 and connect to example-app.klutch.sh:8000.

Health checks and production tips

  • Add a /about/health probe (or similar) via your reverse proxy for uptime monitoring.
  • Enforce HTTPS at the edge; forward HTTP to port 8080 internally.
  • Keep image tags pinned across Jitsi, Jicofo, JVB, and Jibri for compatibility.
  • Monitor disk usage on /config and /recordings; resize volumes before they fill.
  • Use strong secrets for XMPP users and rotate them regularly.

Jitsi on Klutch.sh combines reproducible Docker builds with managed secrets, persistent configuration storage, and flexible HTTP/TCP routing. With the Dockerfile at the repo root and ports set to 8080 for web (8000 externally for any TCP companions), you can host secure, scalable video meetings without extra YAML or workflow overhead.