I see a few issues -

1. you had the database public url as a shared variable, should be using a reference variable.

2. you ran railway up while linked to your database, taking it offline.

3. you gave your database a service domain, it only should have a TCP proxy.

Fixed all of these for you and your data tab works again.

can you clarify the usage of railway up causing issues? I have as part of my ci/cd for instance:

    - name: Deploy to Railway
      env:
        RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
      run: railway up --ci --service ${{ secrets.RAILWAY_SVC_ID }}

should I not be doing that?

im not sure where you ran railway up from be that in CI or locally, but somehow you ran railway up while linked to the database service

I see. I likely ran it locally at one point not thinking it would cause issues. Thanks for your assistance. I can work on it from here.

no problem, ill leave this open for now incase you have any more questions

I'm having the same issue again. I'm thinking maybe I need to remove the Railway steps from my CI/CD? I have a Railway service already triggered by changes on my main branch, and just merged a feature branch into main. Maybe that's what's causing excess railway up executions?

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

- name: Deploy to Railway
  env:
    RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
  run: railway up --ci --service ${{ secrets.RAILWAY_SVC_ID }}

assuming the Railway service I have associated with my Github deploys also is running railway up

the psql command to connect to the DB is unsuccessful now as well. I don't see a constantly spinning "Database connection" in the Data tab, but "We are unable to connect to the database over the public network.

Can you connect using this command?" (no)

how do I resuscitate the DB from here? And am I correct in that I need to change my CI/CD to not also execute railway up?

yep looks like you ran railway up on the database again, you can restore it by redeploying the postgres image from your history.

may i ask why you are using railway up at all?

It was just occurring to me that I don't think I need it at all. At some point I thought I needed it and added it in my ci/cd. That was wrong. I've now removed those steps and letting the Railway Github link take care of the Railway deploy itself.

I am only a Hobby user. In Postgres | Backups I see "Backups are only available for Teams on the Pro plan"

yep they are a Pro feature

I clearly am not a Pro. 🙂 Now that I've removed the step from my ci/cd, can you revive it one more time for me? Unless there's another way to restore the image

i wasnt using backups to restore it

i was just redeploying

thanks for clarifying. makes sense. redeployed OK

everything working as expected now. thanks again. I made some dumb mistakes. they've been corrected

while i have you, is there any reason you are using the public database url instead of the private?

difficulty trying to test with the private URL

for my local testing

use private on railway, use public locally

got it. that makes sense. I'll test that on a branch and then merge that in if all good there too

sounds good

!s