a year ago
Outbound Static IPs are useful for certain use cases, such as:
Whitelisting capabilities for connecting to ext database providers (e.g. MongoDB Atlas)
Certain 3rd party APIs that may apply a global rate limit on certain IP blocks (e.g. Discord)
Compliance purposes where shared tenancy is a no-go
10 Replies
a year ago
Are you able to add any updates on this please? We need to be able to connect to MongoDB Atlas. Thankyou.
a year ago
it's in progress, no ETA yet.
for connecting to Atlas you can whitelist all IP's with 0.0.0.0/0, though that may not be a solution for everyone.
Status changed to In Progress brody • about 1 year ago
a year ago
Are you able to add any updates on this please? We need to be able to connect to MongoDB Atlas. Thankyou.
you can probably get away by whitelisting some of the ips here depending on your region https://utilities.up.railway.app/cidr-list
a year ago
What about via VPC Peering? https://www.mongodb.com/docs/atlas/security-vpc-peering/
a year ago
That wouldn't be applicable on Railway, but I'm going to get a little off topic and ask why not run Mongo on Railway? it would certainly eliminate the Database <--> Service egress fees.
8 months ago
does railway mongodb allow whitelisting of ip addresses that are allowed to connect to the database ?
8 months ago
No it doesn't, but you can completely remove the public TCP proxy to close off all public access, then connect to your database over the private network.
https://docs.railway.app/reference/private-networking
2 months ago
Dear Railway Team,
I am currently using Railway to deploy my trading bot and I noticed that my server's public IP keeps changing with each restart. For my use case, I need a static IP to securely connect to Binance API while following their security restrictions.
Could you please confirm if Railway offers a static IP option on any of the available plans, including the Pro or Add-Ons plans? If not, is there any workaround or additional service that I could use to ensure a stable IP address for my deployment?
I would appreciate any guidance or recommendations on this matter.
2 months ago
Dear Railway Team,
I am currently using Railway to deploy my trading bot, and I noticed that my server's public IP keeps changing with each restart. For my use case, I need a static IP to securely connect to the Binance API while complying with their security restrictions.
I have reviewed the Railway documentation and found references to Static Inbound IPs and Railway Metal, but I also noticed that Static IPs are currently unavailable for Pro users on Railway Metal regions. Could you please clarify:
Does Railway offer a Static Outbound IP option on any of the available plans, including Pro or Add-Ons?
If not, is there any alternative solution, such as a reserved IP, a proxy, or another networking configuration that could allow me to maintain a stable external IP for my service?
Would upgrading to a specific plan or using an external integration help in achieving this requirement?
Since my bot relies on whitelisted IPs to communicate securely with Binance, having a persistent outbound IP is crucial for my operations. I would greatly appreciate any guidance or recommendations you could provide.
2 months ago
Yes we support static outbound IPs on the Pro plan -
Status changed to Completed brody • about 2 months ago