4 hours ago
Hi Railway community,
I'm experiencing a deployment failure with an n8n service on the Hobby plan.
Configuration:
- Docker image:
n8nio/n8n:latest - Region: US East
- Persistent Railway volume attached
- No custom Dockerfile
The deployment successfully completes initialization but gets stuck at Deploy → Create container for approximately 26 minutes before failing.
The error is:
"An unknown error occurred."
Railway's automated diagnosis classifies this as an Infrastructure Error. No build or runtime logs are available.
The previous GitHub-source deployment exceeded the 4 GB image limit, so I switched to the prebuilt Docker Hub image.
Has anyone encountered this issue, particularly with persistent volumes? Could it be related to container scheduling or volume mounting?
I'd appreciate any suggestions for resolving it without changing plans or deleting the volume.
Thanks!
1 Reply
4 hours ago
We're sorry for the trouble. Your failure matches an open incident where deployments are failing or getting stuck for some users, including US East builds, and its current status is Identified. You can follow updates at Deployments are failing for some users.
There's no need to change plans or delete your volume for this.
Status changed to Awaiting User Response Railway • about 4 hours ago