Automatic Migration to Metal
kamenb
PROOP

8 months ago

Hey folks,

Many thanks for the awesome service you provide! We've started getting our instances automatically migrated to Metal, which causes our deploys to crash without reverting to their non-Metal functioning counterparts. With that in mind I wanted to check if:

  1. There is an option for us to opt out of migration to Metal for the time being?

  2. If not, whether it's possible to send across a notification in advance for these being scheduled? This last update happened at 4AM for us without any notifications, so we lost service for several hours.

Many thanks in advance,

Kamen

Solved

5 Replies

sarahkb125
EMPLOYEE

8 months ago

Hi there,

We are migrating on an ongoing basis and unfortunately not optional. The best way to expect a migration is to migrate to Metal yourself.

Follow this guide to do so: https://docs.railway.com/reference/migrate-to-railway-metal


Status changed to Awaiting User Response Railway 8 months ago


Status changed to Solved sarahkb125 8 months ago


kamenb
PROOP

8 months ago

Fantastic, thanks for the swift response! We're doing the migration now, we just need the subnet mask for US East Metal, can that be found somewhere in the settings? We need this to adjust our DB permissions.


Status changed to Awaiting Railway Response Railway 8 months ago


sarahkb125
EMPLOYEE

8 months ago

Is this what you need?

Attachments


Status changed to Awaiting User Response Railway 8 months ago


Status changed to Solved sarahkb125 8 months ago


kamenb
PROOP

8 months ago

Hey, thanks, that seems to have solved the problem. I just want to check that all services in US-East Metal will share that same external IP (162.220.234.15)? When setting up our whitelists, we usually do a subnet mask, i.e. for a range of IPs (162.220.234.0/24 a.k.a. anything that starts with 162.220.234 and then has a number between 0 and 255), so I wanted to make sure we won't be blacklisting anything important if we do only 162.220.234.15


Status changed to Awaiting Railway Response Railway 8 months ago


sarahkb125
EMPLOYEE

8 months ago

Correct, you only need to whitelist the ip (162.220.234.15) without anything extra.


Status changed to Awaiting User Response Railway 8 months ago


Status changed to Solved sarahkb125 8 months ago


Loading...