Preparation
- Create and check out fresh backup.
- Prepare SSH access to the new server and at least 5 GB of free space.
- If the original Remnawave is separate from Axottle, prepare SSH. Go to the original server. First, successfully find it runtime.
- Configure the API address of the new dashboard, DNS, TLS and reverse proxy. The old domain, before the DNS changes, can continue to lead to the source.
Stages
- Transfer Panel. Axottle checks servers, transfers environment and dump, deploys a new stack and checks the panel with an existing API token. The panel version comes from the source: the relocation is not an update to Remnawave.
- Stop the old panel. Click “Stop the old panel” or If you confirm that you’re stopping yourself, as long as both panels are running, they can Control the same nodes. Stop the panel container. The original database and server are saved.
- Check and rebind nodes. View the list and reasons for inaccessibility. If necessary, Axottle updates the connection of available managed nodes Many nodes are already fitting the new panel after restoration. Dump; missed nodes remain in the report with the cause.
- Switching Axottle. Changes the address of the existing connection, Therefore, the associated Flow, nodes and profiles retain the binding.
Verification
- Wait to check the new API and compare the number of users and nodes.
- Make sure that the old panel is stopped and each node has a clear result.
- After switching, check sync, client connection, and links The subscription domain is portable in the settings, but its DNS needs to be checked.
- Recheck backup profiles: records with the old server are not overwritten automatically, they are listed in the final summary.
