2 months ago
Hello! I´ve tried a lot of thing and still
BUILD LOGS:
[Region: us-west1]
==============
Using Nixpacks
==============
context: h9mm-
╔════════ Nixpacks v1.38.0 ═══════╗
║ setup │ nodejs_20, npm-9_x ║
║─────────────────────────────────║
║ install │ npm ci ║
║─────────────────────────────────║
║ build │ npm run build ║
║─────────────────────────────────║
║ start │ npm run start ║
╚═════════════════════════════════╝
internal
load build definition from Dockerfile
0ms
internal
load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1745885067
311ms
internal
load .dockerignore
0ms
internal
load build context
0ms
stage-0
WORKDIR /app/ cached
0ms
stage-0
COPY .nixpacks/nixpkgs-ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.nix .nixpacks/nixpkgs-ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.nix cached
0ms
stage-0
RUN nix-env -if .nixpacks/nixpkgs-ffeebf0acf3ae8b29f8c7049cd911b9636efd7e7.nix && nix-collect-garbage -d cached
0ms
stage-0
COPY . /app/.
165ms
stage-0
RUN npm ci
20s
Run npm audit for details.
stage-0
COPY . /app/.
392ms
stage-0
RUN npm run build
39s
ƒ (Dynamic) server-rendered on demand
stage-0
RUN printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile
104ms
stage-0
COPY . /app
110ms
importing to docker
18s
auth
sharing credentials for production-us-west2.railway-registry.com
0ms
=== Successfully Built! ===
Run:
docker run -it production-us-west2.railway-registry.com/7e982f6d-bfd7-4e5c-87b2-ae1d8729d9e1:1dbde6d1-8eb0-4d1b-8c7b-eb66d938ca2c
Build time: 166.13 seconds
==================== Starting Healthcheck ====================
Path: /api/health
Retry window: 5m0s
[1/1] Healthcheck succeeded!
DEPLOY LOGS:
Starting Container
npm warn config production Use --omit=dev instead.
> backoffice-frontend@0.1.0 start
> next start -H 0.0.0.0 -p ${PORT:-3000}
▲ Next.js 15.0.7
- Local: http://localhost:8080
- Network: http://0.0.0.0:8080
✓ Starting...
✓ Ready in 711ms
Attachments
1 Replies
2 months ago
Your backoffice-front-dev service built and deployed successfully, the healthcheck passed, and it is currently in a running state listening on port 8080. Since the app is reachable during healthchecks but returning 502 on browser requests, the most likely cause is a target port mismatch on your domain backoffice-front-development.up.railway.app. You can verify and update the target port by clicking the edit icon next to the domain under your service's Settings > Networking > Public Networking, and ensuring it is set to 8080 as described in our domain target ports docs.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved co-fa • about 2 months ago