6 months ago
On first deployment, it deploys.
Next, nothing happens anymore.
Run:
docker run -it production-asia-southeast1-eqsg3a.railway-registry.com/6d8c88fa-466e-4dff-8e77-cd862ef83d0d:8ad3d1e0-b5c0-478c-b731-8c9e1ff8089f
Build time: 119.39 seconds
====================
Starting Healthcheck
====================
Path: /api/health
Retry window: 1m0s
Attempt #1 failed with service unavailable. Continuing to retry for 49s
Attempt #2 failed with service unavailable. Continuing to retry for 37s
Attempt #3 failed with service unavailable. Continuing to retry for 25s
Attempt #4 failed with service unavailable. Continuing to retry for 11s
1/1 replicas never became healthy!
Healthcheck failed!
4 Replies
6 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
6 months ago
Apologies but this looks like an issue with the application level code. Due to volume, we can only answer platform level issues.
I've made this thread public so that the community might be able to help with you query.
Status changed to Awaiting User Response Railway • 6 months ago
6 months ago
Is the application even running ?
Did you specify a run script in the start command ?
6 months ago
I found solution.
Well, it's a ladder of constant self-disappointment.
First is I disable/skip health check in .toml file and voila, it deploys successfully.
But upon checking, I can't visit the site. Thus, health check fails from the start
Turns out it's a problem with next start and start and standalone serverless stuff.
I mixed up my outdated knowledge with them and contradicted containerization.
It's all good now but thank you guys.
Status changed to Solved convert-toint32 • 6 months ago
