This isn't a direct answer, but I think you're possibly trying to do the wrong thing.
I run Transmission on our home server via transmission-daemon
and connect to it in a number of ways depending on where I am: browser plugins, the built-in Web UI or even the actual Transmission client.
I'm writing under the assumption that if you could connect directly, that would be better.... But you could still remote in over xrdp
and run a local client that connected to the local daemon instance.
Otherwise you just need to square away the networking. I'm not sure I'd trust open access to a Transmission on the internet so if I were you, I'd limit the daemon to 127.0.0.1
and use SSH's port tunnelling to get access:to handle the networking side of things. I don't think I'd trust open access to Transmission on the internet. I'd use ufw
to limit the connecting port (if you have a static IP) or do port tunnelling with SSH.
ssh -L 9091:localhost:9091 user@your_server.com
Then just browse to http://localhost:9091 (or hook up your client to that).