Transmission

Further information ... Looking at the debug information it appears that transmission-remote picks up the use of an alternative port e.g. 9092, but then seems to hardcode the RPC url to http://localhost:9092/transmission/rpc i.e. it seems to ignore any alternative URL settings specified e.g. /subsit...

Hi rb07,

Thanks for your reply.
I already have the "rpc-url" field updated as the following, but still doesn't work:
"rpc-url": "/subsite1/transmission/"

As mentioned it was working well in previous versions.

Thanks for your help.

I have been running multiple instances of transmission-daemon for a while now as mentioned in this post: https://forum.transmissionbt.com/viewtopic.php?f=8&t=12092 The web inteface works nicely for each instance and downloads work fine, however transmission-remote no longer works except on the d...

I've worked out how to do this, so I thought I would post what needed to be done incase anyone else wanted to do the same thing. I fixed the web interface by: 1. Updating to the latest version of transmission-daemon with the ppa 2. In the settings.json file for the second daemon updating the "r...

I currently have a web interface running which works nicely redirecting traffic to HTTPS with nginx. Browsing to http://example.com redirects to https://example.com/transmisson/web and the web interface works as expected. Browsing to http://example.com/subsite redirects to https://example.com/subsit...