tool · inferred from evidence
railway up
A command in the Railway CLI that failed with an authorization error.
- Railway CLI: RAILWAY_API_TOKEN ignored by "railway link" — "Unauthorized. Please login with railway login"
After CLI v3.14.0, running railway link -p ... with RAILWAY_API_TOKEN set always failed with "Unauthorized. Please login with `railway login`", breaking CI pipelines that relied on token auth. Part of the confusion in the thread was the two
- Railway CLI v3: "railway up" fails with "Unauthorized. Please login with railway login" despite RAILWAY_TOKEN
In CI (GitHub Actions) and locally, railway up with RAILWAY_TOKEN exported started failing on CLI v3.x with: Error: Unauthorized. Please login with `railway login`, exiting with status 1. Oddly, the deployment itself still triggered and com