I have the transmission app running perfectly on my freedombox. I can access its web interface both in my local network and when outside.
Though, I cant seem to figure out any way to access it remotely with a client app (running on phone or desktop). If anyone has been successful, I would appreciate any guidance on how they setup their client.
I submitted a merge request to enable remote access with transmission. The essential problem is that GUIs expect to use simple HTTP Basic authentication where FreedomBox has implemented more complex single sign-on. The merge request will setup Basic authentication on a slightly different URL /transmission-remote/rpc.
The change will be available in next version of Freedombox. In the meanwhile, if you wish to enable remote access do the following:
Create a file /etc/apache2/conf-available/my-transmission-remote.conf with following contents:
My client successfully connected, though I am getting a “Parsing error” - one which I will look into to see if I can solve. It’ probably related to my Transmission configuration which I fiddled with to this point.
In regard to my “not being connected” issue, I think I can mark this post [SOLVED] (though for some reason I cant edit my initial post).
For anyone who wants to configure their client, I’m sharing my settings below:
Looks like web server on your FreedomBox has returned a 301 redirect to another location when contacting the URL https://mydomain.com:443/transmission-remote/rpc. This should not have happened. If you done some experimentation with Apache configuration removing it might help. To check that all the configuration on the server side working, run the following test:
Open https://mydomain.com:443/transmission-remote/web using a web browser. It should open a username/password dialog. Enter FreedomBox credentials (admin account or account with bit-torrent group). You should see Transmission web UI and it should work as expected. If this part does not work, something wrong with web server configuration.
After doing some search online, I found one site that mentioned of 301 errors happening if a Rewrite module created loop with a Location module.
It just hit me that my-transmission-remote.conf was enabled while the transmission-plinth.conf was also active. I went to @sunil 's very recent commit (to be merged) and copied his apache configuration for the transmission-plinth.conf, disable my new my-transmission-remote.conf and presto! All is in order now.
Thanks @sunil and everybody else for the support. Really happy to have this working.
@Ged296123 if you modify a file that is shipped by FreedomBox (transmission-plinth.conf), then FreedomBox won’t automatically upgrade to the next version. You will need to manually upgrade and choose to get the new configuration file discarding old changes.
BTW, having the configuration in two files my-transmission-remote.conf and transmission-plinth.conf should have worked fine. That is why I suggested that change.
@sunil my bad… didn’t know I’d break the update mechanism : (
After 1 manual update - would it get back to normal?
Maybe I made a mistake when copying your configuration file with my-transmission-remote… I’ve been trying to get this to work like I want for some time - I could easily have skipped something… thank you again.
During the manual upgrade, when it asks you to pick which configuration file you want to keep, select the one that comes with the new package (this will have configuration you need anyway). After this, you are back on track with the automatic upgrades.