a month ago
Hello,
I need your help investigating a possible issue related to an automatic deployment.
Project details:
Project: precious-encouragement
Service: n8n
Deployment ID: de098092-4742-4be8-99b6-3ec6e8f4a920
Timeline:
Around 2026-08-16 11:02 UTC, a new /home/node/.n8n/config file was created.
n8n logged:
No encryption key found - Auto-generating and saving
PostgreSQL data remained intact.
credentials_entity still contains all encrypted credentials.
n8n export:credentials --decrypted fails with:
Credentials could not be decrypted. The likely reason is that a different encryptionKey was used to encrypt the data.
Could you please confirm:
Whether Railway automatically recreated or redeployed my service around Aug 16.
Whether there are any retained snapshots/backups of the attached volume before Aug 16.
Whether any platform maintenance or migration could have caused the service to regenerate its local n8n config.
Thank you.
1 Replies
a month ago
Your n8n service was affected by a host maintenance event on 2026-08-14 at 18:38 UTC, which migrated the workload to a healthy server and restarted the service. The deployment you cited was created on 2026-08-16 at 11:01 UTC as a result of that process. The volume mounted at /home/node/.n8n is still attached with ~148 MB of data, so the volume itself survived, but the restart is consistent with n8n auto-generating a new encryption key in its config file on startup. Regarding volume snapshots, restoring volume backups requires the Pro plan ($20/month), so no pre-Aug-16 restore point is available on Hobby.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago