Postgres Database Connection Failing in Project

alexk1mkz
FREE

2 days ago

Hi Railway Support,

I’m encountering an issue with Postgres in my project (https://railway.app/project/cb9ee7cb-cb44-4744-bd0b-84c517097753). The “Database Connection” in the Postgres Data UI is stuck/loading and never establishes a handshake. The service shows as deployed and required variables are present, but the UI cannot connect.

Details:

  • Project: cb9ee7cb-cb44-4744-bd0b-84c517097753

  • Environment: [fill: e.g., production or development, include its ID if available]

  • Service: Postgres

  • Symptom: “Database Connection” does not complete; UI remains hanging.

  • What I’ve done already:

    1. Checked Postgres logs (no obvious crash, but connection isn’t completing) — can supply the last 30–50 lines if needed.

    2. Attempted manual connection with psql using the provided DATABASE_URL (with ?sslmode=require if needed) — getting a connection failure (I can paste the exact error message).

    3. Verified that DATABASE_URL is set and used by the application, including SSL settings.

    4. Restarted the Postgres service.

    5. Confirmed there’s no apparent quota or obvious limit exceeded on my side.

What I need:
Help diagnosing why the Postgres Data UI cannot complete the database connection and guidance on what to adjust so the database becomes reachable (or clarification if there’s a platform-side issue).

I can attach screenshots, full log snippets, and the exact error from the psql attempt if you advise which would be most useful.

$10 Bounty

3 Replies

Railway
BOT

2 days ago

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

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


alexk1mkz
FREE

2 days ago

Database connection issue

Attachments


alexk1mkz

Database connection issue

smolpaw
HOBBYTop 5% Contributor

2 days ago

Attach the logs from the psql attempt
Don 't use the sslmode and verify that you have the TCP proxy setup. Your public endpoint should be using this rlwy.net url with the custom port. not 5432, that's your container's port. here 42467 is the one being exposed to the public. Yours maybe different. Also make sure you haven't changed the default postgres port of 5432.

Attachments