2 hours ago
Hello Railway Support,
An n8n service ran as root and auto-generated its encryption key in /root/.n8n/config, while its Railway volume was mounted at /home/node/.n8n. After redeployment, the runtime-only config disappeared. PostgreSQL and workflows remain, but n8n fails with: Deployment key 'signing.hmac' cannot be read with this instance encryption key.
The old deployment is too old for rollback, redeploying it did not restore the file, and no volume backup exists. Logs confirm: No encryption key found - Auto-generating and saving to: /root/.n8n/config.
Could Railway staff check for any retained runtime filesystem snapshot from before the redeploy and recover /root/.n8n/config or its encryptionKey? Please do not modify or delete the PostgreSQL database or volumes. The affected service is selected below.
Thank you.
1 Reply
2 hours ago
The n8n service's only volume is mounted at /home/node/.n8n, so /root/.n8n/config sat on the container's own filesystem, which is temporary and is replaced on every redeploy. Retrieving files from a previous container's filesystem isn't something we're able to do, so the original encryption key can't be recovered from our side.
Only data written under the volume's mount path carries over between deployments.
Status changed to Awaiting User Response Railway • about 2 hours ago