TCP Proxy Connection Failed: Postgres Public Access Broken (metro.proxy.rlwy.net:56217)
betosalazarg
HOBBYOP

19 days ago

Issue

Cannot connect to Postgres database via Railway's public TCP proxy. All external psql connections fail immediately, while internal app connections work fine.

Environment

  • Project: agile-surprise
  • Service: Postgres
  • Public Proxy: metro.proxy.rlwy.net:56217
  • Internal Port: 5432

Error

psql: error: connection to server at "metro.proxy.rlwy.net" (66.33.22.250), port 56217 failed: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.

Steps to Reproduce

  1. Get Postgres connection string from Railway dashboard
  2. Run: psql "postgresql://postgres:PASSWORD@metro.proxy.rlwy.net:56217/postgres?sslmode=disable"
  3. Connection fails immediately

What Works

  • Internal connections from finanzas-portal app to Postgres work fine
  • Postgres is healthy (logs show "database system is ready to accept connections")
  • TCP connectivity to proxy works (Test-NetConnection succeeds)

What Doesn't Work

  • External psql connections via public proxy
  • Restarting Postgres service did not fix the issue

Expected Behavior

Should be able to connect to Postgres via public TCP proxy like before.

Additional Info

  • Postgres version: 18.4
  • Postgres is listening on 0.0.0.0:5432 and IPv6 ::5432
  • No recent changes to service configuration
$10 Bounty

1 Replies

Railway
BOT

19 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 19 days ago


Try selecting your service, then press CTRL + K, and select Redeploy source image.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...