NovaCloud-Hosting Docs

Migrate from WireGuard to NetBird

Step-by-step instructions for migrating an IP Transit tunnel from WireGuard to NetBird.

This guide replaces your existing WireGuard tunnel with NovaCloud-Hosting's managed NetBird tunnel.

Plan for a short interruption. Once you stop the existing tunnel, systems using it may lose Internet access. Do not begin the cutover until you have received the setup token and coordinated the migration with Support.

Migration in 4 steps

1. Open a support ticket and request the setup token

Open a support ticket and tell us:

  • which host you are migrating
  • whether you use Linux or Proxmox
  • when you want to perform the migration

Wait for the NetBird setup token and confirmation from Support. The IP Transit service installer will ask for this token.

2. Migrate your current setup

Select your current setup and follow only the instructions shown for it. Before the interruption, create a backup and make sure you have independent management access, such as the Proxmox console or a KVM console.

3. Verify connectivity

First, check the Linux or Proxmox host:

systemctl is-active netbird-iptransit.service
ip link show wt10
ip -4 route show table 10
ip -6 route show table 10

Expected result:

  • The service reports active.
  • The wt10 interface exists.
  • Routing table 10 contains the routes required by your setup.
  • The assigned IP addresses are reachable externally, and outbound traffic uses the expected IP address.
  • On Proxmox, the affected virtual machines and containers have connectivity again.

If a check fails, do not remove the old configuration yet. Inspect the service with systemctl status netbird-iptransit.service and send the output to Support.

4. Remove the old WireGuard configuration

Complete this step only after all checks pass.

Only on Linux hosts that used the previous NovaCloud direct-assignment script:

rm -f /etc/cron.d/novacloud-ipt-da \
  /opt/novacloud-ipt-da.sh \
  /opt/novacloud-ipt-da.env

Keep your backup until the NetBird tunnel has operated reliably for an appropriate period. The migration is now complete.

Additional information

On this page