Service exits immediately with no deploy logs (even minimal probe app)
rajat-srivas
HOBBYOP

10 months ago

I’m facing an issue where a Railway service exits immediately at runtime without producing any deploy logs, even though the build succeeds.

What’s happening:

  • Build succeeds (npm ci, npm run build, tsc)
  • Start command runs (npm start)
  • App returns 502
  • No deploy/runtime logs at all (stdout/stderr never attach)

Key debugging steps already done:

  • Verified correct start command (npm start)
  • Verified correct port binding (process.env.PORT, 0.0.0.0)
  • Pinned Node to 18.20.8
  • Environment variables are present
  • Removed any process.exit or early exits
  • Deployed a minimal probe app (10-line Express server with a single route and console logs)

Can it be verified if there are envrionment curroption issue or if any backend logs can be shared which are not visible on UI

Thanks

$10 Bounty

2 Replies

10 months ago

Hey, can you share the public repo of the minimal probe app?


fra
HOBBY

10 months ago

Can you check if the port exposed by the app matches the port used in Settings->Public Network? Usually it is 8080 but the important is that the 2 ports matches


Welcome!

Sign in to your Railway account to join the conversation.

Loading...