Skip to main content
OSSAlt

How to Self-Host Owncast: Live Streaming Server 2026

·OSSAlt Team
owncastlive-streamingself-hostingdockerfediverseobs2026
Share:

TL;DR

Owncast (MIT, ~9K GitHub stars, Go) is a self-hosted live streaming server. Stream via OBS (or any RTMP software), and viewers watch in a built-in web player with live chat — no Twitch, no YouTube, no platform rules. Owncast integrates with the Fediverse (Mastodon, etc.) so followers get notified when you go live. Twitch takes 50% of sub revenue; Owncast is free with zero platform fees.

Key Takeaways

  • Owncast: MIT, ~9K stars, Go — self-hosted live streaming
  • OBS compatible: Stream via RTMP from any streaming software
  • Built-in chat: Real-time chat with moderation tools
  • Fediverse integration: ActivityPub — followers on Mastodon get live notifications
  • S3 storage: Offload video segments to S3/B2 for scalable delivery
  • Embeddable: Embed the player on any website
  • Single binary: No dependencies — runs on any Linux server

Part 1: Docker Setup

# docker-compose.yml
services:
  owncast:
    image: owncast/owncast:latest
    container_name: owncast
    restart: unless-stopped
    ports:
      - "8080:8080"     # Web UI + player
      - "1935:1935"     # RTMP ingest
    volumes:
      - owncast_data:/app/data

volumes:
  owncast_data:

docker compose up -d
  • Web UI: http://your-server:8080
  • Admin panel: http://your-server:8080/admin (default password: abc123 — change immediately!)

Part 2: HTTPS with Caddy

live.yourdomain.com {
    reverse_proxy localhost:8080
}

Note: RTMP (port 1935) doesn't use HTTPS — it stays on port 1935. Only the web UI needs HTTPS.

Part 3: OBS Configuration

Stream from OBS

  1. Open OBS → Settings → Stream
  2. Service: Custom...
  3. Server: rtmp://live.yourdomain.com/live
  4. Stream Key: (from Owncast admin → Configuration → Server Setup → Stream Key)
  5. Apply → Start Streaming
Output → Streaming:
  Encoder: x264 (or NVENC for GPU)
  Rate Control: CBR
  Bitrate: 2500-4500 kbps (adjust for bandwidth)
  Keyframe Interval: 2 seconds

Video:
  Base Resolution: 1920x1080
  Output Resolution: 1280x720 (for lower bandwidth)
  FPS: 30

Audio:
  Sample Rate: 48 kHz
  Bitrate: 160 kbps

Other streaming software

Any RTMP-compatible software works:

  • Streamlabs: Same RTMP URL configuration
  • FFmpeg: ffmpeg -re -i input.mp4 -c copy -f flv rtmp://live.yourdomain.com/live/STREAM_KEY
  • Restream: Forward to Owncast as a custom destination

Part 4: Admin Configuration

General settings

Admin → Configuration:
  Server Name: Your Channel Name
  Server Summary: What your stream is about
  Logo: Upload your channel logo
  Tags: gaming, coding, music (for Fediverse discovery)
  
  Stream Key: (change from default!)
  Stream Title: (update per stream)
  
  NSFW: false

Video quality

Admin → Configuration → Video:
  
  # Output variants (adaptive bitrate):
  - 720p at 2500 kbps (default)
  - 480p at 1200 kbps (low bandwidth)
  - Audio only at 128 kbps (very low bandwidth)
  
  Latency level: Low (4s) / Standard (10s) / High (20s)
  # Lower latency = more CPU, more buffering risk

Custom page content

Admin → Configuration → General:
  Extra Page Content: (Markdown)
  
  ## About This Stream
  Welcome to my channel! I stream:
  - 🎮 Indie games on Tuesdays
  - 💻 Coding sessions on Thursdays
  - 🎵 Music production on weekends
  
  ## Links
  - [Website](https://yourdomain.com)
  - [Mastodon](https://mastodon.social/@you)

Part 5: Chat and Moderation

Chat features

  • Real-time messaging
  • Custom emojis (upload in admin)
  • Username and color customization
  • Chat authentication (optional)

Moderation

Admin → Chat:
  - Require authentication to chat
  - Forbidden usernames: list
  - Forbidden words: filter list
  
Admin → Chat Users:
  - Ban users
  - Moderator role: can timeout/ban others

Chat authentication options

Admin → Configuration → Chat:
  - Anonymous chat (default)
  - IndieAuth authentication
  - Fediverse authentication (login with Mastodon account)

Part 6: Fediverse Integration

Enable ActivityPub

Admin → Configuration → Federation:
  Enable Federation: Yes
  Instance URL: https://live.yourdomain.com
  
  # Your Fediverse handle becomes:
  # @admin@live.yourdomain.com

What happens

  1. People on Mastodon/Pleroma/Pixelfed can follow @admin@live.yourdomain.com
  2. When you go live, followers get a notification post
  3. When you update the stream title, it posts an update
  4. Followers can interact (boost, reply) directly from Mastodon

Follow from Mastodon

# Search for your Owncast handle:
@admin@live.yourdomain.com

# Click Follow → receive notifications when stream goes live

Part 7: S3 Storage (Scaling)

For large audiences, offload video segments to S3/B2/MinIO:

Admin → Configuration → Storage:
  Enable S3 Storage: Yes
  Endpoint: s3.amazonaws.com (or minio.yourdomain.com)
  Access Key: AKIA...
  Secret Key: your-secret
  Bucket: owncast-stream
  Region: us-east-1
  
  # Or Backblaze B2:
  Endpoint: s3.us-west-002.backblazeb2.com
  Bucket: owncast-stream

With S3 storage:

  • Video segments are uploaded to S3 in real-time
  • Viewers download from S3/CDN instead of your server
  • Your server only handles RTMP ingest and chat
  • Scales to thousands of concurrent viewers

Part 8: Embedding

Embed player on your website

<!-- Video player only: -->
<iframe
  src="https://live.yourdomain.com/embed/video"
  width="100%"
  height="450"
  referrerpolicy="origin"
  scrolling="no"
  allowfullscreen>
</iframe>

<!-- Chat only: -->
<iframe
  src="https://live.yourdomain.com/embed/chat/readwrite"
  width="100%"
  height="500">
</iframe>

<!-- Read-only chat: -->
<iframe
  src="https://live.yourdomain.com/embed/chat/readonly"
  width="100%"
  height="500">
</iframe>

REST API

BASE="https://live.yourdomain.com"

# Check if stream is live:
curl "$BASE/api/status" | jq '{online: .online, viewerCount: .viewerCount, title: .streamTitle}'

# Get chat messages:
curl "$BASE/api/chat" | jq '.[].body'

# Send a system message (admin):
curl -X POST "$BASE/api/integrations/chat/system" \
  -H "Authorization: Bearer YOUR_ADMIN_TOKEN" \
  -d '{"body": "Stream starting in 5 minutes!"}'

Maintenance

# Update:
docker compose pull
docker compose up -d

# Backup:
tar -czf owncast-backup-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect owncast_owncast_data --format '{{.Mountpoint}}')

# Check stream health:
curl -s https://live.yourdomain.com/api/status | jq .

# Logs:
docker compose logs -f owncast

Why Self-Host Owncast?

The case for self-hosting Owncast comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Owncast means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Owncast, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Owncast headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Owncast data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Owncast without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Owncast's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Owncast backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Owncast's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Owncast's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Owncast's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Owncast's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f owncast

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Owncast's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

  1. Confirm the container is running: docker compose ps
  2. Test locally on the server: curl -I http://localhost:PORT
  3. If local access works but external doesn't, check your firewall: ufw status
  4. If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats owncast. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Owncast Updated

Owncast follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Owncast is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See all open source media tools at OSSAlt.com/categories/media.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)

Step-by-step: infrastructure setup, data migration, backups, and security for 15+ common SaaS replacements. Used by 300+ developers.

Join 300+ self-hosters. Unsubscribe in one click.