a year ago
Hi,
I’m currently deploying a Node.js backend on Railway and I’m experiencing an issue when hosting it in the US West (California) region.
• My MongoDB Atlas cluster is hosted in europe-west1 (Belgium).
• On Netherlands (EU) region, everything works fine—even with dynamic outbound IPs and 0.0.0.0/0 in the Atlas whitelist.
• However, when deploying in US West, I get the following error from Mongoose: "MongooseServerSelectionError: Could not connect to any servers in your MongoDB Atlas cluster."
Even with 0.0.0.0/0 fully whitelisted, Atlas fails to connect from Railway US West, which suggests the problem may be at the network/proxy level on your side (routing, NAT, or firewall?).
I wanted to use US West primarily because it is currently the only region offering a static outbound IP, which I need for MongoDB Atlas IP whitelisting.
Can you confirm:
1. If outbound traffic from US West is routed differently than EU?
2. Whether the static IP provided in US West might be blocked or misrouted from Atlas’s Europe-based clusters?
3. If there’s a known workaround to solve this?
Thanks for your help :)
2 Replies
a year ago
Hello,
Can you try to put your service in EU-West non-Metal, Metal regions don't support Static IPs, not even US-West.
(I don't know why it's currently working in US West Metal, it shouldn't work)
Best,
Brody
Status changed to Awaiting User Response Railway • 12 months ago
brody
Hello,Can you try to put your service in EU-West non-Metal, Metal regions don't support Static IPs, not even US-West.(I don't know why it's currently working in US West Metal, it shouldn't work)Best,Brody
a year ago
You're right: it works on EU-West non-metals! So it fits my needs perfectly.
Thank you very much :)
Status changed to Awaiting Railway Response Railway • 12 months ago
Status changed to Solved drizzt • 12 months ago