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

a month 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 Performed

Working:

  • Direct psql connection: WORKS

  • TCP connection via netcat: Port 29779 is OPEN

  • DNS resolution: Resolves to 66.33.22.249

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

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

Failing:

  • Prisma Client connection: Timeout after 8 seconds

  • Railway Dashboard connection: Infinite loop

  • 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

a month 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

  • Reinstalled Prisma Client locally

  • Cleared Prisma engine cache

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

  • Tested with IP address instead of hostname

  • All failed with same timeout error


brody
EMPLOYEE

a month 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 about 1 month ago


Loading...