#Postgres volume region migration error

8 messages · Page 1 of 1 (latest)

silk sequoia
#

Hello! In project 36bb0b84-a28c-439f-ab6a-9157df9fb44a, I added a Postgres database. It auto-added to the US West, and I initiated a move to the EU region. After a few seconds, the migration failed and prompted me to contact support. Volume ID: 74e3900a-2aed-41c0-8791-1685b740f31f

steep arrowBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

hushed belfryBOT
#

Project ID: 36bb0b84-a28c-439f-ab6a-9157df9fb44a,74e3900a-2aed-41c0-8791-1685b740f31f

true fog
#

Getting same issue.
Getting following error:

Volume migration failed
Your volume pgdata has failed to migrate to theUS West region.

Can't init DB in Europe from the start which would be ideal.

silk sequoia
true fog
#

Should atleast be exposed via cli

alpine bluff
#

choosing a region before deployment is on the roadmap, don't know if this information was put publicly anywhere, but I was told it would be a feature at some point directly by a team member.
there are some work arounds.
create an empty service, setup all the variables, start commands, anything you'd need to run the app, set the region and then attach your github repo, first deployment will now be in the region of choice.
but for templates there's no way to choose a region beforehand yet

true fog
#

This now works for me again. Seems to been the outage: #🚨|incidents message