25 days ago
Same commit (87740eb) has failed 5 out of 6 times with identical healthcheck routing failures
App builds, starts, and listens on port 8080 correctly
Migrations run successfully (database connection works)
But the healthcheck proxy can't reach the container
No code or config changes between deployments
Pinned Solution
25 days ago
Add PORT=8080 to your service variables. Because healthchecks use the PORT variable to know what port your app is listening on. If your app is running, and listening on port 8080, then that's all you need to do.
You can read more about it here: https://docs.railway.com/deployments/healthchecks#configure-the-healthcheck-port
4 Replies
Status changed to Open Railway • 25 days ago
Status changed to Awaiting User Response Railway • 25 days ago
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
Add PORT=8080 to your service variables. Because healthchecks use the PORT variable to know what port your app is listening on. If your app is running, and listening on port 8080, then that's all you need to do.
You can read more about it here: https://docs.railway.com/deployments/healthchecks#configure-the-healthcheck-port
25 days ago
Easy Peasy! Thank you, and sorry for the stupid question! (Beginner here)
Status changed to Solved 0x5b62656e5d • 24 days ago