railway up fails with "Connection reset by peer" — backend service is down, cannot deploy
Anonymous
PROOP

2 months ago

railway up --detach` consistently fails at the upload step with:

error sending request for url

(https://backboard.railway.com/project/688c153e-5dba-4641-a1ab-34c5faca91a0/environment/ba82b3a8-7a85-437a-a459-31dd03592b11/up?serviceId=8fce00f7-7fd5-4554-8ffd-9effbaafdf95)

Caused by:

0: client error (SendRequest)

1: connection error

2: Connection reset by peer (os error 54)

What I've tried (all fail with the same error):

- Railway CLI v4.35.0 (latest)

- Re-authenticated (railway login)

- Created a new API token

- Deployed from a minimal 14MB directory

- Multiple retries over the past several hours

The last successful deployment crashed due to a migration error, and all previous deployments show as REMOVED, so I cannot rollback. The backend (api.hi-vi.com) is currently returning 502 and

serving production users.

This is urgent — the service is completely down and I have no way to deploy.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway about 2 months ago


Anonymous
PROOP

2 months ago

Current state:

- All previous deployments show as REMOVED in the dashboard, so rollback is not possible

- The only non-removed deployment is the FAILED one (snapshot error) and a CRASHED one

- api.hi-vi.com is returning 502 to production users

- We cannot delete and recreate the service because it has many environment variables we can't easily reproduce

Ask:

Could you help us either (1) fix the upload endpoint for our project, or (2) trigger a deployment from our connected GitHub repo? This is urgent as our production API is completely down.

Thank you.


Status changed to Solved Anonymous about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...