Updating your iTDS Server

When an iTDS update has been released you may follow these instructions to update your iTDS.

1.  Create a Backup

Choose the guide that matches your current version:

• Backup iTDS 3.x
• Backup iTDS 4.0.x – 4.1.x
• Backup iTDS 4.2.x

2.  Update Paths

2.1  Virtual‑Machine Deployments

SSH into the VM (default creds maltego / tasx) and then continue with the Docker steps below.

2.2  Docker‑Compose Deployments (online)

# Log in to the registry (credentials in delivery e‑mail)docker login registry.paterva.com# Stop running containersdocker compose -f itds.yml down# Replace compose file with latest version and pull new imagescurl -o itds.yml "https://dolores.paterva.com/customers/docker/download_compose/12/"docker compose -f itds.yml pull# Start the updated stackdocker compose -f itds.yml up -d# Tail logs until startup completesdocker compose logs -f# Fix ownership of paired configurations (once stack is healthy)sudo docker exec -u 0 itds-itdsphp-1 chown -R php:php /usr/local/paired_config

2.3  Docker‑Compose Deployments (offline)

Use a host with Internet connectivity to pull the images, save them to tar files, then copy and load them on the isolated host.

# On connected hostdocker login registry.paterva.comcurl -o itds.yml "https://dolores.paterva.com/customers/docker/download_compose/12/"docker compose -f itds.yml pulldocker save -o itdsapache.tar  registry.paterva.com/itdsapache:latestdocker save -o itdsdb.tar      registry.paterva.com/itdsdb:latestdocker save -o itdsphp.tar     registry.paterva.com/itdsphp:latest# Transfer *.tar files to the offline host and run:docker load -i itdsapache.tardocker load -i itdsdb.tardocker load -i itdsphp.tar# Proceed with the usual compose-down / compose-up flow (see 2.2)

3.  Updating iTDS to 4.5.x

The iTDS 4.5.x supports SQLite as the default database, so before updating you will need to create a backup of your current server before updating.

Please note that MySQL is considered legacy and user are strongly encouraged to migrate to SQLite.

If you still wish to continue using MySQL, please refer to MySQL legacy support.

The iTDS MySQL to SQLite data migration follows these high-level steps:

1. Create a backup of the existing iTDS
2. Update the existing iTDS
3. Activate license
4. Restore the backup on the new iTDS

3.1 Create a backup of the existing iTDS

(Use the backup guides listed above)

3.2 Update the existing iTDS

Run the Docker commands below as root, either by using sudo, or by running them from a root shell.

Login to Docker registry

docker login registry.paterva.com

Stop your iTDS

docker compose -f itds.yml down

Replace the compose file and pull new images

curl -o itds.yml "https://dolores.paterva.com/customers/docker/download_compose/12/"docker compose -f itds.yml pull

Start your updated iTDS

docker compose -f itds.yml up -d

3.3 Activate server

Navigate to https://<server_ip>:8000/itds/activate to access the activation UI.
From the activation page under Upload License Certificate, click Choose File and upload your .pfx license. Click Submit to activate your server.

3.4 Restore the backup on the new iTDS

With the backup file created on the old server, import it onto your new server.

1. On the new server, open the Backup and Restore page in the admin interface (https://<server_ip>:8000/itds/backup).
2. Under Restore Backup, select the ZIP exported from the old server.
3. Click Restore Backup.