2 months ago
Deployment continues failing with “Failed to connect before the deadline” as the first and only deploy log line, after the August 18 deployment incident was resolved. No application container logs are produced.
Project ID : 23a5a38c-89e4-47fe-9ade-d28260eed194
Deployment ID: ef2f3e01
2 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Railway Diagnosis also fails for the deployment.
The frontend service from the same GitHub commit deployed successfully.
Please reset or inspect the stuck builder for this backend service.
Attachments
2 months ago
Your frontend deploying cleanly from the same commit actually confirms what's happening. The backend's failures started during Monday evening's incident (https://status.railway.com/incident/7M7CBL9X), and every backend attempt since then, including the one at 13:21, has been a redeploy of those broken deployments. A redeploy replays the same failed snapshot step each time, so it can never succeed, and there is no stuck builder to reset.
Push a fresh commit for the backend, even an empty one, exactly like the push that built your frontend. That creates a new deployment instead of replaying the broken one.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved trainixai26 • about 2 months ago