24 days ago
0 days or $0.58 left credits so why my build failed ?
Pinned Solution
24 days ago
Your healthcheck is failing, that is a post-build step.
Make sure your app is listening on the PORT env var, and if you have a hardcoded port, add a PORT env var with that value to your service.
6 Replies
Status changed to Open Railway • 24 days ago
24 days ago
can you share some logs?
24 days ago
i don't see green connection to share logs
fra
can you share some logs?
24 days ago
[Region: asia-southeast1]
=========================
Using Detected Dockerfile
=========================
context: 02nz-hgSM
internal
load build definition from Dockerfile
0ms
internal
load metadata for docker.io/library/node:24-alpine
1s
auth
library/node:pull token for registry-1.docker.io
0ms
internal
load .dockerignore
0ms
internal
load build context
0ms
1
5ms
5
RUN npm install --omit=dev --legacy-peer-deps cached
0ms
4
COPY .npmrc* ./ cached
0ms
3
COPY package*.json ./ cached
0ms
2
WORKDIR /app cached
0ms
6
COPY . .
30ms
auth
sharing credentials for production-asia-southeast1-eqsg3a.railway-registry.com
1ms
importing to docker
7s
Build time: 10.48 seconds
==================== Starting Healthcheck ====================
Path: /api/health
Retry window: 5m0s
Attempt #1 failed with service unavailable. Continuing to retry for 4m49s
Attempt #2 failed with service unavailable. Continuing to retry for 4m38s
Attempt #3 failed with service unavailable. Continuing to retry for 4m26s
Attempt #4 failed with service unavailable. Continuing to retry for 4m12s
Attempt #5 failed with service unavailable. Continuing to retry for 3m54s
Attempt #6 failed with service unavailable. Continuing to retry for 3m28s
Attempt #7 failed with service unavailable. Continuing to retry for 2m48s
Attempt #8 failed with service unavailable. Continuing to retry for 2m8s
Attempt #9 failed with service unavailable. Continuing to retry for 1m28s
Attempt #10 failed with service unavailable. Continuing to retry for 48s
Attempt #11 failed with service unavailable. Continuing to retry for 8s
1/1 replicas never became healthy!
Healthcheck failed!
24 days ago
Your healthcheck is failing, that is a post-build step.
Make sure your app is listening on the PORT env var, and if you have a hardcoded port, add a PORT env var with that value to your service.
24 days ago
Free plan deployments must be serverless. Please go to your service settings and turn on the serverless flag.
Agent usage limit reached. Update your limit to continue usage.Update limit
medim
Your healthcheck is failing, that is a post-build step. Make sure your app is listening on the `PORT` env var, and if you have a hardcoded port, add a `PORT` env var with that value to your service.
24 days ago
it's working now thanks man
Status changed to Open brody • 24 days ago
Status changed to Solved brody • 24 days ago