a month ago
My n8n service crashed repeatedly with "Out of Memory (OOM)" errors about 24 days ago, and Railway automatically removed the deployment ("Deployment was removed because it's been crashed for too long"). At that point my account's trial had expired.
I just upgraded to the Hobby plan (payment confirmed, card on file) and redeployed the service. The redeploy succeeded, but the n8n instance came back completely empty — no workflows, no credentials, prompting a fresh "Set up owner account" screen as if it were a brand new install.
Questions:
- Is there ANY way to recover the data from before the deployment was removed (e.g. a snapshot, backup, or the underlying filesystem of the removed deployment)? This service did not have a persistent Volume attached (confirmed no Volumes section in Settings), so I assume the SQLite data lived on the deployment's ephemeral filesystem — but I want to confirm before giving up on recovery.
- The service is now showing "502 Bad Gateway" again shortly after this fresh redeploy, even with no workflows/data yet. Can you check the deploy logs / memory metrics for this service to see why it's unstable again on an empty instance?
This is a production automation service and the data loss is significant, so any guidance on recovery options would be very helpful.
1 Replies
a month ago
Your n8n service has no volume attached, and there are no detached or orphaned volumes in the project, so the SQLite data only ever existed on the container's ephemeral storage. That storage is discarded on every redeploy and cannot be recovered. Going forward, attaching a volume to the service will persist n8n's data across redeploys.
Regarding the 502 errors, the service's container is refusing connections, which points to n8n itself not starting or not binding its port correctly rather than a platform-side issue. The OOM crashes you saw previously suggest n8n may need its memory allocation reviewed.
Status changed to Awaiting User Response Railway • about 2 months 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