8 days ago
Hi Railway Support,
We have a production application hosted on Railway that needs to connect to an external server:
Host: vcrm.vivinimports.com.au
Port: 9248
The connection works successfully from our local PC, but it times out from our Railway production environment.
The external server administrator requires us to provide a fixed/static IPv4 address so they can allowlist our Railway-hosted application for TCP port 9248.
We would like to clarify the Railway plan and configuration requirements for Static Outbound IP.
Could you please confirm:
Is Static Outbound IP available on the Hobby plan?
If not, is the Pro plan required?
If Pro is required, how do we enable Static Outbound IP for our existing production service?
Once enabled, where can we find the static outbound IPv4 address that we should provide to the external server administrator?
Will outbound connections from our production service consistently use the assigned static IP?
Is any additional Railway configuration required to make outbound TCP connections to port 9248?
Is there any alternative way to achieve fixed-IP allowlisting while remaining on the Hobby plan, without upgrading to Pro?
Our goal is to provide the external server administrator with a fixed Railway outbound IP so they can allowlist it for TCP port 9248.
Current setup:
Environment: Production
External host: vcrm.vivinimports.com.au
External port: 9248
Local connection: Works
Railway connection: Connection timeout
Thanks.
1 Replies
8 days ago
Static Outbound IPs are not available on the Hobby plan. They are a Pro plan feature, and we don't have an alternative for fixed-IP allowlisting on Hobby.
On Pro, open your service's Settings tab, toggle Enable Static IPs in the Networking section, and redeploy the service. The IPv4 addresses for your service's region are shown right there once enabled, and those are what you give the server administrator. You can also manage this with railway outbound-network static-ip enable --service <name>.
Outbound traffic from all replicas of that service is load balanced across the assigned IPs (currently three), so the administrator should allowlist all of them. The addresses stay the same unless you move the service to a different region, and they may be shared with other customers rather than dedicated. No separate configuration is needed for a specific outbound TCP port.
More details: Static Outbound IPs
Status changed to Awaiting User Response Railway • 8 days ago
20 hours ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 20 hours ago