PostgreSQL Connection Loop - Can't reach database server
alle4you
PROOP

4 months ago

Project: endearing-comfort
Environment: production
Service: Postgres-ZEHo
Database URL: nozomi.proxy.rlwy.net:29779

Problem Description

The Railway dashboard shows "Database Connection: Attempting to connect to the database..." in an infinite loop. The database is unreachable from both:

  1. Railway UI (shown in screenshot)

  2. Local development environment via Prisma Client

When it started: ~17 minutes ago (based on last successful deployment)

Tests Performedwhite_check_mark emojix emoji

Working:

  • white_check_mark emoji Direct psql connection: WORKS

  • white_check_mark emoji TCP connection via netcat: Port 29779 is OPEN

  • white_check_mark emoji DNS resolution: Resolves to 66.33.22.249

  • white_check_mark emoji Ping: Server responds (130-173ms latency)

  • white_check_mark emoji Query execution via psql: SELECT NOW() returns successfully

Failing:

  • x emoji Prisma Client connection: Timeout after 8 seconds

  • x emoji Railway Dashboard connection: Infinite loop

  • x emoji SSL connection attempts: SSL SYSCALL error: EOF detected

Technical Details

PostgreSQL Version: 16.x (attempting to upgrade to 16.10)
Connection String: postgresql://postgres:***@nozomi.proxy.rlwy.net:29779/railway
Current Connections: 14 active (checked via psql: 13 idle + 1 active)
Max Connections: 100

Error Messages:

# Prisma Client Error:
Can't reach database server at `nozomi.proxy.rlwy.net:29779`
Please make sure your database server is running

# psql Error (intermittent):
SSL SYSCALL error: EOF detected

$10 Bounty

2 Replies


alle4you
PROOP

4 months ago

Requested Actions

  1. Investigate why Railway UI cannot connect to the database

  2. Check for connection pool exhaustion or hanging connections

  3. Verify SSL/TLS configuration on nozomi.proxy.rlwy.net:29779

  4. Confirm if PostgreSQL 16.10 upgrade is safe to apply

  5. Provide guidance on connection parameters for Prisma Client

Temporary Workarounds Attempted

  • white_check_mark emoji Reinstalled Prisma Client locally

  • white_check_mark emoji Cleared Prisma engine cache

  • white_check_mark emoji Tested different SSL modes (require, prefer, disable)

  • white_check_mark emoji Tested with IP address instead of hostname

  • x emoji All failed with same timeout error


4 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody 4 months ago


Loading...