9 days ago
Build fails on my deployment.
The build failed because the assigned build daemon's gRPC connection closed unexpectedly before any build steps could run. This same error occurred across 6 consecutive deployment attempts over 20 minutes, with no changes to code or configuration involved.
Here are the logs :
You reached the start of the range
Jun 28, 2026, 11:56 AM
unpacking archive2.6 MB29ms
uploading snapshot544.4 KB
using build driver railpack-v0.30.0
INFO No package manager inferred, using npm default
╭─────────────────╮
│ Railpack 0.30.0 │
╰─────────────────╯
↳ Detected Node
↳ Custom start command detected, skipping Caddy start
↳ Custom start command detected, skipping Caddy start
↳ Using npm package manager
↳ Custom start command detected, skipping Caddy start
Packages
──────────
node │ 22.22.3 │ railpack default (22)
Steps
──────────
▸ install
$ npm ci
▸ build
$ npm run build
Deploy
──────────
$ npm run start Build Failed: build daemon returned an error < failed to solve: frontend grpc server closed unexpectedly >
sc
Deployment id : 5385e35e-9ccb-4827-8053-fe9ba13fc138
Pinned Solution
9 days ago
Try to set NO_CACHE=1 in your service variables. This might be caused by a caching issue. You can Also try to trigger a new deployment by pressing CTRL+K then select deploy latest commit.
1 Replies
9 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 9 days ago
9 days ago
Try to set NO_CACHE=1 in your service variables. This might be caused by a caching issue. You can Also try to trigger a new deployment by pressing CTRL+K then select deploy latest commit.
Status changed to Solved medim • 6 days ago