Your Postgres deployment is online and the volume is healthy, but the Database View can't establish a connection. This is typically caused by a stale container image that a normal restart won't fix. Open your Postgres service, press Cmd+K (or Ctrl+K) to open the command palette, and select "Redeploy source image" to pull a fresh image.

Ive done the same steps, but its still the same issue again

Can you share the deployment logs?

Can you take a screenshot of deployment details?

A normal redeploy usually fixes this problem. Since you already tried it, I suggest you wait some time and try to redeploy again if it isn't fixed by then, and see if the issue persists.

Still getting same error. Tried creating new image after hours

are you running a local CLI? It may have an expired authorization token

Are you able to access the database using the public URL via database client (eg, Datagrip)?

https://station.railway.com/questions/railway-ssh-fails-with-unauthorized-imme-4e1737f8

this is what I meant

No, Im not using any CLI. Im just trying to create an instance

Also this is failing from datagrip if i connect using public url with error:

psql: error: connection to server at "maglev.proxy.rlwy.net" (66.33.22.251), port 19093 failed: Operation timed out

Is the server running on that host and accepting TCP/IP connections?

Im having the same issue the past hour

@gkogkos-th is that resolved?

@0x5b62656e5d any other workarounds?