BUG: Railway CLI – persistent timeouts
jakobzach
HOBBYOP

7 months ago

I'm trying to set env vars in my GitHub Action but continuously get timeout errors for the following CLI command:

RAILWAY_TOKEN= railway variables --service <service_id> --environment <env_id> --set "SENTRY_RELEASE=api-test"

Failed to fetch: error sending request for url (https://backboard.railway.com/graphql/v2)

Caused by:

0: error sending request for url (https://backboard.railway.com/graphql/v2)

1: operation timed out

The issue also exists when trying through my local terminal and has persisted for >72h now.

There is also this GitHub issue for almost 2 months now: https://github.com/railwayapp/cli/issues/655

Solved

7 Replies

Railway
BOT

7 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


jakobzach
HOBBYOP

7 months ago

This seems to be the same issue I have: 🧵 railway/cli not working in Github Actions - Timeout

3 months later it is still not fixed tho, and apparently not even being worked on.


7 months ago

Hi there, could you:

  1. try using --skip-deploys to confirm the issue
  2. link the service you're trying to deploy?

Status changed to Awaiting User Response Railway 7 months ago


jakobzach
HOBBYOP

7 months ago

Thanks for getting back to me!

I have tried --skip-deploys which resolved the error locally but not in my GitHub Action.

I don't see an option to link a service to an existing thread. The error happens for all of the services in my account. Hope this helps.


Status changed to Awaiting Railway Response Railway 7 months ago


7 months ago

Sorry, I meant sending a link to the service itself.


Status changed to Awaiting User Response Railway 7 months ago



Status changed to Awaiting Railway Response Railway 7 months ago


7 months ago

For now, the timeout is expected. Our gateway has a timeout, and if your deploy takes longer than our timeout, you will get a 504. So, using that flag is going to be the recommended approach.


Status changed to Awaiting User Response Railway 7 months ago


Status changed to Solved brody 7 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...