Linked Railway resource: 6149ad65 / 90f0eca2 / a6998bea
#PostgresSQL server closed
lean hareBOT
wheat swift
That runs PG17, what version of psql are you using?
surreal ermine
That runs PG17, what version of psql are you using?
The psql client I'm using locally is an older version (likely 14 or 15 via WSL). But that shouldn't matter since the TCP connection succeeds — the issue is the connection drops immediately after the handshake, before any protocol exchange. Could it be a version mismatch between the proxy and the client?
Ok checked same version, psql 17.5. Still getting immediate connection drop after TCP handshake.
wheat swift
Could I run a connection test with a Postgres client? If so, could you DM me the database URL?
surreal ermine
Could I run a connection test with a Postgres client? If so, could you DM me th...
Yes
wheat swift
Works.
surreal ermine
Still can't access to the data here
and having this message when I try a deploy:
Error: P1001: Can't reach database server at postgres-sazm.railway.internal:5432
Please make sure your database server is running at postgres-sazm.railway.internal:5432.
Loaded Prisma config from prisma.config.ts.
Prisma schema loaded from prisma/schema.prisma.
The external proxy maglev.proxy.rlwy.net:11974 works (you just showed it), but the internal hostname postgres-sazm.railway.internal:5432 is unreachable from my backend service. My backend keeps crashing with P1001: Can't reach postgres-sazm.railway.internal:5432. Both services are in the same project. Is the internal networking broken for this specific postgres service?
wheat swift
The private network is not available during build time, only at runtime.
surreal ermine
The private network is not available during build time, only at runtime.
But why can't access to the data here and can for the another db ?
