Healthchecks failing
curiouskal
PROOP

25 days ago

2 of my services have been failing to deploy for the last 1-2 hours with multiple attempts (ever since the massive outage and recovery).

I am running the same code (linked to same github repo) on 2 other services within the same project, and they built fine, so I'm very confused what the issue is.

Solved

4 Replies

Railway
BOT

25 days ago

Your "api-server-trial" and "api-worker-trial" services are failing because they cannot connect to Redis (repeated ETIMEDOUT errors from ioredis during startup), which causes the healthcheck to never pass. This is consistent with lingering impact from the earlier service disruption that was resolved at 07:57 UTC. Your "paid" service variants recovered, but the "trial" ones appear stuck in a failure loop. Triggering a fresh redeploy of both services should resolve the issue now that connectivity has been restored.


Status changed to Awaiting User Response Railway 25 days ago


curiouskal
PROOP

25 days ago

i've already been triggering redeploys, they have been failing consistently on the two 'trial' services.

I also made a temp "forcebuild.md" file in the backend app code inside the monorepo just so it would rebuild and deploy, and even then this issue is persisting.


Status changed to Awaiting Railway Response Railway 25 days ago


Railway
BOT

25 days ago

We can confirm your trial services are still hitting Redis connection timeouts as of 12:34 UTC, which is lingering impact from the earlier service disruption. Your redis-trial service itself hasn't been redeployed since April 14 - try redeploying redis-trial (not just the app services) to re-establish the private network connectivity, since Wireguard tunnels are set up per-deployment.


Status changed to Awaiting User Response Railway 25 days ago


curiouskal
PROOP

25 days ago

yes, i redeployed the redis service. that fixed the issue. much appreciated!


Status changed to Awaiting Railway Response Railway 25 days ago


Status changed to Solved curiouskal 25 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...