Skip to content
AquadactylAquadactyl
Manta

Migrating from Wings

Switch an existing node to Manta's native service and executable while preserving game data.

Manta is the Aquadactyl daemon maintained by Euphoria Development. New installations use the manta executable, manta.service and Aquadactyl directories. Existing nodes can migrate without relocating their game files.

ComponentExisting Wings installationNew Manta installation
Executable/usr/local/bin/wings/usr/local/bin/manta
Servicewings.servicemanta.service
Configuration/etc/pterodactyl/config.yml/etc/aquadactyl/config.yml
Game files/var/lib/pterodactyl/volumes/var/lib/aquadactyl/volumes
Log/var/log/pterodactyl/wings.log/var/log/aquadactyl/manta.log

Upgrade your panel first and back up the daemon configuration, systemd unit and game data. Manta retains compatible node APIs and credentials; upstream attribution remains under its MIT license.

Install the checked release

If /opt/manta already exists, use Existing or interrupted checkout instead of cloning again. Select the release checkout before invoking its installer.

git clone --depth 1 --branch v1.3-beta https://github.com/Aquadactyl/manta.git /opt/manta &&
cd /opt/manta &&
sudo bash scripts/install.sh v1.3-beta &&
/usr/local/bin/manta version

If the legacy service is running, the installer updates its existing executable as well as installing manta. It retains previous copies and restores them if the service start fails. It leaves the legacy service running until you explicitly switch its unit.

Switch to manta.service

Follow Migrate the service, including backing up and comparing custom unit options before disabling the old service and enabling the new one. Only one daemon service should run at a time.

Copy the complete existing config rather than regenerating it. An old partial config without config_version keeps its inherited data, user and network settings. Do not insert the new defaults marker into an old partial config: that would select fresh-install defaults for omitted values. The first save materializes the old settings explicitly.

Game containers remain running during the daemon restart; console and SFTP connections briefly disconnect. Schedule outside installations, backups and transfers. Check the panel's node heartbeat, console, file manager, SFTP and a test server after switching.

Data migration and recovery

The service migration preserves existing data directories and user IDs. Moving game files is a separate maintenance operation: stop affected containers, back up and copy files with permissions preserved, update the node and local config, and recreate Docker bind mounts before restarting servers. See existing data and Docker deployments.

For rollback, stop and disable manta before restoring the old executable/config and enabling the old service. Keep backups until verification succeeds. See the recovery guide.

Continue with additional configuration or the Wings vs Manta benchmarks.