We’re currently facing an issue within our Railway environment.

Although our PostgreSQL service appears to be correctly linked within the same environment, our application is unable to connect to it using the private network.

We’ve verified that this is not related to naming issues — we’ve followed minimal naming conventions and avoided spaces or special characters in service and environment variable names.

The only way we’ve been able to establish a connection is via the public database URL, which unfortunately results in egress costs.

Could you please help us understand why the private/internal connection isn’t reachable and how we can properly configure this to avoid using the public endpoint?