Hi Railway Support,

I’ve been trying to connect a PostgREST container to a Supavisor service running on Railway, but I’m encountering an issue with port accessibility.

From what I understand, each Railway service typically exposes only a single port (the primary PORT) for internal networking. In the case of Supavisor, this primary port is 3000 (used for the HTTP API). However, Supavisor also listens on ports 5432 and 6543 for Postgres traffic, which appear not to be accessible internally by other services.

Even though Supavisor is clearly listening on 6543 inside its container, it seems the internal DNS (supavisor.railway.internal) only routes to the primary port, and other ports are either blocked or not exposed for inter-service communication. This makes it difficult (or impossible) for the PostgREST container to reach the Postgres interface on 6543.

Could you please confirm whether Railway supports exposing multiple internal ports per service, especially for non-HTTP protocols? If not, is there a recommended workaround to enable this kind of inter-service communication?

Thanks in advance!