Eternal Healthcheck failure
mfvas
PROOP

9 months ago

For the last 17 hours, all my deployments fail with the same "Healthcheck failure."

I didn't make any changes that would cause this. The health route works in dev, on the latest version, and in production with the older deployment.

I'm pretty sure it's a Railway problem, because:

  1. Everything works fine in both dev and when building and running the start script locally on my machine.

  2. I tried removing the healthcheck. Then, the deployment works fine, but the app doesn't work for some reason. No errors, I just can't access the app. It keeps loading.

  3. Then I rolled back to the last working deployment and the app perfectly fine again.

  4. Then I added the healthcheck back, and the deployment fails again with a "Healthcheck failure" on the same older deployment that works in step 2. So it's NOT isolated to changes on the newer deployments.

Coincidentally, I also got a cloudflare bad gateway error in the project admin panel while writing this.

Logs:

=== Successfully Built! ===

Run:

docker run -it REDACTED

====================

Starting Healthcheck

====================

Path: /health

Retry window: 5m0s

Attempt #1 failed with status 404. Continuing to retry for 4m59s

Attempt #2 failed with status 404. Continuing to retry for 4m58s

Attempt #3 failed with status 404. Continuing to retry for 4m56s

Attempt #4 failed with status 404. Continuing to retry for 4m52s

Attempt #5 failed with status 404. Continuing to retry for 4m44s

Attempt #6 failed with status 404. Continuing to retry for 4m27s

Attempt #7 failed with status 404. Continuing to retry for 3m57s

Attempt #8 failed with status 404. Continuing to retry for 3m27s

Attempt #9 failed with status 404. Continuing to retry for 2m57s

Attempt #10 failed with status 404. Continuing to retry for 2m26s

Attempt #11 failed with status 404. Continuing to retry for 1m56s

Attempt #12 failed with status 404. Continuing to retry for 1m26s

Attempt #13 failed with status 404. Continuing to retry for 55s

Attempt #14 failed with status 404. Continuing to retry for 25s

1/1 replicas never became healthy!

Healthcheck failed!

Solved

1 Replies

brody
EMPLOYEE

9 months ago

Hello,

I have reverted the Nixpacks version and your latest deployment has gone live!

Best,
Brody


Status changed to Awaiting User Response Railway 9 months ago


Status changed to Solved brody 9 months ago


Loading...