Transmission-Daemon setup

[wowiesy]

Hi,

I've been using Transmission Client for quite some time and I only found out about the daemon and the web interface recently. I used the Synaptic Package Manager to install transmission-daemon in Ubuntu 9.04. So far I could start and restart the daemon. I used the web interface and so far so good.

I seem to be having a problem with downloading a torrent. When I click on Open, a dialog is presented. The dialog asks for a file to upload or a URL. I intend to download torrents so I tried to browse and locate for a .torrent file in my computer. I press Upload and the dialog exits and I'm back to the web interface, but I don't see any torrents downloading.

Next thing I tried is putting the URL of the torrent (via copy link location) from a different site into the URL text box in the dialog. I click on Upload and then so far, the torrent is listed in the transfers. However, there seems to be no peers connecting. Which configuration item should I look into? On the same machine as where the daemon is running, I also have a Transmission client running (Gtk) and the torrents in the Gtk client are connected to peers and downloading properly.

What other configuration options / steps should I do? Involving user id? file permissions on directories? settings in the settings.json?

[Resilldoux]

If you're having no problem with the GTK version, you could tell the daemon to use the GTK configuration file.
First, stop the daemon by running this command:

Code: Select all

sudo service transmission-daemon stop

Edit the transmission-daemon service by running the following command:

Code: Select all

sudo vim /etc/init.d/transmission-daemon

Once opened, look for the following line...:

Code: Select all

NAME=transmission-daemon

...and place the next following line on top of the line you just looked up

Code: Select all

TRANSMISSION_ARGS="-g /home/yourusername/.config/transmission/"

Don't forget to replace "yourusername" with your actual username.

Also, look up these lines...:

Code: Select all

start_daemon () {
    if [ $ENABLE_DAEMON != 1 ]; then
        log_progress_msg "(disabled, see /etc/default/${NAME})"
    else
        start-stop-daemon --start \
        --chuid $USER \
        --exec $DAEMON -- $OPTIONS
    fi
}

...and replace $OPTIONS with $TRANSMISSION_ARGS.

Now, start the daemon again and hopefully this solved your problem:

Code: Select all

sudo service transmission-daemon start

[Longinus00]

That's not correct, you should change

Code: Select all

CONFIG_DIR= 

to point at your local transmission config directory, usually /home/USER/.config/transmission, in /etc/default/transmission-daemon

You might run into some permission problems so you can either run transmission-daemon as your current user or add yourself to the debian-transmission group and fuss with the files.

To the original poster...
Instead of messing around with this you could just try copying your settings.json from your home directory to /etc/transmission-daemon/

[raph]

Hello, I'm trying to fix the error below. But I cannot find settings.json, already searched without luck:

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.

Many thanks

[raph]

thanks for the reply... anyways these /var/lib/transmission-daemon and /var/run/transmission. are transmission daemon itself... settings.json is not located there!

[Longinus00]

Locations
For the Daemon, all settings are kept in $HOME/.config/transmission-daemon

This is only sometimes true due to inconsistent packaging.

[raph]

Thanks Longinus00
I'm trying to seed a file, I already changed transmission-daemon -w /home/myuser/Videos
and params inside settings.json to look in this directory

Instead of seeding, transmission is download the file to /home/myuser/Desktop but the file and the .torrent I want to seed is under /home/myuser/Videos

Any clues?
kind regards