Docs

Practical guides and gotchas for running a self-hosted stack with Coolify on Hetzner. Real issues, real fixes — learned in production.

Coolify

Gotchas & Known Issues

docker-compose overwrites, API quirks, SERVICE_URL issues, and backup pitfalls.

Apps

API auth, custom opt-in emails, bilingual campaigns, and common setup gotchas.

Worker not starting, missing Traefik port label, and the mixed-content fix.

What's missing from CE, valid script extensions, and CSP requirements.

Exposing the backend via Traefik so the frontend can actually reach it.

Two things you must do before going live: hash the admin token, disable signups.

Infrastructure

PGBackWeb for Postgres, docker-volume-backup for file/SQLite, R2 as destination.

Cloudflare auto-injects scripts. Here's the correct script-src and connect-src setup.

Rather have someone else handle it?

We set up and manage the full self-hosted stack — Coolify, Hetzner, backups, monitoring, and all the apps — so you don't have to read any of this.