<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Video-Conferencing – Serverküche</title><link>https://serverkueche.de/en/tags/video-conferencing/</link><description>Video-Conferencing – Neueste Beiträge von Serverküche</description><generator>Hugo</generator><language>en-US</language><managingEditor>feedback@serverkueche.de (Serverküche)</managingEditor><webMaster>feedback@serverkueche.de (Serverküche)</webMaster><copyright>2026 Serverküche</copyright><lastBuildDate>Sat, 14 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://serverkueche.de/en/tags/video-conferencing/index.xml" rel="self" type="application/rss+xml"/><item><title>Jitsi Meet: Your Own Video Conferences Without Zoom</title><link>https://serverkueche.de/en/tutorials/jitsi-meet-video-conferences/</link><pubDate>Sat, 14 Nov 2026 00:00:00 +0000</pubDate><author>feedback@serverkueche.de (Serverküche)</author><guid>https://serverkueche.de/en/tutorials/jitsi-meet-video-conferences/</guid><description>Jitsi Meet in four containers behind Traefik: a moderator login instead of open rooms, the UDP port everything fails on, and what the video really costs.</description><content:encoded><![CDATA[<p>A video conference on your own server is the point where self-hosting stops being comfortable: four
containers, one UDP port and a handful of traps that all surface only once the first guest cannot
hear anybody.</p>
<h2 id="what-are-we-building">What are we building?</h2>
<p>We run Jitsi Meet stable-11248-3 as four containers behind Traefik: the web interface, the XMPP
server, the conference control and the video bridge. At the end you open a room in the browser, and
nobody but you can start a conference. Guests only get in once you are there as the moderator.</p>
<p>Deliberately left out: dial-in by phone (Jigasi), recording (Jibri) and Etherpad. Each of those is
a service of its own with its own requirements; anyone adding them builds on the stack set up here.</p>
<div class="not-prose my-6 rounded-lg border-l-4 p-4 border-amber-400 bg-amber-50 dark:border-amber-700 dark:bg-amber-900/20">
  <p class="mb-1 flex items-center gap-2 font-semibold text-slate-900 dark:text-white">
    <span aria-hidden="true">⚠️</span>One port that does not go through the proxy
  </p>
  <div class="prose-kitchen text-sm">Traefik only takes care of the web interface. <strong>Audio and video go past it</strong>, straight to
UDP 10000 on the server. If that port is closed, Jitsi loads perfectly, everybody sees the
participant list, and nobody hears anyone. This is by far the most common reason a self-hosted
Jitsi instance &ldquo;does not work&rdquo;.</div>
</div>
<h2 id="requirements">Requirements</h2>
<ul>
<li>Debian 13 with Docker and the <a href="/en/tutorials/docker-compose-basics/">Compose basics</a></li>
<li>A running <a href="/en/tutorials/traefik-reverse-proxy/">reverse proxy with Traefik</a> and a
<a href="/en/tutorials/connect-domain-to-server/">domain connected to the server</a></li>
<li>UDP port 10000 reachable from outside, both in the
<a href="/en/tutorials/firewall-ufw-setup/">UFW firewall</a> and as a policy of its own in the
<a href="/en/tutorials/netcup-firewall-setup/">netcup firewall</a>; a web template with 80/443 is not
enough for it</li>
<li>The public IPv4 address of your server; you enter it by hand in a moment</li>
</ul>
<div class="not-prose my-6 overflow-hidden rounded-xl border border-paprika-200 bg-paprika-50 dark:border-paprika-800 dark:bg-paprika-900/20"
     data-track-content data-content-name="Affiliate-Box · /en/tutorials/jitsi-meet-video-conferences/" data-content-piece="VPS 2000 G12.5">
  <div class="flex items-center justify-between border-b border-paprika-200 bg-paprika-100 px-4 py-1.5 text-xs font-semibold uppercase tracking-wide text-paprika-700 dark:border-paprika-800 dark:bg-paprika-900/40 dark:text-paprika-300">
    <span>🍳 Recommendation</span>
    <span title="Links marked with * are affiliate links.">Ad</span>
  </div>
  <div class="flex flex-col gap-4 p-4 sm:flex-row sm:items-center sm:justify-between">
    <div>
      <p class="text-lg font-bold text-slate-900 dark:text-white">VPS 2000 G12.5</p>
      <p class="mt-1 text-sm text-slate-600 dark:text-slate-300">8 vCores · 16 GB RAM · 256 GB SSD</p>
      <p class="mt-1 text-sm font-semibold text-paprika-700 dark:text-paprika-400">from €26.92/month</p>
      <p class="mt-2 text-sm text-slate-600 dark:text-slate-400">Idle, the stack uses just under 400 MB. The demand grows with every participant though – in CPU, not in memory.</p>
    </div>
    <a href="https://www.netcup.com/en/server/vps/vps-2000-g12.5-iv-24m-eu?ref=44083#vps-2000-g12.5-iv-12m-eu" rel="sponsored noopener" target="_blank"
   data-track-event="Affiliate|netcup: Affiliate-Box|VPS 2000 G12.5 · {page}"
   class="inline-flex shrink-0 items-center justify-center rounded-lg bg-paprika-600 px-5 py-2.5 font-semibold text-white transition-colors hover:bg-paprika-700">
  Go to netcup →
</a>

  </div><div class="px-4 pb-4"><div class="not-prose my-3 rounded-lg border border-herb-500/40 bg-herb-50 px-3 py-2 text-sm text-slate-700 dark:bg-herb-900/20 dark:text-slate-200"
     data-voucher-api="vps-2000" data-voucher-msg-empty="No code is available for this plan right now – use the €5.95 code." data-voucher-msg-limit="No more codes today – use the €5.95 code or try again tomorrow." data-voucher-msg-error="The code couldn&#39;t be fetched right now – use the €5.95 code."
     data-voucher-hint="Empty the cart first – the code adds the server itself.">
  <p class="flex flex-wrap items-center gap-x-2 gap-y-1"><span>💶 <span class="font-semibold">1 month free</span>:</span>
    <button type="button" data-voucher-reveal data-copy-title="Click to copy"
            class="cursor-pointer rounded bg-white px-2 py-0.5 font-mono text-sm font-semibold text-herb-800 hover:ring-2 hover:ring-herb-500/40 dark:bg-slate-800 dark:text-herb-400">Show code</button>
    <button type="button" data-voucher-next hidden
            class="rounded border border-herb-500/40 px-2 py-0.5 text-xs text-herb-800 hover:bg-white dark:text-herb-400 dark:hover:bg-slate-800">another code</button>
  </p><p class="mt-1 text-xs text-slate-500 dark:text-slate-400" data-voucher-hint-target>
    Single use, valid for VPS 2000 G12.5.
    <a href="https://www.netcup.com/en/checkout/cart?ref=44083" rel="sponsored noopener" target="_blank"
       data-track-event="Affiliate|netcup: Gutschein einlösen|VPS 2000 G12.5 · {page}"
       class="font-medium text-herb-800 underline underline-offset-2 hover:text-herb-900 dark:text-herb-400">Redeem in the cart →</a>
  </p><p class="mt-2 flex flex-wrap items-center gap-x-2 gap-y-1 border-t border-herb-500/30 pt-2">
    <span>💶 <span class="font-semibold">€5.95 voucher</span> for new netcup customers:</span>
    <button type="button" data-voucher-code data-track-voucher="36nc17844976032"
            title="Click to copy" class="cursor-pointer rounded bg-white px-2 py-0.5 font-mono text-sm font-semibold text-herb-800 hover:ring-2 hover:ring-herb-500/40 dark:bg-slate-800 dark:text-herb-400">36nc17844976032</button>
    <span class="text-xs text-slate-500 dark:text-slate-400">always valid · not for domains or VPS Lite</span>
  </p><p class="mt-1 text-xs"><a href="/en/netcup-voucher/" class="font-medium text-herb-800 underline underline-offset-2 hover:text-herb-900 dark:text-herb-400">All netcup vouchers →</a></p>
</div></div>
</div>

<h2 id="step-by-step">Step by step</h2>
<h3 id="step-1-why-there-are-four-containers">Step 1: Why there are four containers</h3>
<p>Jitsi is a group of several services. Four parts, four jobs:</p>
<div class="sk-code">
  <span class="sk-code-head">Ausgabe</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">web      nginx + the web interface        HTTP  – behind Traefik
</span></span><span class="line"><span class="cl">prosody  XMPP server, accounts and rooms  internal
</span></span><span class="line"><span class="cl">jicofo   conference control, distributes  internal
</span></span><span class="line"><span class="cl">jvb      video bridge – audio and video   UDP 10000 – straight at the server</span></span></code></pre></div>
</div>
<p><code>prosody</code> holds the user accounts and the signalling; your browser talks to it over a WebSocket.
<code>jicofo</code> decides who is a moderator and which bridge a conference gets. <code>jvb</code> is the video
bridge: it takes in the audio and video streams of all participants and passes them on.</p>
<p>The most important part of that is the last line. The video bridge does not sit behind Traefik. WebRTC
needs UDP with low latency; an HTTP proxy has no business there. Traefik serves the web interface
over 443, and in parallel your browser sends audio and video to UDP 10000 at the same address.</p>
<h3 id="step-2-the-images-no-longer-come-from-docker-hub">Step 2: The images no longer come from Docker Hub</h3>
<p>Copy a guide that uses the Docker Hub images and you fetch a version several months old:</p>
<div class="sk-code">
  <span class="sk-code-head">Terminal</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="c1"># On Docker Hub jitsi/web has stopped – the last stable tag is from June.</span>
</span></span><span class="line"><span class="cl"><span class="c1"># The only maintained source now is the GitHub registry:</span>
</span></span><span class="line"><span class="cl">docker pull ghcr.io/jitsi/web:stable-11248-3</span></span></code></pre></div>
</div>
<p>Jitsi now publishes its images under <code>ghcr.io/jitsi</code>. On Docker Hub the series ends in June
2026 at <code>stable-11031</code>; since then <code>stable-11146</code> (August) and <code>stable-11248</code> (September) have been
released, both on GitHub only. Fixes within a release get a suffix: <code>stable-11248-3</code> is the third
revision of <code>stable-11248</code>. The version is not in the image name but in the tag, and it is the same for all four
containers. Never mix versions: <code>jicofo</code> and <code>jvb</code> speak a protocol that changes between releases.</p>
<h3 id="step-3-the-configuration">Step 3: The configuration</h3>
<p>Jitsi is configured entirely through environment variables. Create the folder and generate the three
secrets first:</p>
<div class="sk-code">
  <span class="sk-code-head">Terminal</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir -p /opt/jitsi <span class="o">&amp;&amp;</span> <span class="nb">cd</span> /opt/jitsi
</span></span><span class="line"><span class="cl">openssl rand -hex <span class="m">16</span>   <span class="c1"># run three times – for JICOFO_AUTH_PASSWORD,</span>
</span></span><span class="line"><span class="cl">                       <span class="c1"># JVB_AUTH_PASSWORD and JICOFO_COMPONENT_SECRET</span></span></span></code></pre></div>
</div>
<p>Those three values are the internal passwords <code>jicofo</code> and <code>jvb</code> use to log in to <code>prosody</code>. They go
into the <code>.env</code>:</p>
<div class="sk-code">
  <span class="sk-code-head">INI</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-ini" data-lang="ini"><span class="line"><span class="cl"><span class="c1"># /opt/jitsi/.env</span>
</span></span><span class="line"><span class="cl"><span class="na">PUBLIC_URL</span><span class="o">=</span><span class="s">https://YOUR_DOMAIN</span>
</span></span><span class="line"><span class="cl"><span class="na">TZ</span><span class="o">=</span><span class="s">Europe/Berlin</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="na">XMPP_DOMAIN</span><span class="o">=</span><span class="s">meet.jitsi</span>
</span></span><span class="line"><span class="cl"><span class="na">XMPP_AUTH_DOMAIN</span><span class="o">=</span><span class="s">auth.meet.jitsi</span>
</span></span><span class="line"><span class="cl"><span class="na">XMPP_GUEST_DOMAIN</span><span class="o">=</span><span class="s">guest.meet.jitsi</span>
</span></span><span class="line"><span class="cl"><span class="na">XMPP_MUC_DOMAIN</span><span class="o">=</span><span class="s">muc.meet.jitsi</span>
</span></span><span class="line"><span class="cl"><span class="na">XMPP_INTERNAL_MUC_DOMAIN</span><span class="o">=</span><span class="s">internal-muc.meet.jitsi</span>
</span></span><span class="line"><span class="cl"><span class="na">XMPP_SERVER</span><span class="o">=</span><span class="s">xmpp.meet.jitsi</span>
</span></span><span class="line"><span class="cl"><span class="na">XMPP_BOSH_URL_BASE</span><span class="o">=</span><span class="s">http://xmpp.meet.jitsi:5280</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="na">JVB_BREWERY_MUC</span><span class="o">=</span><span class="s">jvbbrewery</span>
</span></span><span class="line"><span class="cl"><span class="na">JICOFO_AUTH_USER</span><span class="o">=</span><span class="s">focus</span>
</span></span><span class="line"><span class="cl"><span class="na">JVB_AUTH_USER</span><span class="o">=</span><span class="s">jvb</span>
</span></span><span class="line"><span class="cl"><span class="na">JVB_PORT</span><span class="o">=</span><span class="s">10000</span>
</span></span><span class="line"><span class="cl"><span class="na">JVB_ADVERTISE_IPS</span><span class="o">=</span><span class="s">YOUR_SERVER_IP</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="na">JICOFO_AUTH_PASSWORD</span><span class="o">=</span><span class="s">YOUR_FIRST_SECRET</span>
</span></span><span class="line"><span class="cl"><span class="na">JVB_AUTH_PASSWORD</span><span class="o">=</span><span class="s">YOUR_SECOND_SECRET</span>
</span></span><span class="line"><span class="cl"><span class="na">JICOFO_COMPONENT_SECRET</span><span class="o">=</span><span class="s">YOUR_THIRD_SECRET</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="na">ENABLE_AUTH</span><span class="o">=</span><span class="s">1</span>
</span></span><span class="line"><span class="cl"><span class="na">ENABLE_GUESTS</span><span class="o">=</span><span class="s">1</span>
</span></span><span class="line"><span class="cl"><span class="na">AUTH_TYPE</span><span class="o">=</span><span class="s">internal</span></span></span></code></pre></div>
</div>
<p>Two blocks deserve an explanation.</p>
<p>The <code>meet.jitsi</code> domains are purely internal and have nothing to do with your real domain. They
exist only between the containers; you do not have to enter anything in DNS for them. Leave them
unchanged. The default values are identical across every Jitsi guide out there, and that helps when
you are searching for a problem.</p>
<p><code>JVB_ADVERTISE_IPS</code> is the public IPv4 address of your server, and it is mandatory. Left to
itself the video bridge only knows its container address (<code>172.x.x.x</code>) and would announce exactly
that to every browser, an address nobody on the internet can reach. Jitsi does try to find out the
real address through a STUN service, but you cannot rely on it: after start-up the bridge&rsquo;s log
says <code>stunDiscoveryFailed=true</code>. Whether the variable takes effect is shown by a different line,
which you look at in step 6.</p>
<div class="not-prose my-6 rounded-lg border-l-4 p-4 border-amber-400 bg-amber-50 dark:border-amber-700 dark:bg-amber-900/20">
  <p class="mb-1 flex items-center gap-2 font-semibold text-slate-900 dark:text-white">
    <span aria-hidden="true">⚠️</span>The .env is the backup
  </p>
  <div class="prose-kitchen text-sm">The three secrets exist only here. If the <code>.env</code> is lost, <code>jicofo</code> and <code>jvb</code> no longer get past
<code>prosody</code>, and the only way back is to set all three anew and recreate the containers. Put the file
on <code>chmod 600</code> and into your backup.</div>
</div>
<h3 id="step-4-the-stack">Step 4: The stack</h3>
<div class="sk-code">
  <span class="sk-code-head">YAML</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="c"># /opt/jitsi/compose.yaml</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">services</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">web</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">image</span><span class="p">:</span><span class="w"> </span><span class="l">ghcr.io/jitsi/web:stable-11248-3</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">container_name</span><span class="p">:</span><span class="w"> </span><span class="l">jitsi-web</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">restart</span><span class="p">:</span><span class="w"> </span><span class="l">unless-stopped</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">volumes</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">./config/web:/config:Z</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">environment</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">PUBLIC_URL</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">TZ</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">ENABLE_AUTH</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">ENABLE_GUESTS</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_AUTH_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_MUC_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_INTERNAL_MUC_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_BOSH_URL_BASE</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">DISABLE_HTTPS=1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">ENABLE_HTTP_REDIRECT=0</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">ENABLE_LETSENCRYPT=0</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">networks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">meet.jitsi</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">proxy</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">labels</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">traefik.enable=true</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">traefik.docker.network=proxy</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">traefik.http.routers.jitsi.rule=Host(`YOUR_DOMAIN`)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">traefik.http.routers.jitsi.entrypoints=websecure</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">traefik.http.routers.jitsi.tls.certresolver=le</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">traefik.http.services.jitsi.loadbalancer.server.port=8000</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">prosody</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">image</span><span class="p">:</span><span class="w"> </span><span class="l">ghcr.io/jitsi/prosody:stable-11248-3</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">container_name</span><span class="p">:</span><span class="w"> </span><span class="l">jitsi-prosody</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">restart</span><span class="p">:</span><span class="w"> </span><span class="l">unless-stopped</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">expose</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="s1">&#39;5222&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;5347&#39;</span><span class="p">,</span><span class="w"> </span><span class="s1">&#39;5280&#39;</span><span class="p">]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">volumes</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">./config/prosody/config:/config:Z</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">./config/prosody/prosody-plugins-custom:/prosody-plugins-custom:Z</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">./config/prosody/data:/var/lib/prosody:Z</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">environment</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">PUBLIC_URL</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">TZ</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">ENABLE_AUTH</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">ENABLE_GUESTS</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">AUTH_TYPE</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_AUTH_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_GUEST_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_MUC_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_INTERNAL_MUC_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JICOFO_AUTH_USER</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JICOFO_AUTH_PASSWORD</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JICOFO_COMPONENT_SECRET</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JVB_AUTH_USER</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JVB_AUTH_PASSWORD</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">networks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">meet.jitsi</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">        </span><span class="nt">aliases</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">          </span>- <span class="l">xmpp.meet.jitsi</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">jicofo</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">image</span><span class="p">:</span><span class="w"> </span><span class="l">ghcr.io/jitsi/jicofo:stable-11248-3</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">container_name</span><span class="p">:</span><span class="w"> </span><span class="l">jitsi-jicofo</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">restart</span><span class="p">:</span><span class="w"> </span><span class="l">unless-stopped</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">depends_on</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="l">prosody]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">volumes</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">./config/jicofo:/config:Z</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">environment</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">TZ</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">ENABLE_AUTH</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">AUTH_TYPE</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_AUTH_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_INTERNAL_MUC_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_MUC_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_SERVER</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JICOFO_AUTH_USER</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JICOFO_AUTH_PASSWORD</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JICOFO_COMPONENT_SECRET</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JVB_BREWERY_MUC</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">networks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">meet.jitsi</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">jvb</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">image</span><span class="p">:</span><span class="w"> </span><span class="l">ghcr.io/jitsi/jvb:stable-11248-3</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">container_name</span><span class="p">:</span><span class="w"> </span><span class="l">jitsi-jvb</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">restart</span><span class="p">:</span><span class="w"> </span><span class="l">unless-stopped</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">depends_on</span><span class="p">:</span><span class="w"> </span><span class="p">[</span><span class="l">prosody]</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">ports</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="s1">&#39;10000:10000/udp&#39;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">volumes</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">./config/jvb:/config:Z</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">environment</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">TZ</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">PUBLIC_URL</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_AUTH_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_INTERNAL_MUC_DOMAIN</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">XMPP_SERVER</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JVB_AUTH_USER</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JVB_AUTH_PASSWORD</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JVB_BREWERY_MUC</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JVB_PORT</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span>- <span class="l">JVB_ADVERTISE_IPS</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">networks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">      </span><span class="nt">meet.jitsi</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">networks</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">meet.jitsi</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">proxy</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="nt">external</span><span class="p">:</span><span class="w"> </span><span class="kc">true</span></span></span></code></pre></div>
</div>
<p>Three lines deserve an explanation:</p>
<ul>
<li><code>loadbalancer.server.port=8000</code>: The nginx inside the <code>web</code> container runs unprivileged and
therefore listens on 8000, not on 80. Enter 80 and Traefik answers <code>502 Bad Gateway</code> even
though all four containers are running.</li>
<li><code>DISABLE_HTTPS=1</code> and <code>ENABLE_LETSENCRYPT=0</code>: Jitsi ships its own certificate handling,
which we do not want. TLS is Traefik&rsquo;s job.</li>
<li><code>./config/prosody/data:/var/lib/prosody</code>: This is where the user accounts live. The official
template mounts the directory under <code>config/storage/prosody</code>; anyone putting the Compose file
together themselves easily forgets it. Then your moderator account is gone after the next
<code>docker compose down</code>.</li>
</ul>
<h3 id="step-5-create-the-directories-for-the-right-user">Step 5: Create the directories for the right user</h3>
<p>The containers run as the user <code>s6</code> with UID 1000, not as root. They write their generated
configuration into the mounted folders, and that only works if those belong to them:</p>
<div class="sk-code">
  <span class="sk-code-head">Terminal</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">mkdir -p /opt/jitsi/config/<span class="o">{</span>web,prosody/config,prosody/prosody-plugins-custom,prosody/data,jicofo,jvb<span class="o">}</span>
</span></span><span class="line"><span class="cl">chown -R 1000:1000 /opt/jitsi/config</span></span></code></pre></div>
</div>
<p>Skip the <code>chown</code> and the web container does start, but stays empty:</p>
<div class="sk-code">
  <span class="sk-code-head">Ausgabe</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">cp: cannot stat &#39;/config/.&#39;: Permission denied</span></span></code></pre></div>
</div>
<p>The official examples leave the step out because nobody there works as root: anyone creating the
folders under their own account has UID 1000 anyway. On a server where you work as root in <code>/opt</code>,
you have to do it yourself.</p>
<h3 id="step-6-start-and-check">Step 6: Start and check</h3>
<div class="sk-code">
  <span class="sk-code-head">Terminal</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">cd</span> /opt/jitsi
</span></span><span class="line"><span class="cl">docker compose up -d
</span></span><span class="line"><span class="cl">docker compose ps --format <span class="s1">&#39;{{ .Name }}\t{{ .Status }}&#39;</span></span></span></code></pre></div>
</div>
<div class="sk-code">
  <span class="sk-code-head">Ausgabe</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">jitsi-jicofo    Up 45 seconds
</span></span><span class="line"><span class="cl">jitsi-jvb       Up 45 seconds
</span></span><span class="line"><span class="cl">jitsi-prosody   Up 45 seconds
</span></span><span class="line"><span class="cl">jitsi-web       Up 45 seconds</span></span></code></pre></div>
</div>
<p>Four running containers do not yet mean they have found each other. The proof for that is in the
<code>jicofo</code> log, where the video bridge has to show up:</p>
<div class="sk-code">
  <span class="sk-code-head">Terminal</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">docker compose logs jicofo <span class="p">|</span> grep <span class="s2">&#34;Added new videobridge&#34;</span></span></span></code></pre></div>
</div>
<div class="sk-code">
  <span class="sk-code-head">Ausgabe</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">BridgeSelector.addJvbAddress#99: Added new videobridge:
</span></span><span class="line"><span class="cl">  Bridge[jid=jvbbrewery@internal-muc.meet.jitsi/07751be8e24f, version=2.3.318-gbf271b11f, ...]</span></span></code></pre></div>
</div>
<p>If that line is missing, <code>jvb</code> and <code>jicofo</code> are talking past each other. Usually that is because the
passwords in the <code>.env</code> were changed after the first start. Whether the bridge knows its public
address is shown by its own log:</p>
<div class="sk-code">
  <span class="sk-code-head">Terminal</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">docker compose logs jvb <span class="p">|</span> grep <span class="s2">&#34;static mapping&#34;</span></span></span></code></pre></div>
</div>
<div class="sk-code">
  <span class="sk-code-head">Ausgabe</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">MappingCandidateHarvesters.initialize: Adding a static mapping:
</span></span><span class="line"><span class="cl">  StaticMapping(localAddress=172.19.0.4, publicAddress=YOUR_SERVER_IP, …)</span></span></code></pre></div>
</div>
<p>If your public IPv4 shows up there, <code>JVB_ADVERTISE_IPS</code> has arrived. You can then ignore the
<code>stunDiscoveryFailed=true</code> a few lines further down. After that you check the web interface
and the signalling path from outside:</p>
<div class="sk-code">
  <span class="sk-code-head">Terminal</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">curl -s -o /dev/null -w <span class="s2">&#34;%{http_code}\n&#34;</span> https://YOUR_DOMAIN/
</span></span><span class="line"><span class="cl">curl -s -o /dev/null -w <span class="s2">&#34;%{http_code}\n&#34;</span> https://YOUR_DOMAIN/http-bind</span></span></code></pre></div>
</div>
<div class="sk-code">
  <span class="sk-code-head">Ausgabe</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">200
</span></span><span class="line"><span class="cl">200</span></span></code></pre></div>
</div>
<p>The second call is the more important one: <code>/http-bind</code> is the path your browser uses to talk to
<code>prosody</code>. A 404 here means Traefik passed the page through but not the API.</p>
<h3 id="step-7-the-moderator-account">Step 7: The moderator account</h3>
<p>With <code>ENABLE_AUTH=1</code> and <code>ENABLE_GUESTS=1</code> the rule is: <strong>only someone who logs in may open a
room</strong>; after that anyone with the link may join. Without this setting your instance is open to
everyone who knows the address, including the bandwidth that gets used up.</p>
<p>You create the account directly in <code>prosody</code>:</p>
<div class="sk-code">
  <span class="sk-code-head">Terminal</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">docker <span class="nb">exec</span> jitsi-prosody prosodyctl --config /run/prosody/config/prosody.cfg.lua <span class="se">\
</span></span></span><span class="line"><span class="cl">  register YOUR_USERNAME meet.jitsi <span class="s1">&#39;YOUR_PASSWORD&#39;</span></span></span></code></pre></div>
</div>
<div class="sk-code">
  <span class="sk-code-head">Ausgabe</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">usermanager  info  User account created: YOUR_USERNAME@meet.jitsi</span></span></code></pre></div>
</div>
<p>Note the path: at runtime the configuration lives under <code>/run/prosody/config/</code>, not under <code>/config</code>.
With the obvious <code>--config /config/prosody.cfg.lua</code>, Prosody reports &ldquo;Prosody was unable to find the configuration file&rdquo; instead.</p>
<p>The domain is <code>meet.jitsi</code>, the internal one from the <code>.env</code> and not your real one. Logging in
later still happens with the username alone, without a domain.</p>
<h3 id="step-8-the-first-meeting">Step 8: The first meeting</h3>
<p>Open your domain. You land on the start page, which suggests a random room name:</p>
<p><figure class="my-6"><img src="/en/tutorials/jitsi-meet-video-conferences/jitsi-start_hu_ed84b5fbd28a750c.webp" srcset="/en/tutorials/jitsi-meet-video-conferences/jitsi-start_hu_fe6d32017e7a0b7a.webp 480w, /en/tutorials/jitsi-meet-video-conferences/jitsi-start_hu_ed84b5fbd28a750c.webp 768w, /en/tutorials/jitsi-meet-video-conferences/jitsi-start_hu_8188f880e59790b6.webp 1200w, /en/tutorials/jitsi-meet-video-conferences/jitsi-start_hu_11e0b694937df6fe.webp 1920w" sizes="(min-width: 768px) 768px, 100vw"
    width="768" height="432"
    data-full="/en/tutorials/jitsi-meet-video-conferences/jitsi-start_hu_502151b2eadbc9f5.webp"
    alt="The Jitsi Meet start page with an input field for the room name and a Start meeting button" title="The start page suggests a random room name, which you can overwrite"
    loading="lazy" decoding="async" class="rounded-lg"><figcaption class="mt-2 text-sm text-center text-slate-500 italic">The start page suggests a random room name, which you can overwrite</figcaption></figure></p>
<p>The room name becomes part of the URL (<code>https://YOUR_DOMAIN/CookingNight</code>), and <strong>whoever knows the URL
gets into the room</strong>. So do not pick anything guessable like <code>test</code> or <code>meeting</code>. After the click
you land in the pre-join room, where Jitsi checks camera and microphone:</p>
<p><figure class="my-6"><img src="/en/tutorials/jitsi-meet-video-conferences/jitsi-prejoin_hu_4d17ac6411476d5a.webp" srcset="/en/tutorials/jitsi-meet-video-conferences/jitsi-prejoin_hu_79ff3ca1819efb4b.webp 480w, /en/tutorials/jitsi-meet-video-conferences/jitsi-prejoin_hu_4d17ac6411476d5a.webp 768w, /en/tutorials/jitsi-meet-video-conferences/jitsi-prejoin_hu_78282c218fcc10b4.webp 1200w, /en/tutorials/jitsi-meet-video-conferences/jitsi-prejoin_hu_7e8555b37d6bd8f9.webp 1920w" sizes="(min-width: 768px) 768px, 100vw"
    width="768" height="432"
    data-full="/en/tutorials/jitsi-meet-video-conferences/jitsi-prejoin_hu_710549f03ea69e45.webp"
    alt="The Jitsi pre-join screen with a name field, device buttons and the notice Your devices are working properly" title="In the pre-join room you enter your name (the camera is switched off here for the screenshot)"
    loading="lazy" decoding="async" class="rounded-lg"><figcaption class="mt-2 text-sm text-center text-slate-500 italic">In the pre-join room you enter your name (the camera is switched off here for the screenshot)</figcaption></figure></p>
<p>Now comes the part that would look different without authentication. Because no moderator is in the
room yet, the conference stays closed:</p>
<p><figure class="my-6"><img src="/en/tutorials/jitsi-meet-video-conferences/jitsi-moderator_hu_f56c10358e0332d1.webp" srcset="/en/tutorials/jitsi-meet-video-conferences/jitsi-moderator_hu_852e2260c5d1fc2f.webp 480w, /en/tutorials/jitsi-meet-video-conferences/jitsi-moderator_hu_f56c10358e0332d1.webp 768w, /en/tutorials/jitsi-meet-video-conferences/jitsi-moderator_hu_88ef2ea742138d51.webp 1200w, /en/tutorials/jitsi-meet-video-conferences/jitsi-moderator_hu_24d4a117f7f845ad.webp 1920w" sizes="(min-width: 768px) 768px, 100vw"
    width="768" height="432"
    data-full="/en/tutorials/jitsi-meet-video-conferences/jitsi-moderator_hu_33a0969ad864bea6.webp"
    alt="The dialog Waiting for a moderator with the buttons Cancel and Log-in" title="Without a moderator no conference starts: guests wait, you log in"
    loading="lazy" decoding="async" class="rounded-lg"><figcaption class="mt-2 text-sm text-center text-slate-500 italic">Without a moderator no conference starts: guests wait, you log in</figcaption></figure></p>
<p>Through &ldquo;Log-in&rdquo; you enter the username and password from step 7. After that you are in the
room, with an &ldquo;M&rdquo; next to your own name for &ldquo;moderator&rdquo;:</p>
<p><figure class="my-6"><img src="/en/tutorials/jitsi-meet-video-conferences/jitsi-konferenz_hu_8f792d17dc947807.webp" srcset="/en/tutorials/jitsi-meet-video-conferences/jitsi-konferenz_hu_c43d72a37cd81742.webp 480w, /en/tutorials/jitsi-meet-video-conferences/jitsi-konferenz_hu_8f792d17dc947807.webp 768w, /en/tutorials/jitsi-meet-video-conferences/jitsi-konferenz_hu_e481fa31a49d1a17.webp 1200w, /en/tutorials/jitsi-meet-video-conferences/jitsi-konferenz_hu_aae314af6430ff89.webp 1920w" sizes="(min-width: 768px) 768px, 100vw"
    width="768" height="432"
    data-full="/en/tutorials/jitsi-meet-video-conferences/jitsi-konferenz_hu_5e02a8ed7394a515.webp"
    alt="A running Jitsi room with title bar, timer, a participant tile carrying the moderator marker and the toolbar" title="Inside the room: name and running time at the top, your own tile with the M for moderator on the right"
    loading="lazy" decoding="async" class="rounded-lg"><figcaption class="mt-2 text-sm text-center text-slate-500 italic">Inside the room: name and running time at the top, your own tile with the M for moderator on the right</figcaption></figure></p>
<p>From now on guests come in over the same link, without an account. Leave the room as the last
moderator and the conference is over.</p>
<h3 id="step-9-the-udp-port">Step 9: The UDP port</h3>
<p>The web interface works long before the media path does, which is why a closed UDP port only shows
up once several people are inside. Check that the server is listening on 10000:</p>
<div class="sk-code">
  <span class="sk-code-head">Terminal</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ss -lunp <span class="p">|</span> grep <span class="m">10000</span></span></span></code></pre></div>
</div>
<div class="sk-code">
  <span class="sk-code-head">Ausgabe</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">UNCONN 0 0 0.0.0.0:10000 0.0.0.0:* users:((&#34;docker-proxy&#34;,pid=173295,fd=8))
</span></span><span class="line"><span class="cl">UNCONN 0 0    [::]:10000    [::]:* users:((&#34;docker-proxy&#34;,pid=173302,fd=8))</span></span></code></pre></div>
</div>
<p>Then open it, in <strong>both</strong> firewalls. On the server:</p>
<div class="sk-code">
  <span class="sk-code-head">Terminal</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">ufw allow 10000/udp comment <span class="s1">&#39;Jitsi Videobridge&#39;</span></span></span></code></pre></div>
</div>
<div class="not-prose my-6 rounded-lg border-l-4 p-4 border-amber-400 bg-amber-50 dark:border-amber-700 dark:bg-amber-900/20">
  <p class="mb-1 flex items-center gap-2 font-semibold text-slate-900 dark:text-white">
    <span aria-hidden="true">⚠️</span>With two people you are not testing the port at all
  </p>
  <div class="prose-kitchen text-sm"><p>With exactly two participants Jitsi builds a direct connection between the browsers (P2P)
and leaves the video bridge out entirely. The complete media stream of a two-person call then
goes over a direct candidate pair: <strong>not a single byte</strong> goes through UDP 10000. Only from
the third participant onwards does the bridge take over.</p>
<p>So anyone trying out a fresh instance with two people is testing exactly the path that is not
the one that breaks later. Bring in a third person for the test or switch P2P off
temporarily. Putting <code>ENABLE_P2P=0</code> into the <code>.env</code> is not enough: Compose only passes on the
variables listed under the service&rsquo;s <code>environment</code>. Add the line <code>- ENABLE_P2P</code> to the <code>web</code>
service, set <code>ENABLE_P2P=0</code> in the <code>.env</code> and restart with <code>docker compose up -d web</code>; then the
two-person call goes over the bridge as well. Whether it took effect is shown by
<code>curl -s https://YOUR_DOMAIN/config.js | grep -A1 &quot;config.p2p&quot;</code>. It has to say <code>enabled: false</code>.</p>
</div>
</div>
<p>And a <strong>policy of its own</strong> in the netcup SCP. This is the step that goes missing most often,
because without it Jitsi looks entirely normal: the web interface arrives over 443 and is long since
covered by your web policy, the room opens, the participant list fills up, and only once somebody
speaks does anyone notice that nothing arrives.</p>
<p>Under &ldquo;Firewall Policys → Create firewall policy&rdquo; create a template <code>Jitsi</code> with exactly one rule
and assign it to the server in addition to your existing templates:</p>
<div class="sk-code">
  <span class="sk-code-head">Ausgabe</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">Direction          INBOUND
</span></span><span class="line"><span class="cl">Action             ACCEPT
</span></span><span class="line"><span class="cl">Protocol           UDP
</span></span><span class="line"><span class="cl">Source port        –
</span></span><span class="line"><span class="cl">Destination port   10000</span></span></code></pre></div>
</div>
<p>Why this does not happen by itself: the netcup firewall is <strong>stateless for UDP</strong>. It does not
remember that your server is currently sending media and therefore does not let the replies back in
automatically. This path needs an explicit inbound rule. The procedure and how to assign templates
are in <a href="/en/tutorials/netcup-firewall-setup/">setting up the netcup firewall in the SCP</a>.</p>
<div class="not-prose my-6 rounded-lg border-l-4 p-4 border-amber-400 bg-amber-50 dark:border-amber-700 dark:bg-amber-900/20">
  <p class="mb-1 flex items-center gap-2 font-semibold text-slate-900 dark:text-white">
    <span aria-hidden="true">⚠️</span>One firewall is not enough
  </p>
  <div class="prose-kitchen text-sm">UFW runs on the server, the netcup firewall in front of it. Neither sees the other. Open
only one of the two and you get a video conference where everyone can see each other and nobody is
heard, and you will look for the fault in the Jitsi configuration for hours.</div>
</div>
<h2 id="when-it-doesnt-work">When it doesn&rsquo;t work</h2>
<div class="troubleshoot not-prose">
<p><strong>Traefik answers with <code>502 Bad Gateway</code> even though all four containers are running.</strong> The nginx inside the web container listens on port 8000, not on 80, because it runs unprivileged. Set <code>traefik.http.services.jitsi.loadbalancer.server.port=8000</code>. You can look it up with <code>docker exec jitsi-web ss -lnt</code>; the port actually in use is right there. The same error appears when <code>traefik.docker.network=proxy</code> is missing and Traefik picks up the container address from the internal <code>meet.jitsi</code> network, which it cannot reach itself.</p>
<p><strong>The web container starts but reports <code>cp: cannot stat '/config/.': Permission denied</code> and serves nothing.</strong> The mounted folders under <code>/opt/jitsi/config</code> belong to root while the containers run as UID 1000. A <code>chown -R 1000:1000 /opt/jitsi/config</code> and a restart fix it. On hardened servers with <code>umask 027</code> this hits you every time, because newly created folders then get <code>0750</code>.</p>
<p><strong>With two people everything works, from the third participant on nobody hears or sees anything.</strong> That is the classic picture of a closed UDP port. It only surfaces now, because Jitsi runs two-person calls directly between the browsers and only uses the video bridge from three participants onwards. Check <code>ss -lunp | grep 10000</code> on the server and the inbound ACCEPT rule for UDP 10000 in both firewalls. The bridge&rsquo;s logs show it too: <code>docker compose logs jvb | grep -i 'ICE state'</code> then shows transitions to <code>Terminated</code> without a connection ever being established.</p>
<p><strong>Everyone is in the room, but nobody hears or sees anybody.</strong> That is almost always the media path, not the conference. Check <code>docker compose logs jvb | grep &quot;static mapping&quot;</code> first. If there is no line with your public address, <code>JVB_ADVERTISE_IPS</code> is missing from the <code>.env</code> and the video bridge announces its container address to the browsers. If the address is right, the next suspect is UDP 10000 in the firewall, in <strong>both</strong> of them (the one on the server and the one at the provider). In the netcup SCP that means a policy of its own with an inbound ACCEPT rule on UDP 10000; a web template covering 80/443 does not include it.</p>
<p><strong>After <code>docker compose down</code> the moderator account is gone.</strong> Prosody stores accounts under <code>/var/lib/prosody</code>, and that directory is not mounted in the official template: the accounts disappear along with the container. The mount <code>./config/prosody/data:/var/lib/prosody:Z</code> fixes it; afterwards the accounts live on the host under <code>config/prosody/data/data/meet%2ejitsi/accounts/</code>. An account that is already lost is simply created again.</p>
<p><strong>The &ldquo;Waiting for a moderator&rdquo; dialog stays up even after logging in.</strong> Then the account does not exist in the domain Jitsi looks in. Registration happens against <code>meet.jitsi</code>, the internal domain from the <code>.env</code>, not your real one. Check with <code>docker exec jitsi-prosody prosodyctl --config /run/prosody/config/prosody.cfg.lua register NAME meet.jitsi PASSWORD</code>: if the command reports &ldquo;User already exists&rdquo;, the domain is right and the password is wrong.</p>

</div>
<p class="mt-3 text-sm text-slate-500 dark:text-slate-400">
  Your problem is not listed?
  <a href="/en/errors/" class="font-medium text-paprika-700 hover:underline dark:text-paprika-400">Search all error messages →</a>
</p>

<h2 id="maintenance--backups">Maintenance &amp; backups</h2>
<p>Updates arrive as one package. Jitsi puts out a new <code>stable</code> tag every few weeks, and all four
images carry the same one:</p>
<div class="sk-code">
  <span class="sk-code-head">Terminal</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="nb">cd</span> /opt/jitsi
</span></span><span class="line"><span class="cl">sed -i <span class="s1">&#39;s/stable-11248-3/stable-NEW_VERSION/g&#39;</span> compose.yaml
</span></span><span class="line"><span class="cl">docker compose pull <span class="o">&amp;&amp;</span> docker compose up -d
</span></span><span class="line"><span class="cl">docker compose logs jicofo <span class="p">|</span> grep <span class="s2">&#34;Added new videobridge&#34;</span></span></span></code></pre></div>
</div>
<p>The last command is the acceptance test: if the line does not appear, something shifted between
control and bridge during the update. You find the current tag at the
<a href="https://github.com/jitsi/docker-jitsi-meet/releases">docker-jitsi-meet releases</a>, not on Docker
Hub, whose state lags months behind.</p>
<p>What you have to back up is little, but it counts:</p>
<div class="sk-code">
  <span class="sk-code-head">Ausgabe</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">/opt/jitsi/.env                 # the three secrets
</span></span><span class="line"><span class="cl">/opt/jitsi/config/prosody/data  # the moderator accounts</span></span></code></pre></div>
</div>
<p>Everything else under <code>config/</code> is regenerated from the environment variables on every start. Your
own edits to those files are gone after the next restart. If you really want to change something
about the interface, create a <code>custom-config.js</code> for it; everything else belongs in the <code>.env</code>. Both
paths together are a few kilobytes and fit into any <a href="/en/tutorials/restic-backups/">Restic backup</a>.</p>
<p>Resource use is unremarkable at first. Idle, the stack uses just under 400 MB:</p>
<div class="sk-code">
  <span class="sk-code-head">Ausgabe</span>
  <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">jitsi-web       14 MB
</span></span><span class="line"><span class="cl">jitsi-prosody   22 MB
</span></span><span class="line"><span class="cl">jitsi-jicofo   146 MB
</span></span><span class="line"><span class="cl">jitsi-jvb      191 MB</span></span></code></pre></div>
</div>
<p>That stays similar under load; what grows is the CPU load and the bandwidth of the video bridge.
It forwards the streams without re-encoding them, but every additional participant means more
packets. A small VPS is enough for a handful of people; from roughly a dozen simultaneous cameras
onwards the uplink becomes the topic, not the memory.</p>
<p>Realistically, it is once a month a look for a new <code>stable</code> tag and an update that costs ten
minutes. Nothing happens in between: Jitsi has no database that grows and no media that piles up.
The one appointment you should make for yourself is a short test call after every update, before the
first real meeting is due.</p>
]]></content:encoded></item></channel></rss>