Unable to use Railway CLI
gauthamses
PROOP

8 months ago

Solved

9 Replies

chandrika
EMPLOYEE

8 months ago

Hey Gautham, would you happen to be behind a firewall or have anything within a network config that might be blocking this?

Status changed to Awaiting User Response Railway • 9 months ago

gauthamses
PROOP

8 months ago

No, you should check with cloudflare.

Status changed to Awaiting Railway Response Railway • 9 months ago

gauthamses
PROOP

8 months ago

I'm able to access https://railway.com/dashboard and requests to https://backboard.railway.com/graphql/v2 are failing. Clearly somethings up with Cloudflare config on your end

gauthamses
PROOP

8 months ago

This is a show-stopper / critical issue for us.

chandrika
EMPLOYEE

8 months ago

Strange and sorry to hear Gautham, we have users across many continents and regions and haven’t seen many other reports of this so wondering why it might be the case for you (or perhaps a particular region)

Status changed to Awaiting User Response Railway • 9 months ago

gauthamses
PROOP

8 months ago

You should check with cloudflare as to why they are blocking the request. I have shared my ip (ipv6) and the cloudflare

request id

Status changed to Awaiting Railway Response Railway • 9 months ago

chandrika
EMPLOYEE

8 months ago

Hey Gautham, trying to recreate this on our end — after the successful login, what commands did you run with the CLI to get to this state? If you can share the command + a video of what leads you to the error you're running into, would be really helpful!

Another quick question, could you try running a super simple CLI command like railway docs - does that lead you to our docs in the browser?

Status changed to Awaiting User Response Railway • 8 months ago

plungarini
HOBBY

5 months ago

Hello there! I'm joining this discussion since i've the same problem. I've a workflow file for github actions:

name: Version Management
on:
  push:
    branches: master
  pull_request:
    branches: master

jobs:
  update-version:
    runs-on: ubuntu-latest
    environment: Production

    steps:
      - name: Clone repository
        uses: actions/checkout@v4
        with:
          fetch-depth: 0
          fetch-tags: true
          ref: ${{ github.sha }}

      - name: Get version from tag
        run: |
          TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "0.0.0")
          echo "VERSION=$TAG" >> $GITHUB_ENV

      - name: Install Railway CLI
        run: npm install -g @railway/cli@latest

      - name: Update Railway env var
        env:
          RAILWAY_SERVICE_ID: ${{ secrets.RAILWAY_SERVICE_ID }}
          RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
          VERSION: ${{ env.VERSION }}
        run: |
          railway variables --set "VERSION=$VERSION" --service "$RAILWAY_SERVICE_ID"

It was working since 3 weeks ago. Now i did another deployment and i saw this error message:

Run railway variables --set "VERSION=$VERSION" --service "$RAILWAY_SERVICE_ID"

railway variables --set "VERSION=$VERSION" --service "$RAILWAY_SERVICE_ID"
shell: /usr/bin/bash -e {0}
env:
VERSION: 0.20.5
RAILWAY_SERVICE_ID: ***
RAILWAY_TOKEN: ***

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

Error: Process completed with exit code 1.

Edit 1:
Using `railway variables --set ...` locally it works.

Edit 2:
I noticed that by unchecking the "Wait for CI" toggle, it actually works. You can see from the screenshot below that it actually bumped the version:

I think the only problem is that the cli is returning a timeout error, so my workflow actually fails on github actions.

Status changed to Awaiting Railway Response Railway • 5 months ago

plungarini

Hello there! I'm joining this discussion since i've the same problem. I've a workflow file for github actions:name: Version Management on: push: branches: master pull_request: branches: master jobs: update-version: runs-on: ubuntu-latest environment: Production steps: - name: Clone repository uses: actions/checkout@v4 with: fetch-depth: 0 fetch-tags: true ref: ${{ github.sha }} - name: Get version from tag run: | TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "0.0.0") echo "VERSION=$TAG" >> $GITHUB_ENV - name: Install Railway CLI run: npm install -g @railway/cli@latest - name: Update Railway env var env: RAILWAY_SERVICE_ID: ${{ secrets.RAILWAY_SERVICE_ID }} RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }} VERSION: ${{ env.VERSION }} run: | railway variables --set "VERSION=$VERSION" --service "$RAILWAY_SERVICE_ID"It was working since 3 weeks ago. Now i did another deployment and i saw this error message:Run railway variables --set "VERSION=$VERSION" --service "$RAILWAY_SERVICE_ID" railway variables --set "VERSION=$VERSION" --service "$RAILWAY_SERVICE_ID" shell: /usr/bin/bash -e {0} env: VERSION: 0.20.5 RAILWAY_SERVICE_ID: *** RAILWAY_TOKEN: *** 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 Error: Process completed with exit code 1.Edit 1:Using `railway variables --set ...` locally it works.Edit 2:I noticed that by unchecking the "Wait for CI" toggle, it actually works. You can see from the screenshot below that it actually bumped the version:I think the only problem is that the cli is returning a timeout error, so my workflow actually fails on github actions.

brody
EMPLOYEE

5 months ago

Please open your own thread.

Status changed to Awaiting User Response Railway • 5 months ago

Railway
BOT

4 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 4 months ago

Loading...