Transmission-daemon config

rogg · 2009-08-11 13:47:46

Hey guys,
I'm a bit confused on how to set up the Transmission-Daemon, i was wondering if someone could provide some insight

so i stop the daemon (transmissiond) and located/edited the configuration file .config/transmission-daemon/settings.json. Even after disabling rpc-whitelist-enabled, i consistently get the following error when trying to access the webui:

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.

Does anybody know what im doing wrong here, as i am also unsure of how to create webui authentication credentials.
my settings.json is as follows:
{
"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": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": false,
"dht-enabled": true,
"download-dir": "\/home\/test\/Downloads",
"encryption": 1,
"lazy-bitfield-enabled": true,
"message-level": 2,
"open-file-limit": 32,
"peer-limit-global": 240,
"peer-limit-per-torrent": 60,
"peer-port": 51414,
"peer-port-random-high": 65535,
"peer-port-random-low": 49152,
"peer-port-random-on-start": false,
"peer-socket-tos": 0,
"pex-enabled": true,
"port-forwarding-enabled": true,
"preallocation": 1,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"ratio-limit": 2.0000,
"ratio-limit-enabled": false,
"rpc-authentication-required": true,
"rpc-bind-address": "0.0.0.0",
"rpc-enabled": true,
"rpc-password": "{8609cc68bea16183926927620d8b4ba924dd3df27XGLaHGw",
"rpc-port": 9091,
"rpc-username": "testaccount",
"rpc-whitelist": "127.0.0.1",
"rpc-whitelist-enabled": false,
"speed-limit-down": 100,
"speed-limit-down-enabled": false,
"speed-limit-up": 100,
"speed-limit-up-enabled": false,
"umask": 18,
"upload-slots-per-torrent": 14
}

thanks in advance

jozef00 · 2009-08-28 10:06:08

Hello rogg,

Install transmission-cli and transmission-gtk on an Arch installation with a Desktop, then configure transmission with the GUI. Then copy the settings.json to your server.

With kind regards,

Jozef00

vacant · 2009-08-28 10:26:30

Have a look at /etc/rc.d/transmissiond. Notice is references "TRANS_USER". Notice it includes "/etc/conf.d/transmissiond".

So as root:

1) edit /etc/conf.d/transmissiond and set TRANS_USER to your username, e.g.

TRANS_USER="paul"

2) restart transmission

I think that's the converntinal why to control it.

Subsequently, any changes to your user setting should be obeyed by the daemon.

rogg · 2009-08-30 14:33:15

Hi guys,
thanks so much for the replies

I have change TRANS_USER to TRANS_USER="username", when accessing localhost:9091 iam now prompted for authentication
Do you know where i am to set the settings for the transmission-daemon, i have apparently changed it once because i am able to authenticate using username with password test
When i run transmission-daemon -d, i am given an output from /home/username/.config/transmission-daemon/settings.json, however when i modify it to change rpc password the password does not change

Am i editing the right file?, i have tried using transmission-daemon -parmater to change things around but nothing seems to be happening

vacant · 2009-08-30 15:09:00

I'm not sure as I always use transmission-remote (cli client) but localhost:9091 got me straight in on firefox. Have you tried setting the authentication info using "transmission-remote -n" ?

Last edited by vacant (2009-08-30 15:13:39)

rogg · 2009-08-30 15:39:01

do you always go transmission-remote -n username:password?
i just tried that, but i was not able to change the password
i am getting very confused

vacant · 2009-08-30 16:04:02

rogg wrote:

do you always go transmission-remote -n username:password?
i just tried that, but i was not able to change the password

No, I've never had to use the "-n" option.

Relevant bits from my settings.json:

    "rpc-authentication-required": false,
    "rpc-bind-address": "0.0.0.0",
    "rpc-enabled": true,
    "rpc-password": "(snipped out, this was a long random string)",
    "rpc-port": 9091,
    "rpc-username": "",
    "rpc-whitelist": "127.0.0.1",
    "rpc-whitelist-enabled": true,

Last edited by vacant (2009-08-30 16:04:23)

rogg · 2009-09-04 13:46:58

thats really strange, i keep editing that file. I currently have very similar settings, but nothing quite seems to be working
particularly the password settings =[

sinister99 · 2009-09-07 02:32:48

rogg wrote:

thats really strange, i keep editing that file. I currently have very similar settings, but nothing quite seems to be working
particularly the password settings =[

I've been recently having this problem after I updated transmission-daemon but using a different platform. I ended up just ditching the json file and running transmission-daemon directly with the switches I needed (see man)

Fackamato · 2009-09-30 15:54:00

There's a bug - transmission overwrites settings.json on exit - make it non-writable after you've modified it and you should be fine.

schef · 2011-02-04 12:49:55

Transmission is reading the config file (eg. /etc/transmission-daemon/
settings.json) upon startup, storing its values in memory, altering
these values based on any changes made while the program is running,
and then writing all these values back out to settings.json when it is
shut down.

This means if you wish to change the configuration by editing
settings.json you must first shut down transmission-daemon so as to
let it write out any stored values, and then restart it after having
saved settings.json.

I presume the best way to change settings while the daemon is running
is from the web interface or using the RPC (but getting that to work
was beyond me).

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539936

corvinus · 2011-09-12 08:03:35

It's not recommended to run daemon under your user, since chosen user should have no password, and daemon should run even if you're not logged.
See https://trac.transmissionbt.com/wiki/He … ge/General

For this and other Transmission-related topics, see instructions at https://trac.transmissionbt.com/wiki

vassie · 2012-06-07 11:56:32

There is a new wiki entry for Arch that implies that it is OK to run the daemon as your normal user

https://trac.transmissionbt.com/wiki/UnixServer/Arch

ewaller · 2012-06-07 13:16:38

Moderator: It was suggest this is an old thread, come back to life. This thread is a little on the old side, but I think it is still on track. Carry on.

Arch Linux

#1 2009-08-11 13:47:46

Transmission-daemon config

#2 2009-08-28 10:06:08

Re: Transmission-daemon config

#3 2009-08-28 10:26:30

Re: Transmission-daemon config

#4 2009-08-30 14:33:15

Re: Transmission-daemon config

#5 2009-08-30 15:09:00

Re: Transmission-daemon config

#6 2009-08-30 15:39:01

Re: Transmission-daemon config

#7 2009-08-30 16:04:02

Re: Transmission-daemon config

#8 2009-09-04 13:46:58

Re: Transmission-daemon config

#9 2009-09-07 02:32:48

Re: Transmission-daemon config

#10 2009-09-30 15:54:00

Re: Transmission-daemon config

#11 2011-02-04 12:49:55

Re: Transmission-daemon config

#12 2011-09-12 08:03:35

Re: Transmission-daemon config

#13 2012-06-07 11:56:32

Re: Transmission-daemon config

#14 2012-06-07 13:16:38

Re: Transmission-daemon config

Board footer