Transmission

Unfortunately, I'm not sure if this will help me. Firstly, I'm not sure if transmission-remote can be passed the raw base64-encoded metainfo data. I think you can only pass in the filename (or URL) of the torrent file. This, of course, works just fine on my machine, but I'm trying to make use of the ...

I'm trying to write a tool that will send torrent file metainfo to the daemon via RPC, but I can't seem to figure out the correct method to encode the metainfo.
I am using Javascript and can take advantage of Mozilla's window.btoa function, which base64 encodes a string. However, if I pass in the ...

I'm having some trouble with my transmission-daemon, and I think it has to do with the fact that I recently set it up to run as "guest" user (which is my public user on the media server).
I copied the .config folder from /root to the guest user's home directory, and I modified the startup script to ...

You answered your own question: if there is an error (as you see with transmission-remote) the Web client shows nothing. In other words, if you can't add the torrent using an URL with transmission-remote, the same goes for the Web client.

And you made a mistake, you're not using version 1.62 you ...

Hi all,
I current have the 1.62 transmission, but I'm still seeing problems with Opening a URL from the web UI. If my memory serves me, this was actually working for me the very first day I got this up and running (about a week ago). Since then I have been modifying the settings.js slightly (to test ...