Healthcheck fails even if the site is properly deployed

Service url: https://railway.com/project/9f2865af-cba4-418d-b78f-cad8d04be1a4/service/2bf7a3d5-6ca5-4140-b151-801f0e95b894?environmentId=589300fa-08aa-46a4-91d8-ef71ad029541&id=1c550f10-8f7f-4ec2-a12d-b55edffbfa63#build

If I deploy without healthchecks, it deploys and works properly, I was using healthchecks for months now, they stopped working (not the website since it deploys without them) a few days ago.

$20 Bounty

1 Replies

Healthchecks are working fine for me , I tested with a fresh service.

  I deployed a minimal Node.js service with a healthcheck at /api/v1/health and it passes without issues.

  Screenshot:

  If your healthchecks are still failing, here's a quick checklist I follow :

  - Make sure your server binds to 0.0.0.0, not localhost or 127.0.0.1

  - Use the PORT environment variable provided by Railway (process.env.PORT)

  - Ensure your health endpoint returns a 200 status code immediately (no auth, no heavy logic)

  - Check if your app actually starts before the healthcheck retry window expires large images (400MB+) with slow startup can

  timeout

  - After an outage, try a full redeploy (not just restart) to clear stale build cache

  - Increase your healthcheck timeout if your app needs more startup time (Settings → Deploy → Healthcheck Timeout)

  This was likely caused by the outage leaving services in a stale state, or a slow-starting app timing out within the retry

  window.

my code for testing https://github.com/dharmateja03/railway-bounty-testing
deployment :
railway-bounty-testing-production.up.railway.app


Loading...