Moving Hetzner Cloud Server to other location

[robi]

@Kubernetes said in Moving Hetzner Cloud Server to other location:

With N8N I have no experience, so I may not be a help with that. Sorry

nothing a quick video can't get you up to speed on quickly ;-]

[Kubernetes]

@robi Ok, could you link your thread pls?

[robi]

@Kubernetes For you, sure.. https://forum.cloudron.io/post/67715

[ccfu]

Is there a particular reason you want to move your Cloudron from Nuremberg to Falkenstein? I would have thought it would be easier to move the storage boxes from Falkenstein to Nuremberg (if you really need everythting in one DC) so you don't need a new IP.

[Kubernetes]

I think for perfomance reasons it's better to have them in the same datacenter. Unfortunately there are no Storageboxes available to book for DC Nuremberg. That's why I want to migrate to Falkenstein.
However, I just started the migration process and the IP of the new cloud server seems to be okay in terms of reputation

[Kubernetes]

Migration went fine within 39 Minutes in total (37GB Snapshot)
The DynDNS Feature didn't work for me. So I initiated the DNS Sync and it seems everything works fine again - but in Falkenstein now
Thanks guys!

[ccfu]

That was quick and good to know if I ever need to migrate. I also have servers in Nuremberg and storage boxes in Falkenstein, though so far I haven't had any performance issues.

[robi]

@Kubernetes said in Moving Hetzner Cloud Server to other location:

The DynDNS Feature didn't work for me. So I initiated the DNS Sync

I recently had an emergency IP change as it seems the upstream network provider was swapped, and had the DynDNS feature enabled which worked for the Cloudron server itself, but not for the hosted sites.

To fix it I also had to resync DNS for 100+ sites.

@girish why doesn't DynDNS feature update all the records for all the sites that no longer match?

IMO the manual Sync should not be required.

[girish]

@robi as in, update records which cloudron didn't create/doesn't maintain?

[robi]

@girish quite the opposite, it created all of them but did not maintain them after the IP change.

[girish]

@robi dyndns is run as a cron job every 1 hour. This was changed last release to run every 10 mins.

[Kubernetes]

@girish Ahh, this explains it. I was not patient enough and was assuming DynDNS is triggered when IP is changed

[robi]

@Kubernetes same here, or at least on reboot, like a run once, then on cron.

@girish that was the odd part, the dashboard domain had the IP set right, but all other sites didn't and needed re-syncing