টরেন্ট ডাউনলোড
মেম্বাররা ম্যাগনেট লিংক বা .torrent দেন, সার্ভারের Transmission বা uTorrent তা তাঁদের অ্যাকাউন্টে নামায়, অগ্রগতি, সীমা ও অ্যাডমিন তালিকাসহ। প্রিমিয়াম।
The Torrent Download plugin adds a Torrent tab to the uploader. A member pastes a magnet link or picks a .torrent file; a torrent engine on your server - Transmission or uTorrent - downloads it, and when it is complete the files are imported into the member's account in a folder named after the torrent. The member watches progress, peers and speed on the tab and can cancel; you see every torrent in the panel and set limits per day and at once.
It is the "download from torrent to my cloud" feature of a premium file host: large public datasets, Linux images and the like arrive on the server's fast line instead of the member's.
Switching it on
Torrent Download is a premium plugin: it needs the torrent-download addon on your licence. Buy it at lcpanel.com, press Check again now on Admin → Configuration → License, then switch Torrent Download on at Admin → Extensions → Plugins (Manage Plugins). Its admin page appears under Extensions as Torrents (/admin/plugin/torrent-download).
It needs a torrent engine running on the same server (or one the web server can reach and whose download folder it can read):
| Engine | How the plugin talks to it | Default port |
|---|---|---|
| Transmission (RPC) | transmission-daemon's RPC interface, with the session-id handshake. | 9091 |
| uTorrent (Web UI) | The Web UI's token API. | 8080 |
Progress is synced and finished torrents are imported by the cron job track_torrents (Track torrents, every minute) - see Scheduled jobs.
Settings
| Setting | What it does |
|---|---|
| Engine | Transmission (RPC) or uTorrent (Web UI). |
| Engine host / Engine port | Where the engine listens (default 127.0.0.1, 9091). |
| Engine username / Engine password | The engine's RPC or Web UI login. |
| Download folder | Where the engine writes files (default /var/lib/transmission-daemon/downloads). The web server must be able to read it: the import copies the files from there. |
| Paid accounts only | On (default): premium, moderator and admin accounts may add torrents. Off: any package with Enable Url Downloading may. Trial accounts never. |
| Max torrents per day (free) / (paid) | Default 2 and 20. |
| Max at once (free) / (paid) | Running torrents per member, default 1 and 5. |
| Largest torrent (GB) | A torrent bigger than this is removed from the engine and marked failed (default 20; 0 = the package upload limit decides). |
| Remove from the engine once imported | On: the torrent and its data are deleted from the engine after the import, keeping its disk free. |
The admin page: Torrents
Every torrent members added: Added, Torrent (name and total size), Owner, Progress bar, Peers, Speed (down and up), Status (queued, downloading, importing, completed, failed, cancelled) with the engine's message when something went wrong. Filter by Status or by Name / member. A running torrent has Cancel (removes it from the engine with its data); Contents folds out the files inside; Delete removes the row. Two buttons at the top: Test engine asks the engine for its session (Transmission) or its list (uTorrent) and reports The engine answered or the error, and Sync now runs the cron job's work at once.
What the member sees
In the upload dialog of the file manager (Uploads) a Torrent tab appears for members who may use it. It says Paste a magnet link or pick a .torrent file. The site downloads it for you into a folder named after the torrent., has a magnet box, a file picker for .torrent files and Add torrent, and shows the member's limits (Limits: 20 per day, 5 at once.). Under it, the list of their torrents refreshes every few seconds with progress, size, speed, peers and status; a running one can be cancelled and a finished one cleared.
Accepted sources are a magnet:?xt=urn:btih:... link, a URL ending in .torrent, or an uploaded .torrent file. The torrent is handed to the engine at once and the row starts as downloading. When the engine reports it complete, the import makes a folder named after the torrent in the folder the uploader was open on (in the active team workspace when there is one), recreates the torrent's sub-folders, and stores every file through the normal road - so the package's Max Upload Size, blocked extensions and storage allowance apply to each file. The member gets a notification: Torrent "..." finished: 12 file(s) are in your account. Files that the engine downloaded but the web server cannot read fail with a message that names the folder to check.
Typical workflow
- Install
transmission-daemon, set an RPC username and password in itssettings.json, allow RPC from the web server's address, and note the download folder. - In the plugin settings type the host, port, login and Download folder; make the download folder readable by the web server user.
- Press Test engine on Extensions → Torrents.
- Add a small public torrent yourself from the uploader's Torrent tab and watch it come in.
Tips
- Keep Paid accounts only on and the free limits low: torrents cost the server bandwidth and disk twice (the engine's copy, then storage).
- A torrent the engine no longer knows is marked failed after six hours, so a restart of the engine does not leave rows spinning forever.
- Both engines were written against their documented protocols; the test button is the quickest way to prove the connection on your server before members try.
- Public torrents can carry anything. Your Blocked extensions everywhere setting (Site settings) is applied to every imported file, and the Abuse Reports page covers torrent files like any other.