2 months ago
The TLS diagnostic reveals the root cause - Railway's PostgreSQL proxy is returning HTTP responses instead of
PostgreSQL protocol. Both internal and external URLs show the same issue:
PostgreSQL SSL Request → HTTP/1.1 400 Bad Request
This explains why all SSL connection attempts failed - the proxy isn't forwarding PostgreSQL wire protocol correctly. This is a Railway infrastructure issue, not a code problem.
Summary of the situation:
1. XXX
2. Cannot test because Railway's database proxy is broken
3. Both internal (postgres.railway.internal:5432) and external (shortline.proxy.rlwy.net:58059) URLs have the same issue
3 Replies
2 months ago
Claude is convinced this is Railway, would really like to get this fixed. It looks like in other similar posts it has indeed be related to Railway maintenance concerns. Help please (:
2 months ago
This is prod, need help!
Challenge cleanup error: Error: Connection terminated unexpectedly
at /app/node_modules/pg-pool/index.js:45:11
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.deleteExpired (file:///app/dist/database/index.js:681:24)
at async cleanupExpiredChallenges (file:///app/dist/services/challengeService.js:159:12)
a month ago
What does your variable config look like? What options are you using to connect to Postgres?