4 months ago
"Cannot migrate volumes between non-metal and metal regions. Please create a new volume instead"
3 Replies
4 months ago
For some odd reason, some users are not able to migrate non-metal volumes to metal. I have escalated this issue to team in another thread.
4 months ago
Same here. The feature flag is on, but I cannot migrate with the same message: "Cannot migrate volumes between non-metal and metal regions. Please create a new volume instead."
4 months ago
Apologies for the late response, non metal to metal volume migrations are currently paused for pro users. More on that can be found in the latest changelog: https://railway.com/changelog/2025-03-14-ssh-railpack-improvements#hobby-metal-volumes.
4 months ago
@uxuz When will this be unpaused?
4 months ago
Hey @Furiae, unfortunately I am unable to provide you with an exact date. However, what I can do is to notify everyone that has participated in this thread once non metal to metal volume migrations have been resumed for pro users.
4 months ago
That works for me. I have small demo environments at the moment so I am not in a huge rush. I do have a new app I am about to start building that we do not want to GCP or AWS which is why I am really checking. 😄
4 months ago
Same error here. But I managed to create a new volume on metal, but impossible to import database dump from the previous non metal volume - pg_restore: error: could not execute query: ERROR: unrecognized configuration parameter "transaction_timeout"
3 months ago
Hey everyone, metal volume migrations have been enabled for pro users under the metal volumes feature flag: https://railway.com/account/feature-flags. More on this can be found in the latest changelog: https://railway.com/changelog/2025-03-28-preferred-deployment-region#metal-feature-parity-+-migration-timeline
@volemrdat @Furiae
3 months ago
You are welcome! 🙂
3 months ago
!s
Status changed to Solved uxuz • 3 months ago