8 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:
- Railway UI (shown in screenshot)
- Local development environment via Prisma Client
When it started: ~17 minutes ago (based on last successful deployment)
Tests Performed
Working:
- Direct
psqlconnection: 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
2 Replies
8 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 psycopg2.OperationalError: SSL SYSCALL error: EOF detected
- 🧵 Posgresql cant connect without sslmode=disable inside railway
- 🧵 Failed to prune sessions: Error: self-signed certificate in certificate chain
- 🧵 SSL SYSCALL error: EOF detectedError during user update check: connection already closed
If you find the answer from one of these, please let us know by solving the thread!
8 months ago
Requested Actions
- Investigate why Railway UI cannot connect to the database
- Check for connection pool exhaustion or hanging connections
- Verify SSL/TLS configuration on
nozomi.proxy.rlwy.net:29779 - Confirm if PostgreSQL 16.10 upgrade is safe to apply
- 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
8 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 • 8 months ago