2 days ago
Title: Postgres stuck at "Create container" then FAILED – volume with no backups
Project: infra-n8n (67f339ea-691b-4dd0-88e0-f4d17a8c051d), environment: production
Service: Postgres (2c89c354-b624-4086-8c4b-c0f94cdd2ec4)
Image: ghcr.io/railwayapp-templates/postgres-ssl:16
Volume: postgres-volume (38acf4e9-53b2-4540-9876-2f2387e82916), 5 GB, us-east4, idle since 2026-03-30
Deployment: ee233ace-ecc7-457f-be1c-c72090d30536
Redeploy started 2026-10-15 16:43 UTC, stayed ~26 min at Deploy > Create container, then FAILED with "An unknown error occurred". No build or deploy logs, no automatic diagnosis. Redis in the same project redeployed fine at the same time. Variables are complete and billing is up to date.
The volume has NO backups and holds our production n8n data. Please bring the container up with the existing volume intact. Do not recreate or wipe the volume.
3 Replies
Status changed to Awaiting Railway Response Railway • 2 days ago
2 days ago
The deployment failed while its container was still being created, so your Postgres image never started. That is why there are no build or deploy logs and no diagnosis to show. The failure did not come from your variables, image, or billing.
This deployment did not recreate, wipe, or modify the postgres-volume volume. Its data stays in place and the volume is still attached to the Postgres service.
Status changed to Awaiting User Response sam-a • 2 days ago
2 hours ago
Ta mas como resolve isso entao?
Status changed to Awaiting Railway Response Railway • about 2 hours ago
2 hours ago
Apologies, we only correspond in English. Please open a new thread in English.
Status changed to Closed Railway • about 2 hours ago