ID 84818c19-a210-4dc2-93d2-f12b6f6c08c3.
oronico
PROOP

a month 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

Solved$20 Bounty

Pinned Solution

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 about 1 month ago


What exaclty is the error displayed in your logs?


Status changed to Awaiting User Response Railway about 1 month ago


oronico
PROOP

a month ago

Screenshot 2026-05-19 at 2.05.30 PM.png

Attachments


Status changed to Awaiting Railway Response Railway about 1 month 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


oronico
PROOP

a month ago

Easy Peasy! Thank you, and sorry for the stupid question! (Beginner here)


Status changed to Solved 0x5b62656e5d about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...