Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
You are connecting to transmission daemon via nginx proxy. It causes problems.
Original comment by j...@cp-lab.com
on 18 Aug 2011 at 6:39
Hello,
As it seems that the problem is known, is there a solution ?
Original comment by ribotphi...@gmail.com
on 20 Aug 2011 at 12:22
Connect to transmission daemon directly.
Original comment by j...@cp-lab.com
on 20 Aug 2011 at 5:35
Thank you.
And how do I do that ?
In my case, connection options are set as follow :
- Remote host : IP adress of the Freebox on my local network (192.168.1.254)
- Port : 9091
- Username and Password : Those used to connect to the Freebox
- Use SSL is not selected
- Use a proxy is NOT selected
- Paths are left blank
- Misc is unchanged
Thank you for your advices
Original comment by ribotphi...@gmail.com
on 20 Aug 2011 at 7:07
[deleted comment]
Somehow you are connecting to the daemon via nginx proxy. Check your network
configuration and services running on the destination computer...
The problem is not related to transgui or transmission daemon.
Original comment by j...@cp-lab.com
on 21 Aug 2011 at 2:19
OK. Thank you.
The problem is that the transmission deamon is not running on a computer but on
an ADSL box working also as router for my local network (Ethernet and WiFi).
And I can't see the parameters of this box or change its configuration about
the way transmission deamon is running.
I will try to have informations through the developers of this box.
Original comment by ribotphi...@gmail.com
on 21 Aug 2011 at 6:12
[deleted comment]
Sorry to dig up an old topic, but I had the same problem, and found a
discussion thread with the solution : in the options window, uncheck the seed
ratio box.
The error message will no longer show up, and you will be able to modify your
options.
Looks like the problem could be related to transgui after all ?
Original comment by rek...@gmail.com
on 23 Sep 2012 at 6:05
I'm sure this issue is related to transgui.
These command lines works by RPC:
curl -v http://mafreebox.freebox.fr:9091/transmission/rpc -u freebox:password
-d '{"arguments": {"blocklist-enabled": "true"}, "method": "session-set"}'
curl -v http://mafreebox.freebox.fr:9091/transmission/rpc -u freebox:password
-d '{"arguments": {"blocklist-url":
"http://www.bluetack.co.uk/config/level1.zip"}, "method": "session-set"}'
curl -v http://mafreebox.freebox.fr:9091/transmission/rpc -u freebox:password
-d '{"method": "blocklist-update"}'
Full command-lines here:
http://www.freebox-v6.fr/wiki/index.php?title=Télécharger_des_fichiers_avec_la
_SeedBox
It means this is an implementation problem with trangiu, as the Freebox accepts
the previous commands.
Original comment by vianney....@googlemail.com
on 6 Jan 2013 at 6:10
You can try to dig further by dumping full HTTP request sent by transgui and
trying to send it via curl.
Since it is nginx error, the problem is related to nginx. Maybe wrong
configuration.
Original comment by j...@cp-lab.com
on 6 Jan 2013 at 8:00
Seems that problem come from "Seed ratio". If you uncheck it then you can
modify other parameters without the Bad Gateway problem.
Original comment by captaine...@gmail.com
on 26 Jan 2013 at 8:32
It's another proof that something wrong in your environment.
Original comment by j...@cp-lab.com
on 26 Jan 2013 at 10:55
still not fixed ? :(
Original comment by lemachin...@gmail.com
on 22 Jul 2013 at 11:09
Original issue reported on code.google.com by
vianney....@googlemail.com
on 18 Aug 2011 at 3:18