a year ago
Hello! I recently opened a new strapi/ postgres app via this template: https://railway.app/template/strapi
Strapi Build logs time out and fail due to the health check service being unavailable. Postgres builds and deploys fine!
I am new to Railway and am wondering if this is an issue with Railway or the template itself? I haven't seen any raised issues on their repository. I recently had another deployment of the same server and it was working fine.
Any help would be greatly appreciated
Error I am receiving:
====================
Starting Healthcheck
====================
Path: /admin
Retry window: 5m0s
Attempt #1 failed with service unavailable. Continuing to retry for 4m59s
Attempt #2 failed with service unavailable. Continuing to retry for 4m58s
Attempt #3 failed with service unavailable. Continuing to retry for 4m56s
Attempt #4 failed with service unavailable. Continuing to retry for 4m52s
Attempt #5 failed with service unavailable. Continuing to retry for 4m44s
Attempt #6 failed with service unavailable. Continuing to retry for 4m28s
Attempt #7 failed with service unavailable. Continuing to retry for 3m58s
Attempt #8 failed with service unavailable. Continuing to retry for 3m28s
Attempt #9 failed with service unavailable. Continuing to retry for 2m58s
Attempt #10 failed with service unavailable. Continuing to retry for 2m28s
Attempt #11 failed with service unavailable. Continuing to retry for 2m28s
Attempt #12 failed with service unavailable. Continuing to retry for 1m58s
Attempt #13 failed with service unavailable. Continuing to retry for 1m27s
Attempt #14 failed with service unavailable. Continuing to retry for 57s
Attempt #15 failed with service unavailable. Continuing to retry for 27s
1/1 replicas never became healthy!
Healthcheck failed!
ⓘ Deployment information is only viewable by project members and Railway employees.
3 Replies
a year ago
This is due to a caveat (that will be fixed) with the v2 runtime that Railway enables by default for new deployments, deployments have to listen on IPv6 in order to pass the heath check where as they didn't need to listen on IPv6 to pass the health check on the legacy runtime.
The fix for now would be to configure strapi to listen on :: or switch back to the legacy runtime in your service settings.
a year ago
thank you for the heads up! both fixes are working for now!
a year ago
I'll see about making a PR to the strapi template to have it listen on :: because I would imagine that it would be beneficial regardless of this bug in v2.