a month ago
Since the outage and even now, cannot redeploy.
Redeployed/Restarted, and nothing.
I am getting these in my logs:
Attempt #6 failed with service unavailable. Continuing to retry for 8s
==================== Starting Healthcheck ====================
Path: /api/v1/health
Retry window: 1m40s
Attempt #1 failed with service unavailable. Continuing to retry for 1m29s
Attempt #2 failed with service unavailable. Continuing to retry for 1m18s
image push435.7 MB9.7s
Attempt #3 failed with service unavailable. Continuing to retry for 1m6s
Attempt #4 failed with service unavailable. Continuing to retry for 52s
Attempt #5 failed with service unavailable. Continuing to retry for 34s
Attempt #6 failed with service unavailable. Continuing to retry for 8s
1/1 replicas never became healthy!
Healthcheck failed!
1 Replies
a month ago
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
Attachments