Skip to content
Railway CLI 5.71.0 upload returns 401 while whoami and GraphQL work
moematcom-alt
OP

18 days ago

Railway CLI 5.71.0 returns HTTP 401 / UPLOAD_FAILED during railway up, while whoami and GraphQL configuration/readbacks succeed using the same saved login. The dashboard shows the CLI authorized for all workspaces and projects. The failed upload creates no deployment and returns in about 1.8 seconds. RAILWAY_TOKEN was removed from the child process, and checks found no RAILWAY_API_TOKEN override. No OAuth refresh warning was captured. We found older reports involving account/team API tokens, but have not established that they apply to this saved-login case. Is there a known upload-route authentication issue or a supported diagnostic that can distinguish it safely? If staff need request identifiers, please advise how to provide them privately. We do not want to expose credentials or broaden access unnecessarily.

Solved

1 Reply

Railway
BOT

18 days ago

We can't confirm a known authentication issue specific to the upload step of railway up for saved CLI logins, so we can't tell you this matches the older API-token reports.

The safe self-serve step is to issue a fresh CLI session: run railway logout, then railway login, and retry railway up. Your active browser and CLI sessions are listed on your account security page, where you can delete any older CLI session you no longer use, so this doesn't broaden access.


Status changed to Awaiting User Response Railway • 18 days ago


Railway
BOT

11 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 • 11 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...