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?

Guys any solution please?

Ok I asked Google AI and this is what came back (I'm still somewhat new to Railway sorry if you've already checked all this)

The connection timeout error indicates that the network request from your local machine is failing to reach Railway's proxy server. [1]

An Operation timed out message means a network barrier or configuration mismatch is silently dropping the packets before DataGrip or psql can authenticate with the database. [1, 2]

📑 Checklist to Resolve the Timeout

1. Verify Your Local Network Restriction

• The Issue: Many corporate, school, or public Wi-Fi networks block outbound traffic on non-standard ports (like 19093).

•   * The Fix: Switch to a different network (like a mobile hotspot) or connect through a VPN. If the timeout disappears, your current network is blocking the port. [3, 4, 5] 

1. Check DataGrip Parameter Separation

• Ensure you are not putting the entire string into the Host field.

•   * Host: maglev.proxy.rlwy.net

  • Port: 19093

  •   * Do not use the default internal port 5432 for remote connections. [6, 7, 8] 

1. Validate the Proxy Domain Status

• Railway proxy domains can change if a database service is deleted, recreated, or un-proxied.

•   * Go to your PostgreSQL service in the Railway console.

  • Click Settings and scroll down to the Networking / Public Networking section.

  •   * Confirm that maglev.proxy.rlwy.net and port 19093 exactly match what is listed. If they don't, copy the new connection variables. [5, 7, 9] 

1. Verify Database Deployment Health

• Go to the Variables or Deployments tab of your Postgres instance in Railway.

•   * Confirm the instance status reads "Active" or "Ready to accept connections". If it crashed during initialization, the proxy will have nothing to route to, resulting in a timeout. [5, 6, 10, 11] 

1. Test via Terminal Network Tools

• Bypass DataGrip entirely to rule out client-side configuration bugs. Run this in your terminal:

  nc -vz maglev.proxy.rlwy.net 19093

  * If it says Connection to maglev.proxy.rlwy.net port 19093 [tcp/*] succeeded!, the network path is open, meaning the issue is strictly inside your DataGrip configuration settings. [5, 12] 
  *    

✅ Verification

Below is an illustration of what a successful low-level TCP handshake looks like compared to your current network timeout scenario:

[Your Machine] ----❌ (Firewall / Blocked Port) ❌----> [maglev.proxy.rlwy.net:19093]

[Your Machine] ----🟢 (VPN / Open Network) ----> [maglev.proxy.rlwy.net:19093]