You are not logged in.
Pages: 1
Hi,
Transmission Web interface seems to be poorly documented, unless I'm missing something obvious. Well,
# /etc/rc.d/transmissiond start
then
localhost:9091
do the trick, more or less.
My first question: I've got a GUI version seeding some torrents (transmission-qt). Stopping GUI and starting WebUI I expected the Web version to continue seeding, but no such luck. Is there a way to tell it to carry on with the existing set of torrents?
Offline
https://trac.transmissionbt.com/wiki/ConfigFiles
If you want to swap between the two applications, all you have to do is pass in a different config directory with the -g command-line option. For example, to have the daemon pick up where the gtk+ client left off, run transmission-daemon -g ~/.config/transmission.
Change the path to whatever client you want to resume from and you're done.
Oops, I should mention that you should be running the daemon and then you can access it through whatever front end you like.
Last edited by Meyithi (2011-01-24 03:46:41)
Offline
Thanks, Meyithi!
I discovered that you have to run
$ transmission-daemon -g ~/.config/transmission
every time you start it. You can't really use /etc/rc.d/transmissiond start (or just put it into /etc/rc.conf), or can you?
Another question: is it possible to set the thing as a default application for torrents in Firefox?
Last edited by Llama (2011-01-24 04:20:34)
Offline
I discovered that you have to run
$ transmission-daemon -g ~/.config/transmission
every time you start it. You can't really use /etc/rc.d/transmissiond start (or just put it into /etc/rc.conf), or can you?
Take a look at /etc/conf.d.d/transmissiond, there is an TRANS_ARGS field where you can specify what config files to use, for example I use..
TRANS_ARGS="-T --blocklist -g $TRANSMISSION_HOME/.config/transmission-daemon"
because I use the daemon as a base and access it through the web interface.
Offline
Thanks!
Another problem: can't access the "server":
stovepipebox:9091 on the "client"
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.
On the "server", I put my "client" IP into settings.json:
"rpc-whitelist": "127.0.0.1,192.168.1.34",
"rpc-whitelist-enabled": true,
restarted the daemon, but still 403.
Offline
Another trouble: can I tell WebUI where to store data files (on a per torrent basis)?
Offline
Pages: 1