Hey, sorry for the delay here.

https://railway.app/project/d580c7ab-3391-40da-acfe-d939073dec57/service/3dc083c2-6634-421a-9c6a-d773b9db47b6 is this the database you're referring to? I can see it up and running. Are you missing any data?

My operation process:

1. Modify Region to Singapore and deploy tools to V2, save

2. After Redeploy, it could not be started. At that time, I couldn't see the log in Safari.

I have made a lot of attempts:

1.Create a new database mysql, observe the normal operation, mount the old database Volume to the new database instance, and the startup failed.

2....

3....

4....

Finally, the possible problem is that mysql should be pointed to 9.0.0 in the docker hub instead of the previous version, so the data set failed to load (I saw the log in Chrome browser at this time)

It is recommended that when migrating the database, pay attention to the possible version pointing problem of the Docker Image alias. You need to help users provide clearer guidelines in the product, which may also be a defect of Docker hub.

thank goodness

I encountered a new problem. The database has been successfully started, but the private network address cannot be connected (in fact, it has not been successful). After modifying it to the public network, it also cannot be connected. The ip parsed in the error message is different from the ip resolved by my computer.

Going to continue this conversation in the other thread you created