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

• 🧵 Postgres database unreachable

• 🧵 Railway Support Request - Internal Database Connection Failure

• 🧵 Postgres Database Connection

• 🧵 Postgres Database Connection

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

I had the same issue and i could solve it with adding the TCP Port in the Networking.

Is that a recent change or is adding a TCP port required now? It was working with no issues and I can still manually log in and see my data. Its just not currently connected to my project. lol

I have no Idea. I am new to railway and thought that this was my fault

Ok I think I misunderstood. I already have the initial TCP port setup that is required for connection as well as the correct variables.

A TCP Proxy has always been required; without one, the data tab has no way to access your database.

I hadn't had enough coffee yet to process what he was saying lol. I thought he meant another TCP port or something. I finally caught up. Any idea on your end what could be happening? I didn't make any changes but noticed the DB is on metal and I don't think my server is. If that makes a difference.

To be clear, my comment above states that I already have the standard setup for TCP so it's not that. Can I get some assistance getting this to work please?

While the data tab does not use the private network, it still needs to be enabled. Please go ahead and enable it.

That worked. Thank you! Is this a new change or has it always been this way? Because it was working with no issues for months.

The new change caused this as a side effect, but there is zero reason to have private networking disabled, so I see this as a non issue.