a month ago
Production API is down. Every new deployment of service "schedapro" (domain api.schedapro.it, region EU West, 1 replica) fails in about 1 second at "Deploy > Pre deploy command", before the container is created. Build and initialization succeed.
Error:
This deployment expects a volume mounted at /data/uploads, but the service has no volume attached. Railway did not create the container: it would have run without the volume, and data written there is lost on the next deploy. Attach a volume at /data/uploads, or remove the mount, and deploy again.
The volume is attached in the dashboard:
- Volume name: schedapro-volume
- Size: 500 MB
- Mount path: /data/uploads
- Volume Settings > Connection says this path is mounted in service "schedapro"
- On the canvas, schedapro-volume is nested under the schedapro service
- Service variable UPLOADS_DIR=/data/uploads
- Postgres uses a different volume (postgres-volume) and is still online
What we already tried:
- Redeploy of the failed deployment (example: a10c9a20, 2026-10-06 23:16 GMT+2)
- Redeploy of a deployment that succeeded about 4 hours ago. It now fails with the same error, so this is not caused by the latest commit
- Railway Diagnose, which repeats "attach a volume at /data/uploads" even though the volume is already attached
Current impact:
- Service status: Offline
- GET https://api.schedapro.it/livez returns HTTP 404 {"status":"error","code":404,"message":"Application not found"} with header x-railway-fallback: true
- There is no running deployment to roll back to
Please reconcile the volume attachment for schedapro-volume on /data/uploads and redeploy the last successful deployment. Do not delete the volume: it holds user avatars and admin-uploaded images. If a stale or duplicate volume instance is attached to this service, remove only that stale instance and leave the live data in place.
1 Reply
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hey! Thanks for the detailed report. This was caused by a recent change on our side, and we've now rolled it back. Deploys with a volume and a pre-deploy command should go through again, so please redeploy and your volume will be mounted as usual. Your volume and its data weren't affected.
If you detached your volume or deployed without it while this was happening, reply here before redeploying and we'll help make sure nothing written since then gets lost.
Sorry for the disruption, and let us know if anything still fails.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved gterribilio • about 1 month ago