Synology

Tunely runs on Synology NAS systems through Container Manager. The Synology installation is one long-running tunely-agent container that uses the public ghcr.io/tunely-eu/agent image, one persistent /data mount, and one agent token from the Tunely dashboard.

Everything below is done through the DSM web interface. You do not need SSH, router port forwarding, or published NAS ports for the agent itself.

Requirements

• Synology NAS with DSM and Container Manager installed from Package Center.
• Admin access to the DSM web interface.
• An agent token from the Tunely dashboard.
• A persistent folder on the NAS for agent data.
• Outbound HTTPS access from the NAS to Tunely.
• Network access from the NAS to the local services you want to publish.

Install Container Manager

Open Package Center in DSM, search for Container Manager, and install the package. After installation, open Container Manager from the DSM main menu.

Create The Data Folder

Open File Station and create a folder for the agent, for example:

/volume1/docker/tunely-agent/data

If your Docker shared folder is on a different Synology volume, adjust the /volume1 part. This folder is mounted into the container as /data and must survive container replacement, NAS reboots, and image updates.

Create The Container Manager Project

1. Open Container Manager.
2. Go to Project.
3. Select Create.
4. Use tunely-agent as the project name.
5. Use the parent folder, for example /volume1/docker/tunely-agent, as the project path.
6. Choose the option to create the project from a docker-compose.yml file.

Use this Compose definition and replace the token value before creating the project:

services:
  tunely-agent:
    image: ghcr.io/tunely-eu/agent
    container_name: tunely-agent
    restart: unless-stopped
    environment:
      TOKEN: replace-with-your-agent-token
    volumes:
      - /volume1/docker/tunely-agent/data:/data

If your NAS uses another volume, change the left side of the volume mount to match the folder you created. The right side must stay /data.

Start the project when the wizard asks whether the container should run after creation. Container Manager will pull the image, create the container, and keep it configured for automatic restart.

Check The Agent

Open Container in Container Manager and select tunely-agent.

• The container should be running.
• Logs should show the agent starting and connecting to Tunely.
• The Tunely dashboard should show the agent as online after the first successful connection.

The agent does not expose an HTTP setup page on the NAS. Services, domains, and target addresses are configured in the Tunely dashboard.

Network Notes

Use target addresses that are reachable from inside the container:

• For services on another LAN device, use the device LAN IP address or local DNS name.
• For services running directly on the Synology NAS, use the NAS LAN IP address instead of localhost or 127.0.0.1.
• For services in the same Container Manager project, service names can work as container DNS names.

Do not add port mappings for tunely-agent unless a future guide explicitly requires them. The agent opens outbound connections to Tunely.

Update

To update the agent, stop the tunely-agent project, refresh the image through Container Manager, and start the project again with the same Compose definition. Do not delete the data folder mounted at /data.

Troubleshooting

If the agent does not come online:

• Confirm that TOKEN contains the agent token copied from the dashboard.
• Check the container logs in Container Manager.
• Confirm that the NAS can reach api.tunely.eu over HTTPS.
• Confirm that service target addresses are reachable from the NAS LAN.
• Avoid localhost targets unless the target service is inside the same container.