---
title: "Discussion on \"Deploying Jitsi Meet Behind Traefik with Docker Compose (Custom SSL PEM/KEY + Host Authentication)\" | Hashnode"
description: "Discussion on \"Deploying Jitsi Meet Behind Traefik with Docker Compose (Custom SSL PEM/KEY + Host Authentication)\". Self-host Jitsi Meet with Traefik reverse proxy: custom TLS via file provider, secure headers, and internal authentication with Prosody users."
url: "https://hashnode.com/posts/deploying-jitsi-meet-behind-traefik-with-docker/6992cd208f48ce650126ca3f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Deploying Jitsi Meet Behind Traefik with Docker Compose (Custom SSL PEM/KEY + Host Authentication)](https://blog.mahdishadi.me/deploying-jitsi-meet-behind-traefik-with-docker?utm_source=hashnode&utm_medium=feed)

Self-host Jitsi Meet with Traefik reverse proxy: custom TLS via file provider, secure headers, and internal authentication with Prosody users.

Feb 16 · 5 min read · blog.mahdishadi.me  
Read the article

-   [#docker](https://hashnode.com/tag/docker)
-   [#jitsi-meet](https://hashnode.com/tag/jitsi-meet)
-   [#traefik](https://hashnode.com/tag/traefik)
-   [#docker-compose](https://hashnode.com/tag/docker-compose)

## Written by

[Mahdi Shadi](https://hashnode.com/@soloranger)

@soloranger

  
[View profile](https://hashnode.com/@soloranger)

network,virtualization,cisco,cloud,devops

Linux &amp; Network Lover 💻 DevOps Student Chess Player ♟️

## Responses 1

Markdown supported · ⌘↵ to post

[Edge Ops](https://hashnode.com/@edgecacheops)

[Nov 5](https://hashnode.com/posts/deploying-jitsi-meet-behind-traefik-with-docker/6992cd208f48ce650126ca3f/comment/6aebeb13b3c9758989bd4f00)

Putting Jitsi behind Traefik with a file-provider PEM stays reliable when the TLS certificate and Host routers share the same websecure entrypoint and the PEM/KEY pair is mounted read-only where the static config expects it. I pin which entrypoint terminates TLS, keep the dashboard off the public listener, and make sure every router hostname already resolves to the address Traefik binds before flipping production DNS. Docker labels should declare the same cert source the file provider loads; a Host rule that matches while the cert SAN does not looks like a random browser trust failure while sibling stacks continue fine.

After apply I watch which router each Meet hostname matched, then hit the web UI once and open a short test call to confirm WebSocket and long-lived media signaling paths are not buffered or timed out like ordinary API traffic. Also verify X-Forwarded-Proto and the real client address still reach Prosody/web after Traefik terminates TLS — losing those on a label bump often shows up as a redirect or auth loop that is still the proxy hop. An internal health probe to the service name, then the same path through the public Host, separates discovery drift from a real container crash.
