2 months ago
My Postgres service has been failing to deploy for a long time. The deployment always fails during the pre-deploy step with the error "Volume migration failed". The service never starts, so there are no deploy logs available.
Issue details:
- Deployment ID: c63a9920
- Image: ghcr.io/railwayapp-templates/postgres-ssl:latest
- Region: us-west1 (Legacy)
- Error: "Deployment failed during pre-deploy process" → "Pre-deploy › Migrate volumes" → "Volume migration failed."
- There is also a warning saying the deployment configuration was automatically modified to ignore deprecated regions, but the migration still fails.
I am on the Free plan, so I do not have access to backups or the ability to change the region manually.
The data stored in this volume belongs to an academic project and is important to me. I am not able to access it in any way since the service never comes online.
Could anyone from the Railway team or the community help me either migrate the volume to an active region, or advise on how to obtain a database dump (.sql) of the data stored in the volume? Any help is appreciated.
5 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
There are no Postgres deployments belonging to the account you are currently communicating with.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
I apologize for the confusion. The project belongs to another account and I am a collaborator on it. Here is the project ID for reference: f02c4f9b-4370-4412-ba12-14f33572fe3d.
Could you please look up the Postgres service and the volume migration issue using this project ID?
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Thank you for the fix! The region is now showing us-west2 in the deployment details, which is progress. However, the deployment is still failing at the same step: "Pre-deploy › Migrate volumes" → "Volume migration failed." It seems the volume data itself could not be migrated from the legacy infrastructure. Could you help with migrating the volume data as well, or provide a database dump (.sql) of its contents?
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
The data for this database is gone; it was left on an unpaid account long past our standard data retention period.
Status changed to Awaiting User Response Railway • 2 months ago
2 months 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 2 months ago