2 years ago
Been using the same build but during docker build it keeps retrying but unable to reach service
"Attempt #1 failed with service unavailable"
ⓘ Deployment information is only viewable by project members and Railway employees.
5 Replies
brody
Hello, Please check the deployment logs, your app never started.
2 years ago
This is a working build: https://railway.com/project/52b44fed-61b5-47d4-90cd-58ad55a0b2cf/service/b8fee395-d888-453b-9553-c05071e22d56?environmentId=c92bc494-72ff-4aaf-9442-848ec6b6747d&id=bbe2079f-d3fd-412b-b718-20023c353f60
This is a same build but failed: https://railway.com/project/52b44fed-61b5-47d4-90cd-58ad55a0b2cf/service/b8fee395-d888-453b-9553-c05071e22d56?environmentId=c92bc494-72ff-4aaf-9442-848ec6b6747d&id=6cc92d11-dd57-4968-bec6-ff18c64ccb87#build
What I did is to try to redeploy the build.
2 years ago
Yep but if the app doesn't start, there is no app to answer the health check, and thus the health check will fail, so please see your deployment logs for the error that is preventing your app from starting.
brody
Yep but if the app doesn't start, there is no app to answer the health check, and thus the health check will fail, so please see your deployment logs for the error that is preventing your app from starting.
2 years ago
Thanks! It helps a lot!