Skip to content

Back up Coolify and its hosted applications separately

Protect the control plane and each workload, not just the Coolify dashboard database.

Protect your data firstKeep a current off-server backup before reinstalling, updating, changing firewall rules, or running an application installer.
On this page

Protect two different layers

A Coolify instance backup protects its own configuration and deployment records. It does not replace backups of application databases, uploads, or persistent volumes on connected servers.

Preserve recovery material

Keep the instance encryption key securely outside the server with the recovery documentation. Do not reveal it in logs or tickets. Record application versions, mounts, database engines, and external storage locations separately.

Verify each scheduled backup

For a supported database, inspect the backup execution, intended scope, size, and remote-storage result. A successful local dump and a failed remote upload are different outcomes. Ensure an off-server copy actually exists.

Test a restore

Restore into an isolated destination and confirm representative application records and files. A successful backup job alone is not proof of recovery. Do not test by overwriting your production database.

Coolify instance backups, database backups.

Was this not enough?Include the service number, exact error, and time of the problem. Never send a password or private key.
Contact support