Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sailing:transmission [2023/12/05 15:50] – willy | sailing:transmission [2024/02/27 12:30] (current) – removed willy | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Prev to: [[sailing: | ||
- | Next to: [[sailing: | ||
- | ---- | ||
- | ====== Transmission ====== | ||
- | |||
- | [[https:// | ||
- | |||
- | I have been experiencing quite some issues running Transmission lately (errors in connecting to trackers mostly, which leads to zero peers to download from) which come out of nowhere. Since YMMV, here are the instructions for Transmission for you. | ||
- | |||
- | |||
- | |||
- | ===== Installation ===== | ||
- | |||
- | Transmission is easily installed and managed within Gentoo linux since there is an ebuild for it. All you need to do is to emerge it: | ||
- | <code bash> | ||
- | > emerge -v transmission | ||
- | </ | ||
- | |||
- | This step will create a dedicated // | ||
- | <code bash> | ||
- | > usermod -a -G media transmission | ||
- | </ | ||
- | |||
- | Also, you want to move Transmission home folder under **/ | ||
- | <code bash> | ||
- | > mv / | ||
- | </ | ||
- | |||
- | then you need to change the user transmission runs under, this is to ensure that the other tools can fetch the downloads once complete. This is pretty easy, open the file **/ | ||
- | < | ||
- | runas_user=transmission: | ||
- | </ | ||
- | |||
- | One last required step is to ensure that the other tools can access the transmission folder (to reach the download folders inside), so: | ||
- | <code bash> | ||
- | > chgrp media / | ||
- | </ | ||
- | |||
- | ===== Reverse-Proxy configuration ===== | ||
- | |||
- | Before you proceed, you should make Transmission accessible via the reverse-proxy, | ||
- | <file txt transmission.conf> | ||
- | |||
- | # Transmission | ||
- | location / | ||
- | proxy_pass http:// | ||
- | } | ||
- | </ | ||
- | |||
- | Add this to your **/ | ||
- | < | ||
- | include " | ||
- | </ | ||
- | |||
- | and restart nginx: | ||
- | <code bash> | ||
- | > / | ||
- | </ | ||
- | |||
- | ===== Startup ===== | ||
- | |||
- | You need to change some default Transmission settings now, edit the file **/ | ||
- | < | ||
- | " | ||
- | " | ||
- | " | ||
- | " | ||
- | </ | ||
- | |||
- | Where: | ||
- | * download-dir: | ||
- | * rcp-url: the base-url where the Transmission web GUI is reverse-proxied | ||
- | * bind-address-ipv4 / rpc-bind-address: | ||
- | |||
- | |||
- | Now, setup the daemon to start at boot, and start it now: | ||
- | <code bash> | ||
- | > rc-update add transmission-daemon default | ||
- | > / | ||
- | </ | ||
- | |||
- | |||
- | ===== Integration ===== | ||
- | |||
- | Every download client needs to be integrated in your other tools. Unfortunately, | ||
- | |||
- | Every *Arr's tool has the same // | ||
- | |||
- | Prowlarr is a special case: you only need to define the downloader IF you plan to search from the Prowlarr web GUI, otherwise it's not needed. And no, Prowlarr will **not** synchronize your downloader to the other *Arr' | ||
- | |||
- | |||
- | |||
- | ===== Usage ===== | ||
- | |||
- | Head to [[http:// | ||
- | |||
- | |||
- | Now, head on to install the more downloaders... | ||
- | |||
- | |||
- | |||
- | |||
- | ---- | ||
- | Next to: [[sailing: | ||
- | |||
- | Prev to: [[sailing: |