a month ago
Hello Railway Support,
Our production STARK service is unavailable following a deployment that failed during container creation.
Project: energetic-courtesy
Service ID: da9f7f95-b78a-4256-bde1-af89fe8eb41e
Environment: production
Region: ams
Failed deployment: 1863f1b9-a22d-4c42-8201-d20a50dd6564
Previous successful deployment: 0a25c548-f881-48fe-a305-2a74c6755528
The failed deployment completed image building and publishing but became stuck at CREATE_CONTAINER.
Our subsequent checks found:
- Public endpoints return HTTP 502.
- The container reports stopping or stopped.
- SSH access is unavailable.
- The production volume, stark-volume, reports Ready but cannot be accessed.
- SFTP attempts fail with "Failed to initialize SFTP session" and timeout errors.
- The Railway dashboard reports an online replica, conflicting with direct runtime and HTTP checks.
The volume is mounted at /app/data and contains production prospect, outreach, and SQLite databases.
Please investigate and restore the existing service and volume data path without deleting, recreating, detaching, or overwriting the production volume.
We cannot safely deploy, restore, or reconcile our databases until access is recovered and a verified backup is created.
Please advise whether this is a container scheduling or volume attachment issue and what recovery action is safest.
Thank you.
1 Reply
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We've cleared the stale state left by the previous STARK deployment, which was blocking the new one from starting. Your stark-volume was not detached, recreated, or modified.
You can redeploy the service now.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 1 month ago