Skip to content
Build consistently failing with BuildKit daemon connection error (4 consecutive failures)
schneidertimothy-cmd
OP

22 days ago

Project ID: a937dc48-7a30-4ebe-8bae-f8210a997ac0

Service ID: 02a78145-de06-41f5-885d-5f471f397904

Environment: production (de7998e2-daa8-46c2-9ec1-93a332e4b87d)

Issue: Every deployment attempt since ~19:26 UTC on 2026-10-28 has failed at the build stage with the identical error:

Build Failed: build daemon returned an error < listing workers for Build: failed to list workers: Unavailable: connection error: desc = "error reading server preface: raw-read unix @->/run/buildkit/buildkitd.sock: use of closed network connection" >

Deployment IDs affected (all identical error):

450f8581-e441-4d83-8565-451cc0f5beb9 (~19:36 UTC) — build succeeded but never rolled out to a running instance

7846f8ad-fd56-46b4-98e6-1eb95ba9fe38 (~19:42 UTC)

d72059db-5ee0-49f4-8ee0-345f58097ef9 (~19:46 UTC)

21304198-06ad-487c-b98d-578c74054982 (~19:47 UTC) — triggered via a fresh git push rather than the Railway redeploy API, same error

So this reproduces identically whether triggered via the Railway API (redeploy) or a GitHub webhook push — doesn’t appear to be specific to one trigger path.

Context: This started right around your “Deployments stuck in initializing” incident (identified 17:49 UTC, later marked resolved on status.railway.com) — possibly related fallout from that, or a separate issue in the same build pipeline.

Impact: The service itself is still running fine on its last successful deployment (no outage) — this only blocks shipping new code.

Request: Please check BuildKit daemon health for this project/service.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 22 days ago


22 days ago

Apologies for the disruption and the delay getting back to you. These build failures were caused by a transient issue with an upstream provider, which has since been resolved. We’re sorry this interrupted your releases.


Status changed to Awaiting User Response Railway • 22 days ago


Railway
BOT

3 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 3 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...