Transmission client configuration

donhylo · November 27, 2016, 12:33pm

I’m trying to configure the Transmission client in combination with the NAS box.

What I’ve done so far is enabling the client in LuCi and downloading and installing the Transmission Remote GUI. The problem is that the connection is being refused.

What I can’t figure out is:

In LuCi:

What should I set for the “Run daemon as user” option?
What the url for downloads should be? I have the NAS mounted so would this url work: /mnt/nas/downloads?
Do I need to change anything in the Peer and Peer Port sections?
In the RPC section, I understood that I should whitelist my own address, so in RPC whitelist I put 192.168.11.*

In the GUI:

What the host should be? I though 192.168.1.1 but it doesn’t work

Thanks for the help

ubermutant · November 27, 2016, 6:38pm

i chose root, that works, however once transmission works, you may wish to check if it works with lower level account too
if /mnt/nas/downloads directory exists and it is on the SSD/HDD drive, and there is write and read permission on it , then that is ok. basically any directory works, technically.
i have enabled port forwarding, not sure if you really need it with your config. otherwise the port can be anything (the high ports preferred above 10000)
yes i whitelisted 127.0.0.1 and 192.168.*.*

GUI

yes its the router local address:9091/transmission/web/ you should also have a direct link from LUCI services transmission config page, (top right)

keep in mind, i am not professional, but hope the above helps.
keep trying, i managed to make it work and it works like a charm (although i directed the download folder onto a usb flash key )

donhylo · November 28, 2016, 8:07pm

Thanks for your help. I’m making progress but still no connection.

I get this message

Any idea?

ubermutant · November 28, 2016, 8:38pm

please check Luci-> SYSTEM -> Startup page whether transmission is enabled and running or not.

donhylo · November 28, 2016, 9:19pm

Good catch but still no connection.

In LuCI > Services > Transmission I left the following settings, which I believe are by default:

Config file directory: /tmp/transmission
RPC URL: /transmission

Could that be the issue?

ubermutant · November 28, 2016, 9:51pm

well, i changed the config file directory to a new directory i made on the usb drive. (so that i can find the config and see if the daemon created it)

the RPC URL is the same as yours (the default)

my RPC config section is like this
RPC enabled tick
RPC port 9091 ( suppose this can be anything unused)
RPC bind address 192.168.1.1 (router local ip)
RPC url /transmission (this is the default)
RPC whitelist enabled tick
RPC whitelist 127.0.0.1, 192.168.star.star
RPC auth required unticked

i would also try to reboot ( i know linux does not need to have rebooted, but still, might work)

ubermutant · November 28, 2016, 9:58pm

indent preformatted text by 4 spaces
root@turris:/tmp/run/mountd/sda1/torrent# cat settings.json
{
    "alt-speed-down": 50,
    "alt-speed-enabled": false,
    "alt-speed-time-begin": 540,
    "alt-speed-time-day": 127,
    "alt-speed-time-enabled": false,
    "alt-speed-time-end": 1020,
    "alt-speed-up": 50,
    "bind-address-ipv4": "192.168.1.1",
    "bind-address-ipv6": "::",
    "blocklist-enabled": false,
    "blocklist-url": "http://www.example.com/blocklist",
    "cache-size-mb": 2,
    "dht-enabled": true,
    "download-dir": "/tmp/run/mountd/sda1/torrent/",
    "download-queue-enabled": true,
    "download-queue-size": 4,
    "encryption": 1,
    "idle-seeding-limit": 30,
    "idle-seeding-limit-enabled": false,
    "incomplete-dir": "//Downloads",
    "incomplete-dir-enabled": true,
    "invalid-key": false,
    "lazy-bitfield-enabled": true,
    "lpd-enabled": true,
    "message-level": 1,
    "peer-congestion-algorithm": "",
    "peer-id-ttl-hours": 6,
    "peer-limit-global": 240,
    "peer-limit-per-torrent": 60,
    "peer-port": 51413,
    "peer-port-random-high": 65535,
    "peer-port-random-low": 49152,
    "peer-port-random-on-start": false,
    "peer-socket-tos": "default",
    "pex-enabled": true,
    "port-forwarding-enabled": true,
    "preallocation": 1,
    "prefetch-enabled": true,
    "queue-stalled-enabled": true,
    "queue-stalled-minutes": 30,
    "ratio-limit": 2,
    "ratio-limit-enabled": false,
    "rename-partial-files": true,
    "rpc-authentication-required": false,
    "rpc-bind-address": "192.168.1.1",
    "rpc-enabled": true,
    "rpc-password": "{534be694f9be1fd7d08fe88495adf52287eb548bftz4oPfx",
    "rpc-port": 9091,
    "rpc-url": "/transmission/",
    "rpc-username": "",
    "rpc-whitelist": "127.0.0.1,192.168.*.*",
    "rpc-whitelist-enabled": true,
    "scrape-paused-torrents": true,
    "scrape-paused-torrents-enabled": true,
    "script-torrent-done-enabled": false,
    "script-torrent-done-filename": "",
    "seed-queue-enabled": false,
    "seed-queue-size": 10,
    "speed-limit-down": 100,
    "speed-limit-down-enabled": false,
    "speed-limit-up": 100,
    "speed-limit-up-enabled": false,
    "start-added-torrents": true,
    "trash-original-torrent-files": false,
    "umask": 18,
    "upload-slots-per-torrent": 14,
    "utp-enabled": true,
    "watch-dir": "/tmp/run/mountd/sda1/torrent/",
    "watch-dir-enabled": true
}

this is the whole settings.json

donhylo · December 3, 2016, 12:34am

Ok so today I tried again and it still is a failure.

I finally got what you were saying by “changing the config file URL to see if the daemon created it”. So I changed the URL, created the new directory beforehand, and I see the new settings.json in the new directory. The rest of the configuration file is the same as yours. Still not working and no error message, just a bunch of blank spaces and then “–>” at the end.

Could the problem be related with the firewall or the port being closed? How do I check for that?

Thanks

donhylo · December 3, 2016, 1:15am

Ok so that was the case, the port 51413 was closed. I thought that the UPnP would do that automatically, as it is the case with the Transmission software. but no… that wasn’t the case.

So in LuCI > Firewall > Port Forwards I add a new port forward as follows:

From any host in WAN and the external port 51413
Forward to LAN to the internal IP 192.168.1.1 and the internal port 51413

Is that correct and secure?

markerfit · December 4, 2016, 3:51pm

Any idea how to fix this?

Couldn't find Transmission's web interface files!

Users: to tell Transmission where to look, set the TRANSMISSION_WEB_HOME environment variable to the folder where the web interface's index.html is located.

donhylo · December 4, 2016, 4:04pm

In LuCI > Services > Transmission, do you see the grey box that says ‘Open Web Interface’?

Make sure you enabled and started Transmission in In LuCI > System > Startup and/or try to reboot the service.

Make sure you have installed the packages for Transmission to work:

luci-app-transmission
luci-i18n-transmission-en
luci-i18n-transmission-cs
(optional) transmission-cli-openssl
transmission-daemon-openssl
transmission-web

Try to reboot your TO

markerfit · December 4, 2016, 6:35pm

I have no web interface button in LuCi, Transmissiin is up and running (restarted the process several times to make sure settings applied). Tried to transmission-web but package could not be found. And I also tried rebooting the router, just in case.

Weird thing is that the first time I configured Transmission the web interface link appeared in the menu, but I had to restore the router to factory defaults for a different reason and I lost the configuration. I don’t remember doing something different for the second setup (although I am sure I did) but I can’t seem to get it right this time.

donhylo · December 4, 2016, 7:03pm

In LuCI > System > Software

To install the packages, you simply type ‘transmission’ in the filter box and hit ‘Find Packages’

In the ‘Status’ section below, you’ll get a list of the packages you already have installed. Click on ‘Available Packages’ to find and install what you need (especially Transmission Web).

Make sure the Transmission deamon is up and running. You can do that in LuCI (LuCI > System > Startup) or in Terminal:

/etc/init.d/transmission enable
/etc/init.d/transmission start

markerfit · December 4, 2016, 8:07pm

Geez, installing the web interface was the step I skipped on the second setup (dunno how in the world I forgot to do this). Many thanks!!!

Nick87 · December 5, 2016, 8:19pm

I get this error message when I click the web interface button.
Though I have the right RPC whitelist entry as far as I can see.
Any ideas?

403: Forbidden

Unauthorized IP Address.

Either disable the IP address whitelist or add your address to it.

If you’re editing settings.json, see the ‘rpc-whitelist’ and ‘rpc-whitelist-enabled’ entries.

If you’re still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.

donhylo · December 5, 2016, 8:38pm

My RPC settings are as follows, I hope that helps.

RPC enabled: tick
RPC port: 9091
RPC bind address: 0.0.0.0
RPC URL: /transmission/
RPC whitelist enabled: tick
RPC whitelist: 127.0.0.1,192.168.*.*
RPC authentication required: tick
RPC username: your-username
RPC password: your-password

Nick87 · December 5, 2016, 8:59pm

Hmm…I removed all the packages and reinstalled everything from scratch

Now i see the transmission web interface but immediately get a “connection failed, could not connect to the server” in the web interface.
Is RPC authentication really necessary?

Nick87 · December 5, 2016, 9:03pm

Ok, I reloaded the page and it seems to work. the right URL to access is http://192.168.1.1:9091/transmission/web/

For some reason it first said: http://192.168.1.1:9091/transmissionweb/
Might’ve been my own fault.

Always a good idea to restart the transmission service under “startup” or even rebooting it seems.

Thanks for the help, going trying to download a torrent to test.

Nick87 · December 5, 2016, 9:14pm

It worked! File downloaded succesfully.

Many thanks.

donhylo · December 7, 2016, 8:05pm

Hey @Nick87, now it’s my turn to run into trouble.

Everything was fine until it stopped working and I get the same message you got:

403: Forbidden
Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.
If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.

I tried everything and nothing works. Tweaking the configuration, removing everything and installing it back. Nothing.

The weird part is that even when the daemon is not installed I still get the same error, as if the problem was something not related to Transmission at all. How did you open the port in your firewall?

Any thoughts are welcome at this point, thanks.