Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: vpn migration #444

Open
1 of 2 tasks
Mhalkyo opened this issue Jun 18, 2024 · 0 comments
Open
1 of 2 tasks

[Bug]: vpn migration #444

Mhalkyo opened this issue Jun 18, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Mhalkyo
Copy link
Contributor

Mhalkyo commented Jun 18, 2024

🐛 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

  • Docker
  • Standalone

✨ 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

@Mhalkyo Mhalkyo added the bug Something isn't working label Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant