Add `adminapi` resource to MAS HTTP listener in deploy.sh and quickstart.sh. Without it, MAS never served /api/admin/v1/... causing Element Admin to always throw TypeError: Failed to fetch. Updated docs and added regression test. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Matrix Server - Docker Compose Setup
A self-hosted Matrix server stack with modern OIDC authentication, web client, optional video calling, and optional messaging bridges.
What's Included
Core (always on)
- Synapse — Matrix homeserver
- Matrix Authentication Service (MAS) — OIDC-based authentication
- Element Web — Web client
- Element Admin — Admin dashboard
- PostgreSQL 16 — Database
- Caddy — Reverse proxy with automatic HTTPS
Optional: Element Call (--profile element-call)
- LiveKit — WebRTC SFU media server (self-hosted, media stays on your server)
- lk-jwt-service — LiveKit token issuer
- Element Call — Self-hosted video/voice calling frontend
Optional: Messaging Bridges (via setup-bridges.sh)
- mautrix-whatsapp — WhatsApp bridge
- mautrix-signal — Signal bridge
- mautrix-telegram — Telegram bridge (requires API credentials)
Optional: Upstream OIDC (--profile authelia)
- Authelia — SSO / identity provider with 2FA
Quick Start
Simple production deployment — three prompts, everything else is automatic:
./quickstart.sh
Asks for: your domain, a Let's Encrypt email, and whether to enable Element Call. Generates all secrets and configs, starts the stack.
Advanced deployment — local testing, Authelia SSO, multi-machine setups:
./deploy.sh
Bridges are set up separately after the core stack is running:
./setup-bridges.sh
Architecture
Browser
|
Caddy (HTTPS, Let's Encrypt)
|
+-- matrix.example.com --> Synapse :8008
| /.well-known --> (served inline by Caddy)
| /login, /logout --> MAS :8080
+-- auth.example.com --> MAS :8080
+-- element.example.com --> Element Web :80
+-- admin.example.com --> Element Admin :8080
+-- call.example.com --> Element Call :8080 (optional)
+-- rtc.example.com --> lk-jwt-service :8080 (optional)
LiveKit :7880 (optional)
All services communicate over an internal Docker network. The database is not exposed.
Deployment Options
Simple production — single machine, Let's Encrypt, no Authelia:
./quickstart.sh
Local testing — self-signed certificates, *.example.test domains:
./deploy.sh # choose "Local Testing"
Production with Authelia — SSO, 2FA, upstream OIDC:
./deploy.sh # choose "Production", answer yes to Authelia
Multi-machine — Matrix backend on one server, Caddy on another:
./deploy.sh # choose "Production" (multi-server mode)
Generates a caddy/Caddyfile.production for the Caddy machine.
Element Call
When enabled, all three components are self-hosted. Media streams never leave your server (they route through your LiveKit SFU). The Element Call frontend is served from your own call. subdomain.
Required open ports in addition to 80 and 443:
- TCP 7881 (WebRTC signaling)
- UDP 50100–50200 (media streams)
Bridges
setup-bridges.sh configures WhatsApp and Signal automatically. Telegram requires API credentials from my.telegram.org — add them to .env before running:
TELEGRAM_API_ID=your_id
TELEGRAM_API_HASH=your_hash
Bridges use double puppet support (messages appear from your actual Matrix user, not a bridge bot) and have encryption disabled for compatibility with MAS. See BRIDGE_SETUP_GUIDE.md for details.
Air-gapped / Custom Registry
deploy.sh optionally prefixes all image references with a custom registry URL (for internal mirrors or air-gapped environments) and optionally switches Redis, PostgreSQL, and Caddy to hardened variants from dhi.io. Both settings are written to .env and picked up automatically by Docker Compose.
See SETUP.md — Custom Docker Registry for details, including a note on pull-through cache registries (Harbor, Artifactory, Nexus) that require the full registry path in image names.
Requirements
- Docker and Docker Compose v2
- A domain with DNS control
- Ports 80 and 443 accessible from the internet
- For Element Call: ports 7881/TCP and 50100–50200/UDP open
Common Operations
# Status
docker compose ps
# Logs
docker compose logs -f [service]
# Restart a service
docker compose restart synapse
# Update all images
docker compose pull && docker compose up -d
# Bridge logs
docker compose logs mautrix-whatsapp
Data Directories
postgres/data/ database (back this up)
synapse/data/ media store, signing keys
mas/data/ MAS sessions
.env all secrets and domain config
Backup:
tar -czf matrix-backup-$(date +%Y%m%d).tar.gz postgres/data synapse/data mas/data .env
Documentation
- SETUP.md — manual configuration reference
- PRODUCTION_DEPLOYMENT.md — production checklist and hardening
- BRIDGE_SETUP_GUIDE.md — bridge configuration details
- BUGFIXES.md — known issues and their solutions
- QUICK_REFERENCE.md — common commands
License
- Synapse: Apache 2.0
- Matrix Authentication Service: Apache 2.0
- Element Web / Element Admin / Element Call: Apache 2.0
- PostgreSQL: PostgreSQL License
- Caddy: Apache 2.0
- LiveKit: Apache 2.0