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

• 🧵 Error: Redis initialization failed: Error: Connection timeout

• 🧵 railway/cli not working in Github Actions - Timeout

• 🧵 CLI error

• 🧵 Error logging in to CLI. Please try again with --browserless

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

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.

Hi there, could you:

1. try using --skip-deploys to confirm the issue

2. link the service you're trying to deploy?

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.

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

This is one of the services: https://railway.com/project/d3b67aaa-65cc-43c9-80aa-9da1b00cafa5/service/44e7a644-4527-4ca3-b9c8-605465000151/settings?environmentId=18bdc586-99d3-4594-8ec7-337073957d02

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.