Automatically Move Finished Downloads From Your Seedbox to a NAS

Almost every seedbox thread that starts with “how do I get my files home automatically” ends in the same advice: write an rsync cron job on the seedbox. On Evoseedbox that advice does not apply — your account has no shell, so nothing on the box can start a transfer to your house. The transfer has to be pulled from home. That is not a limitation to work around; once you set it up correctly it is more reliable, because your home machine is the one that knows whether it is awake, online and has disk space.

There are three ways to do it, and one way to stop your home side from polling blindly.

Option 1 — Syncthing (easiest, keeps both ends in step)

Syncthing is in the app catalogue and installs on your seedbox in one click. Install it at home too, pair the two devices, and share your completed-downloads folder one-way (set the home side to Receive Only so a local delete never propagates back and pauses your seeding).

1. Install Syncthing from the Apps page in your client area.
2. Open it, add your home machine with its device ID, and accept the pairing at home.
3. Share the folder that your finished downloads land in — if you use labels, share the label folder rather than everything.
4. On the home side set the folder type to Receive Only and pick where the files land.

Syncthing keeps a live connection, so a finished file starts moving within seconds. Its downside is that it holds an index of every file, which costs a little memory on both ends when you seed tens of thousands of torrents.

Option 2 — rclone, pulled from home

If your home box already runs rclone, point an sftp remote at your seedbox and copy from home on a timer:

rclone copy seedbox:downloads/movies /mnt/media/movies --sftp-set-modtime=false --transfers 4

Run it from cron or a systemd timer at home. Use copy, never sync — sync mirrors deletions, and a tidy-up at home would delete the copy you are still seeding. Rclone Browser is also in the catalogue if you would rather drive it from a GUI.

Option 3 — lftp over FTPS or SFTP

The classic, and still the fastest for a lot of small files, because it opens several connections at once:

lftp -e "mirror -c --parallel=4 --only-newer /downloads /mnt/media; quit" -u USER,PASS sftp://your-server.myseedbox.site

--only-newer makes it resumable, -c continues interrupted transfers. Again: run this at home, not on the seedbox.

Stop polling — have the seedbox tell your home server what to fetch

All three options above poll. Polling every five minutes means an average two-and-a-half-minute delay and a lot of pointless directory listings. Liteflow, included with your service, closes that gap: the moment rTorrent marks a download finished, it can call a URL at your house with the name, path, label and size, and your home side fetches exactly that one item.

1. Open your service in the client area and click Open Liteflow on the Automation card.
2. Create New → Start from Template, choose Tell my home server what to fetch, then Use Template and Confirm.
3. Click Torrent Finished and pick your rTorrent connection. Leave the label blank for everything, or set one to restrict it.
4. Click Tell home and replace the URL with your own endpoint — a Home Assistant webhook, a Node-RED endpoint, or a few lines of Flask sitting next to the lftp command above.
5. Publish the flow.

The payload your endpoint receives looks like this:

{"name":"Some.Release.1080p","path":"/home/you/downloads/movies","label":"movies","sizeBytes":8123456789,"sizeGb":"7.57","hash":"AB12…","finishedAt":"2026-09-09T10:04:11.000Z"}

Your endpoint calls the same lftp or rclone command it would have run on a timer, but with the exact path — one transfer, started the second the file exists.

What not to do

Do not follow guides that tell you to mount the seedbox with sshfs or run rsync from the box itself. Both need shell access on the server. Your account has SFTP and FTPS, which is what every option above uses.