Railway deployment healthy but public domain returns 502
sania-ali
FREEOP

9 days ago

Sir, I’m getting a 502 Bad Gateway after deployment even though Railway shows the deployment as healthy. My app listens on PORT=8080, and the healthcheck returns 200, but the public domain still shows connection refused. What fixed it was checking Service Settings → Networking and changing the public-domain target port from 3000 to the actual runtime port 8080.

Solved

1 Replies

Railway
BOT

9 days ago

That's correct, the public domain's target port must match the port your application actually listens on. Glad you got it sorted.


Status changed to Awaiting User Response Railway 9 days ago


Status changed to Solved sania-ali 8 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...