Ok I gotcha myself because anyway I create my own pain so from what I understand to being able to restore Cloudron verify the DNS first than app/data I forgot to authorize my new IP in my Cloudflare API code 9109 is probably related to the fact it was unable to edit the DNS.

@Nicolas One way to avoid this mistake is use getenv('CLOUDRON_MYSQL_USERNAME'), getenv('CLOUDRON_MYSQL_DATABASE') instead of the raw values. This way when you migrate next time, it will pick up the correct database connection values. The full env list for MySQL is at https://cloudron.io/documentation/custom-apps/addons/#mysql

Thanks! The migration went super smooth and fast with the "All In One" plugin.

@girish Thanks for the quick turn around on a fix!

@echokos Right as @NCKNE suggested, you can enable the dynamic dns option under Domains view before migration and take a backup after you enabled it. With that the DNS records will be automatically updated post migration. After migration, you can turn off that option since the IP won't change anyways.

The backups also contain the sql dump and all the data files nicely structured, if required.

@girish said in Migrating the license: If the domain name changes, we will have to do this by hand on our side. nope, the main domain didn't change @girish said in Migrating the license: we might have some license file that you can export/import if you are happy with this kind of license and user are happy, why not keeping it that way Thank for your explanation and replied.

That's great to know. I'm using DigitalOcean at the mo, which I love so far, but it looks a little on the expensive side in comparison to NetCup for instance.

I’m having some similar thoughts about restoring / migrating Cloudron as @d19dotca . So it is possible to set up Cloudron on different primary domains (or IPs) but still keep the same subscription. The use-case I’m aiming for is just to serve the code closer to the readers / users. Will the apps on one Cloudron appear on the other Cloudron? @girish

Thank you @girish for the refund! Much, much appreciated!

Thanks for the reply! Definitely a great start, we will take it from there and refine it to put in our documentation to get more people started.