FibaCloud n8n Compose example — tested 2026-10-31

TR: https://www.fibacloud.com/community/tutorials/n8n-kurulumu-ubuntu-docker/
EN: https://www.fibacloud.com/community/tutorials/en/install-n8n-ubuntu-docker/

Follow the article for installation. The files live inside the n8n-compose folder in this archive. Use a new private 0700 project directory. Copy .env.example to .env (0600), replace the DNS hostname and operator IP, and generate four separate secrets. Placeholder values are not usable credentials. Keep initdb.sh readable (0644); it contains no password. Preserve the original N8N_ENCRYPTION_KEY for recovery.

Caddyfile is the final proxy configuration. Keep a copy as Caddyfile.final and use Caddyfile.bootstrap as Caddyfile during first-owner setup. Switch only after creating the owner. The initial IP restriction assumes DNS-only access with no extra proxy.

workflow.json is an unpublished, sanitized native export of the tested three-node workflow. Create your own Header Auth credential: Name Authorization; Value Bearer followed by your private token. Use the whole-canvas Execute action to test the full chain. A trigger-only test does not exercise Code and Respond. Webhook input/execution panels may show Authorization headers: keep them private. No live credential or instance ID is included.

maintenance.py uses a brief application outage for a logical PostgreSQL backup plus persistent-volume archives. It restores to a different, unpublished Compose project; all attached networks are internal, and Caddy is not started. Internal networking does not prevent local timers or all access to host services: test only controlled workflows. On small servers stop the source before starting the clone, then stop the clone using both compose.yml and restore.override.json before resuming the source. See the article for the exact sequence and functional checks. Keep backups private, encrypted where stored, and off the original server. This example is not a capacity or high-availability guarantee.
