6 months ago
Since this morning I'm facing issues when running Github Actions with railway CLI
I'm running this in my action:
- name: Deploy API to Railway
run: |
cp railway.api.json railway.json
railway up --service ${{ secrets.RAILWAY_API_SERVICE_ID }} --detach
env:
RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}it worked fine for 2 months, until this morning.
The error I get:
Run cp railway.api.json railway.json
Unauthorized. Please login with railway login
Error: Process completed with exit code 1.
The token was 2 months old so I couldn't have expired. I tried creating new tokens also and didn't work either. Neither project tokens nor general account tokens that other support threads suggested.
10 Replies
6 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 railway/cli not working in Github Actions - Timeout
- 🧵 setting repo from CLI
- 🧵 Github actions with Railway CLI requires login?
If you find the answer from one of these, please let us know by solving the thread!
Status changed to Awaiting User Response Railway • 6 months ago
6 months ago
I’m experiencing the same issue. I can’t run it either via GitHub Actions or locally using the CLI. It’s been broken for about 30 minutes.
My project code is: 1517f30a-b1c5-43a9-aa46-3bffd9f72e7d.
Status changed to Awaiting Railway Response Railway • 6 months ago
6 months ago
What version of the CLI are you using? Can view this with railway --version
Status changed to Awaiting User Response Railway • 6 months ago
noahd
What version of the CLI are you using? Can view this with `railway --version`
6 months ago
4.11.0
Attachments
Status changed to Awaiting Railway Response Railway • 6 months ago
6 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
6 months ago
my project ID: 68ec13c9-8137-4b38-8ee2-9b561858d491
and version 4.11.0 as well
6 months ago
I have a ticket with them and they have acknowledged that a build is going up now with a fix.
6 months ago
seems to work again, so closing
Status changed to Solved rip32700 • 6 months ago
6 months ago
✅ The ticket Access Issues with Command Line Tool has been marked as completed.
