I have tried whitelisting IPs for US West (California) and EU West (Amsterdam) but that doesn't seem to help.

Railway recently migrated a lot of apps to metal automatically, if it's a big issue then you can migrate your app back to US West Oregon for now

I'll go ask about the metal IP address range for us-west

Thanks @Fragly

It is a big issue in as much as my app won't work at all. If this cannot be solved, I'll have to be deploy my app somewhere else quickly.

Would migrating the app back to US West Oregon be only a temporary measure? If that's the case, let's rather go for something more permanent. If not, I'd appreciate some tip about how I can do that. Simply changing the region in the settings didn't work, the region changes when I re-deploy.

I don't mind what region it is as long as it works. I can whitelist up to 200 IPs.

Railway will remove their reliance on GCP in the near future and all deploys will happen on metal, so yea staying on oregon is a temporary solution
once I know where I can find the IP range for us-west metal then I'll share that with you and you can whitelist those IPs and move to metal

It's odd to me that your region would change when you redeploy.. I have deployments in oregon right now so I know it's still available 🤔
if you're sure it is moving the region back then you could try adding a volume
metal doesn't support volume yet so adding a volume will prevent it from moving back to metal (for now)

By the way, if you want more info on metal, there's a very detailed page all about it here:

Indeed, it's odd to me too, but that's what happens. Can you see what I mean in the gif?

yea, that's very weird..
see if adding a volume will help

adding the volume did the trick

thanks a lot @Fragly

I guess that's good for now

when you can, will you please let me know how I can find out what IPs correspond to the metal regions?

No problem! yes I'll ping you the moment I have information on that

Hey @مــــــانــــــو, the IP range for Railway US West metal is 162.220.232.0/23

thanks @Fragly, I can whitelist individual IPs, not sure how I must use a "range". Does that mean that I should whitelist the 512 IPs between 162.220.232.0 and 162.220.233.255?

unfortunately, I cannot whitelist more than 200 IP addresses

you would need to upgrade to Pro for a single static IP, since this is a temporary solution

though most firewalls allow you to enter a cidr range

MongoDB Atlas does not allow whitelisting an entire CIDR range directly, but I have found out I can whitelist smaller subnets. I have worked out how to consume only two slots. Instead of whitelisting every individual IP, I can break down the /23 range into two /24 blocks:

162.220.232.0/24 (covers 162.220.232.0 – 162.220.232.255)
162.220.233.0/24 (covers 162.220.233.0 – 162.220.233.255)

Thanks @Brody and @Fragly for your help.

Awesome, glad to hear you got it working

Clear to mark as solved?

Yes, please

!s

🫡 perfect

!s