a year ago
I have not been able to build my workers instance as it healthcheck is failing
Build Error output'''
Path: /health
Jun 14 16:54:16
Retry window: 5m0s
Jun 14 16:54:16
Jun 14 16:54:16
Attempt #1 failed with service unavailable. Continuing to retry for 4m59s
Jun 14 16:54:17
Attempt #2 failed with service unavailable. Continuing to retry for 4m58s
Jun 14 16:54:19
Attempt #3 failed with status 404. Continuing to retry for 4m56s
Jun 14 16:54:23
Attempt #4 failed with status 404. Continuing to retry for 4m52s
Jun 14 16:54:31
Attempt #5 failed with status 404. Continuing to retry for 4m44s
Jun 14 16:54:47
Attempt #6 failed with status 404. Continuing to retry for 4m28s
Jun 14 16:56:17
Attempt #9 failed with status 404. Continuing to retry for 2m58s
Jun 14 16:57:48
Attempt #12 failed with status 404. Continuing to retry for 1m27s
Jun 14 16:58:18
Attempt #13 failed with status 404. Continuing to retry for 57s
Jun 14 16:58:48
Attempt #14 failed with status 404. Continuing to retry for 27s
Jun 14 16:58:48
Jun 14 16:58:48
1/1 replicas never became healthy!
Jun 14 16:58:48
Healthcheck failed!"""
3 Replies
a year ago
Been seeing this as well on basic Strapi/Postgres template deployment as well - where my path is:
Path: /admin
and same timeout response:
1/1 replicas never became healthy!
Healthcheck failed!
I am fairly new to railway, but have successfully deployed a strapi app here before. Is this service wide or template/app specfic?
a year ago
Your issue is a bit different since your logs are consistently service unavailable, where as OP has a 404 meaning there is a misconfiguration somewhere on their side.