when i deploy everytime it say healthcheck failed
Anonymous
FREEOP

a month ago

UN apt-get update && apt-get install -y --no-install-recommends nodejs npm && rm -rf /var/lib/apt/lists/*

24s

Processing triggers for libc-bin (2.41-12+deb13u1) ...

builder

COPY frontend ./frontend

132ms

builder

WORKDIR /app/frontend

12ms

builder

RUN npm install --legacy-peer-deps && npm run build || echo "Frontend build optional"

44s

https://cra.link/deployment

stage-1

COPY --from=builder /root/.local /root/.local

1s

stage-1

COPY backend ./backend

79ms

stage-1

COPY .env.example .env.example

13ms

stage-1

RUN mkdir -p ./frontend/build

114ms

stage-1

COPY --from=builder /app/frontend/build ./frontend/build

19ms

stage-1

RUN mkdir -p /etc/nginx/conf.d

99ms

stage-1

COPY frontend/nginx.conf /etc/nginx/conf.d/default.conf

24ms

stage-1

COPY entrypoint.sh /app/entrypoint.sh

97ms

stage-1

RUN chmod +x /app/entrypoint.sh

118ms

stage-1

RUN mkdir -p /tmp/ai_video_editor /app/temp /app/ai_engine/models

91ms

auth

sharing credentials for production-us-west2.railway-registry.com

0ms

importing to docker

6s

Build time: 152.54 seconds

==================== Starting Healthcheck ====================

Path: /health

Retry window: 10s

1/1 replicas never became healthy!

Healthcheck failed!

$10 Bounty

2 Replies

1.make sure the port your server listens on is the same port Railway is routing to .
2.make sure healthcheck path is correct

3.Is your app listening on localhost (127.0.0.1) instead of 0.0.0.0?


lu4p
FREETop 10% Contributor

a month ago

Set env var PORT for the service to the port your app is listening on


Loading...