-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Open
Labels
🐛 BugReported issues that need to be reproduced by the team.Reported issues that need to be reproduced by the team.🔍 TriageIssues that need assessment and prioritization.Issues that need assessment and prioritization.
Description
Error Message and Logs
Coolify main container logs it cannot cannot to the Coolify database.
Steps to Reproduce
Hi,
I followed https://coolify.io/docs/knowledge-base/how-to/backup-restore-coolify to migrate my Coolify to a new server, everything is almost good.
Except that restoring the database with the backup seems to override the database password. So there is not only APP_PREVIOUS_KEYS
to add the .env
but also probably override DB_PASSWORD
with the value from the old Coolify .env
.
Overriding this did fix the issue on my side. If anyone else can confirm what I found (confirmation is better, there is still the possibility I did something wrong?).
Example Repository URL
No response
Coolify Version
v4.0.0-beta.426
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
Also below a few more things:
- Why don't you recommend as for "application migration" to copy Docker volumes of Coolify to the new instance with the same exact settings
.env
, SSH keys...? (since your tutorial is requesting in all cases the same version of installation, it seems Coolify files outside volumes would work too) - My
~/.ssh/authorized_keys
from the old server installed 1 year ago is allowingroot@coolify
whereas the new one was allowing something likecoolify
. Any importance over time? - About migrating Docker volumes for applications in my case, just to mention on my side I recreate empty volumes of the same name on the new server (
docker volume create $volumeNameX
to adjust for all names), then usersync
to populate them. It seems to me a bit more straightforward than dealing with bash scripts as mentioned at https://coolify.io/docs/knowledge-base/how-to/migrate-apps-different-host . For example a command to run BEFORE installing Coolify on the new server, and from the source server (rsync
must be on both):
rsync -aAXHv --numeric-ids --delete \
-e "ssh -p 22" \
--relative \
--exclude="/var/lib/docker/volumes/coolify-*/" \
/data/coolify/backups/coolify/coolify-db-hostdockerinternal/pg-dump-coolify-*.dmp \
/data/coolify/proxy/acme.json \
/var/lib/docker/volumes/*/_data/ \
[email protected]:/
Metadata
Metadata
Assignees
Labels
🐛 BugReported issues that need to be reproduced by the team.Reported issues that need to be reproduced by the team.🔍 TriageIssues that need assessment and prioritization.Issues that need assessment and prioritization.