2 months ago
Project ID: b74ef3b4-071c-4680-9fb9-d856fa6f26e2
Environment ID: a8346d6e-9fce-4187-a921-8ab0b9e8bf38
Service ID: 7727849b-3573-46d4-bb0e-2632f9ff7633
railway up has been failing consistently for several attempts today with:
error sending request for url (https://backboard.railway.com/project/.../environment/.../up?serviceId=...)
Caused by:
0: client error (SendRequest)
1: connection error
2: An existing connection was forcibly closed by the remote host. (os error 10054)The dashboard shows a corresponding failed deployment: "Deployment failed during initialization process" → "Initialization > Snapshot code" → "Failed to create code snapshot. Please review your last commit, or try again." Build never starts. The built-in Diagnosis tool couldn't identify a cause either.
I've already ruled out the usual suspects on my end:
- Upload size: with --verbose, the actual compressed payload is only 8,446,610 bytes (~8MB) — well under any known limit.
- Network path: identical failure from both my regular network and a separate mobile hotspot.
- .railwayignore: confirmed no BOM issue, node_modules/.next/.git properly excluded.
- Local code: builds and type-checks cleanly.
The existing production deployment (railway up, successful, currently Online/ACTIVE) is unaffected. Could you check the backend logs around this service/environment for these snapshot-creation failures? Happy to provide the exact timestamps of each failed attempt if useful.
5 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
We found the failed deployments you’re seeing in the dashboard, so we have the timestamps needed to investigate. Could you share your CLI version (railway --version)?
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
railway 5.62.1
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
The backend logs confirm that your upload reaches Railway, but the connection closes before snapshot creation completes. A larger upload succeeded earlier, so this doesn’t look like a size limit.
We haven’t established where the connection is being closed. Since you’ve already tested two networks, could you try the same upload from another machine? That would help narrow down whether the failure follows the device.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
Update: I tested from a completely different machine (Google Cloud Shell, different OS/network/IP) with the same project linked. The upload succeeded this time — no connection reset, it progressed past Compressed/Uploading into Railpack build preparation (which then failed for an unrelated reason specific to that throwaway test environment). This confirms the failure follows my Windows PC specifically, not Railway or the account/project. Is there anything Railway-side (e.g. a known Windows CLI issue in 5.62.1) that could explain a connection reset during upload on Windows specifically?
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Update: Reinstalling the Railway CLI (uninstall + reinstall @railway/cli via npm) fixed it — deploy succeeded right after. So the root cause was a corrupted/stale local CLI install on my machine, not Railway's backend. Thanks for the help — resolving this thread.
Status changed to Solved Railway • about 2 months ago