sinamics / ztnet

ZTNET - ZeroTier Web UI for Private Controllers with Multiuser and Organization Support.
https://ztnet.network
GNU General Public License v3.0
392 stars 36 forks source link

[Bug]: vpn migration #444

Open Mhalkyo opened 2 weeks ago

Mhalkyo commented 2 weeks ago

πŸ› Describe the Bug

I tried to migrate the ZTNET VPN, with an export of the database. I carried out this migration on a new machine with a different IP. I reimport the database and put back the three containers. I can connect and I have access to my networks. I'm using a custom route, so I changed the IP of the route to the new IP. I replaced the planet after changing the IP but when I select a network it does not appear, and when I create a network it appears fine but it is impossible to add a computer to it.

Capture d'Γ©cran 2024-06-18 124056 Capture d'Γ©cran 2024-06-18 124116

πŸ” Steps to Reproduce

Perform a migration by exporting and importing the database. Replace the route IP.

πŸ”§ Deployment Type

✨ Expected Behavior

What would be best is if we could perform a migration on another machine that does not have the same IP. I don't know if there is another alternative or if there is something I'm doing wrong.

πŸ“‹ ZTNET Logs

I have no error

πŸ–Ό Screenshots

No response

sinamics commented 4 days ago

Did you export the zerotier docker volume? It looks to me that those ztnet networks does not exist on the new zerotier controller, hence the loading screen.

Mhalkyo commented 4 days ago

I did an export of the postgresql bss, but I didn't get the volume back. I thought that only the bdd was needed?

sinamics commented 3 days ago

You also need to export ZeroTier volume, or at least the /lib/zerotier-one folder, Ztnet is simply a wrapper for the ZeroTier controller, and the networks in the PostgreSQL database must match the existing networks in ZeroTier.

Mhalkyo commented 3 days ago

actually by recovering the data from zerotier it works