Can you share the logs?

The logs were too long, added a text file. Im going to dinner but will be back tomorrow. Hopefully that should be all of them

The attachment doesnt look like its working - here is most recent log (I think): You reached the start of the range

May 12, 2026, 5:19 PM

stage-0

FROM ghcr.io/railwayapp/nixpacks:ubuntu-1745885067@sha256:d45c89d80e13d7ad0fd555b5130f22a866d9dd10e861f589932303ef2314c7de

16ms

scheduling build on Metal builder "builder-grpkqg"

unpacking archive670 KB7ms

using build driver nixpacks-v1.41.0

uploading snapshot147.1 KB

╔═════════════════════ Nixpacks v1.41.0 ═════════════════════╗

║ setup │ nodejs_24, npm-9_x ║

║────────────────────────────────────────────────────────────║

║ caddy │ pkgs: caddy ║

║ │ cmds: caddy fmt --overwrite /assets/Caddyfile ║

║────────────────────────────────────────────────────────────║

║ install │ npm ci ║

║────────────────────────────────────────────────────────────║

║ build │ npm install && npm run build ║

║────────────────────────────────────────────────────────────║

║ start │ npm start ║

╚════════════════════════════════════════════════════════════╝

Saved output to:

snapshot-target-unpack

internal

load build definition from Dockerfile

0ms

internal

load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1745885067

336ms

internal

load .dockerignore

0ms

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "ANTHROPIC_API_KEY") (line 13)(https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/) details: Sensitive data should not be used in the ARG or ENV commands

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "JWT_SECRET") (line 13)(https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/) details: Sensitive data should not be used in the ARG or ENV commands

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "RESEND_API_KEY") (line 13)(https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/) details: Sensitive data should not be used in the ARG or ENV commands

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "ANTHROPIC_API_KEY") (line 14)(https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/) details: Sensitive data should not be used in the ARG or ENV commands

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "JWT_SECRET") (line 14)(https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/) details: Sensitive data should not be used in the ARG or ENV commands

SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "RESEND_API_KEY") (line 14)(https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/) details: Sensitive data should not be used in the ARG or ENV commands

UndefinedVar: Usage of undefined variable '$NIXPACKS_PATH' (line 24)(https://docs.docker.com/go/dockerfile/rule/undefined-var/) details: Variables should be defined before their use

internal

load build context

0ms

stage-0

RUN nix-env -if .nixpacks/nixpkgs-ba913eda2df8eb72147259189d55932012df6301.nix && nix-collect-garbage -d cached

0ms

stage-0

RUN nix-env -if .nixpacks/nixpkgs-23f9169c4ccce521379e602cc82ed873a1f1b52b.nix && nix-collect-garbage -d cached

0ms

stage-0

COPY .nixpacks/nixpkgs-23f9169c4ccce521379e602cc82ed873a1f1b52b.nix .nixpacks/nixpkgs-23f9169c4ccce521379e602cc82ed873a1f1b52b.nix cached

0ms

stage-0

WORKDIR /app/ cached

0ms

stage-0

COPY .nixpacks/nixpkgs-ba913eda2df8eb72147259189d55932012df6301.nix .nixpacks/nixpkgs-ba913eda2df8eb72147259189d55932012df6301.nix cached

0ms

stage-0

COPY .nixpacks/assets /assets/ cached

0ms

stage-0

COPY . /app/.

2s

stage-0

RUN caddy fmt --overwrite /assets/Caddyfile

3s

stage-0

COPY . /app/.

4s

stage-0

RUN npm ci

10s

Run npm audit for details.

stage-0

COPY . /app/.

6s

stage-0

RUN npm install && npm run build

8s

✓ built in 2.77s

stage-0

RUN printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile

993ms

stage-0

COPY . /app

2s

exporting to docker image format

5s

containerimage.descriptor: eyJtZWRpYVR5cGUiOiJhcHBsaWNhdGlvbi92bmQub2NpLmltYWdlLm1hbmlmZXN0LnYxK2pzb24iLCJkaWdlc3QiOiJzaGEyNTY6ZmNlZDE0N2ExZDA4NmVjZGMxMDAzOTQxNjAyODAzOGJiNWFlZmI4M2ZkMDMxNzQxZjQyZDgzN2ZlOGZmZGNlYSIsInNpemUiOjM3MTIsImFubm90YXRpb25zIjp7Im9yZy5vcGVuY29udGFpbmVycy5pbWFnZS5jcmVhdGVkIjoiMjAyNi0wNS0xMlQxNjoyNToyM1oifSwicGxhdGZvcm0iOnsiYXJjaGl0ZWN0dXJlIjoiYW1kNjQiLCJvcyI6ImxpbnV4In19

containerimage.config.digest: sha256:843672543927a94784f4db3483ff6f204e06a88a8463f7938306c1e68a2defcb

containerimage.digest: sha256:fced147a1d086ecdc10039416028038bb5aefb83fd031741f42d837fe8ffdcea

image push

428.1 MB / 428.2 MB

This is what the AI diagnostic says "This deployment failed at the container creation stage due to a persistent infrastructure issue. The build and image publish completed successfully, but Railway has been unable to create a container for this service for over 2 days across 12+ consecutive deployments. Please reach out to Railway support for help resolving this."

first try this go to service settings , deploy then region, pick a different one and redeploy

Just tried this, it didnt work, it got the same "This deployment failed at the container creation stage due to a persistent infrastructure issue. The build and image publish completed successfully, but container creation has been failing across 12+ consecutive deployments since May 10. Please reach out to Railway support to investigate."

this was the most recent diagnostic summary: I'll fetch the build failure log for you. Let me first check the environment status to identify which service has a failed build.

Checked environment status

Hide result

1 of 1 service with issues•2 recent failures

health-tracker

13

Offline

Now let me get the build logs for the most recent failed deployment:

Searched build logs: @level:error

Hide result

No logs found

Let me get the full build logs without filtering to see what happened:

Searched build logs

Hide result

22:51:42

22:51:42

22:51:42Saved output to:

22:51:42snapshot-target-unpack

22:51:43[internal] load build definition from Dockerfile

22:51:43[internal] load build definition from Dockerfile

22:51:43[internal] load build definition from Dockerfile

22:51:43[internal] load build definition from Dockerfile

22:51:43[internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1745885067

22:51:43[internal] load metadata for ghcr.io/railwayapp/nixpacks:ubuntu-1745885067

...and 90 more logs

The build logs show the build completed successfully. Let me get the deployment diagnosis to see what actually failed:

Diagnosed deployment

Build Status: The build itself completed successfully. The failure is at the container creation stage, not the build.

Root Cause: Infrastructure error. The deployment failed at CREATE_CONTAINER after the build and image publish succeeded. This has been happening consistently since May 10 across 12+ deployments, even with different commits.

Key Details:

• Build: ✓ Completed (npm ci, Vite build all successful)
• Image publish: ✓ Completed
• Container creation: ✗ Failed with "Failed to create deployment"
• Service has a volume mount at /app/data which may be related

Recommendation: This is a persistent infrastructure issue outside your control. Contact Railway support to investigate the container scheduling failure for this service.

can anyone at railway help me, that is the suggestion from Diagnostic tracker and ClaudeCode, that someone from Railway will have to understand what is wrong with their system as it’s not a code problem?

Has your problem been solved? I have got the same one