a year ago
Did something recently change (within ~12-24hrs) with project tokens? My CI/CD on GitHub Actions is unable to deploy to Railway and I'm getting an error - "Unauthorized. Please login with railway login". This is happening for two different projects that use two different keys and nothing has changed on my end since yesterday AFAIK.
Using "@railway/cli": "^4.1.0"
Also running railway up --service api --ci --detach in GitHub actions with the RAILWAY_TOKEN env key defined.
9 Replies
a year ago
Hey there! I know it's not ideal and you might have tried already but did you try creating a new project scoped token and updating RAILWAY_TOKEN?
Just to rule out that possibility
The command also fails when I run it locally with the same newly created token 🤔
RAILWAY_TOKEN=XXXX pnpm run railway up --service api --ci
Oh wait okay upgrading to CLI 4.10.0 solved it - was previously on 4.1.0.
a year ago
great! glad to hear it works
a year ago
let me know if it also works on CI
10 months ago
I'm currently experiencing this same issue on 4.10.0. Any ideas?
jamesburrow23
I'm currently experiencing this same issue on 4.10.0\. Any ideas?
10 months ago
ha, I just figured it out. I set an API level token as RAILWAY_TOKEN in my bitbucket pipeline and was then trying to run railway link -p {PROJECT_ID}