Railway upgraded to $20 plan, caused railway-cli auth fails
sajithamma
PROOP

23 days ago

Railway is awesome, and i was on $5 plan, and my Claude cli managed everything with railway cli, till yesterday, everything was fine, me happy, my Claude happy.

So, thought to upgrade railway to $20 plan, boom, railway cli auth started failing.

Now i created the access token and curl way of deploying from Claude. (You know nowadays we don't code :), though I am a 25 year experienced coder)

So, I am writing behave of my Claude CLI, solve the railway cli (i am using the latest version), about the auth problem for $20 professional plan.

Solved

2 Replies

Railway
BOT

23 days ago

Your account is active on the Pro plan, and plan upgrades do not invalidate existing CLI authentication sessions or tokens. You can try running railway logout followed by railway login to re-authenticate, or for non-interactive usage (such as from Claude CLI), set the RAILWAY_API_TOKEN environment variable with a personal token from your account settings so the CLI authenticates automatically without requiring a browser flow.


Status changed to Awaiting User Response Railway 23 days ago


Status changed to Solved sajithamma 23 days ago


sajithamma
PROOP

23 days ago

I love you Railway bot 🙂


Status changed to Awaiting Railway Response Railway 23 days ago


Status changed to Solved Railway 23 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...