14 days ago
I need it back. I said not to erase, but it did it selves. Its a retaiable-volume. And it cleans all of it. I had almost 500 clients.
-
- Volume
reliable-2026-04-29 21:11 UTCwas accidentally deleted - date and time that was deleted: 2026-05-04
- Volume
- Project ID:
ecfbe528-5531-47ec-87af-93f342a0e3fc
2 Replies
14 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 14 days ago
14 days ago
Description:
MongoDB service (mongo:7) fails in both regions
Error: "recurring infrastructure issue during container creation"
Configuration is valid (worked before)
Volume restored from backup
Project: ecfbe528-5531-47ec-87af-93f342a0e3fc
Environment: production
Urgency: Production database down
Mention that you have already tried redeploying and changing regions
an hour ago
For the volume: Railway doesn't expose snapshot restoration in the dashboard.
Open a support ticket at help.railway.com immediately with your project ID (ecfbe528-5531-47ec-87af-93f342a0e3fc) and the exact volume name reliable-2026-04-29 21:11 UTC.
Retainable volumes may have internal block-level backups that only Railway's infra team can restore — the sooner you escalate, the better.
For MongoDB failing: The error "recurring infrastructure issue during container creation" is Railway-side, not your config. Steps:
- Check status.railway.com for active incidents.
- Delete only the MongoDB service (not the volume), recreate it, and reattach the volume to /data/db.
- Pin your image to mongo:7.0.8 instead of mongo:7 to avoid a bad pull.
- If that fails, temporarily detach the volume and deploy ephemeral Mongo — if it boots, the issue is volume-attachment-specific, which again needs Railway support escalation.