Hello!

You can start migrating right now, as long as you have the "Metal Volumes" feature flag enabled -

This shouldn't be behind a flag for Hobby 🤔

Lemme converse with the team about this.

I think I may need to enable something else then

Ah yes the runtime needs to be V2

Feature bingo strikes again

That allowed the migration to happen.
Both the service (node) and the (mysql&volume) seem to have migrated, but the service cannot connect to the database.

I am reverting back for the moment as I need the site live and will look at this again later or tomorrow

The MySQL container log looks the same on non-metal.

It just seems to be some kind of internal routing / permissions error on metal?

You migrated both the services to US-West Metal right?

Actually netherlands metal.
Waited for them both to be green and restarted node service but got those errors.
Tried a redeploy and same result.
Switch back to.non-metal has everything up again, but obviously I will need to find the issue and migrate at some point.

Would a migration to us west metal 1st be better? And then move to netherlands once it works on metal?

Ok, migrating to us west metal has worked.
We can leave things there for now.
Most of the access is from europe so I had thought netherlands was a better fit - but its not a deal breaker

Ah I was purely just curious what region you migrated to is all, unfortunately there is nothing for me or platform to dig into given your stuff works right now, perhaps you would be interested in duplicating to a test environment with our environment duplication feature, then migrating those services to EU Metal?

I ended up getting distracted by bugs and my own bad coding choices.
US Calif metal is working so far, so I will revisit this at a later date

Thank you for your help

Sounds good!, ill mark this solved for now then

!s