Failure server responded with an irregular http error code about remote-torrent-adder

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I can confirm this but i dont know how to investigate this

Original comment by [email protected] on 26 Mar 2013 at 8:19

[GoogleCodeExporter]

for one, you could re-check all of the values you've entered in configuration, 
leave empty the directory and label entries and see if it works then, and if 
not, post a more detailed error log, in particular the http error code would be 
interesting.

also, as a routine first round troubleshot, try adding a torrent from the 
rutorrent webui manually and see if that works.

Original comment by [email protected] on 26 Mar 2013 at 11:19

[GoogleCodeExporter]

first check: from the webui, "add torrent" -> add torrent floating window, 
Torrent URL, WORKS
it works for torrent file and magnet link

where i can find the error log?

Original comment by [email protected] on 31 Mar 2013 at 7:11

[GoogleCodeExporter]

i got this

log(theUILang.addTorrentFailed);

can be useful?

Original comment by [email protected] on 31 Mar 2013 at 8:48

[GoogleCodeExporter]

I'm also getting the "irregular HTTP error code".

Original comment by [email protected] on 2 Sep 2013 at 5:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I had this code but it was actually the relative path causing this error.  

Enter ONLY the text in quotation marks: 
http://someserver.com"/some/path/to/webui"/
Note: this folder should contain the "php" directory.

I made the mistake not reading it properly. Not the whole path just the 
question marks!

Original comment by [email protected] on 7 Sep 2013 at 5:03

[GoogleCodeExporter]

I can also confirm this. Adding torrent manually works. Via Remote Torrent 
Adder it returns an http error 400, invalid request.

(uTorrent 3.3.1, Chrome 31.0.1650.26 beta-m on Win7)

Original comment by [email protected] on 20 Oct 2013 at 11:48

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

no use replying to this issue in the future, please create a new one.

there are many causes to this problem, usually a botched configuration.

Original comment by [email protected] on 11 Jan 2014 at 12:41

• Changed state: WontFix