patric99 / remote-torrent-adder

Automatically exported from code.google.com/p/remote-torrent-adder
0 stars 1 forks source link

Failture Server didn't accept data: 200 #66

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What version of Chrome are you using? On what operating system?
Google Chrome   26.0.1410.43 (Official Build 189671) m
OS Windows 

What client (version?) are you connecting to? Are you using SSL?
v3.5

What steps will reproduce the problem?
1. Be on a page that has a link to a torrent, right click on it and select RTAs 
context menu option
2. have Label/Directory interactivity selected in RTAs options
3. From the "Select label and... " dialogue box, make selections and then press 
the "Add torrent" button

What is the expected output? What do you see instead?
Expected is: Popup notification that says success
Instead I see: (see attachment)

Additionally...
this didn't happen with previous versions of ruTorrent; it is only when the 
Lable/directory interactivity is selected that the error message is displayed. 
Otherwise the the torrent is successfully added.

Original issue reported on code.google.com by jhstuc...@gmail.com on 30 Mar 2013 at 10:04

Attachments:

GoogleCodeExporter commented 9 years ago
hey, thanks for the issue report.
unfortunately i couldn't reproduce the error.

i've tried out 
https://code.google.com/p/rutorrent/downloads/detail?name=rutorrent-3.5.tar.gz&c
an=2&q=&sort=-size and RTA works fine with it, even with random values for 
label/directory using the interactive dialog.

can you be more precise about what you're doing (e.g. precise values you enter 
for directory/value - just try bogus ones out and if they don't work, post 
them) and paste the full error message from that notification? please also 
check if the server configuration is "good", in particular whether the paths 
you're downloading to are writable by the user that runs the webserver.

Original comment by jul...@gmail.com on 31 Mar 2013 at 1:22

GoogleCodeExporter commented 9 years ago
I am getting the same error with the same configuration.

Original comment by johntbr...@gmail.com on 3 Apr 2013 at 8:58

GoogleCodeExporter commented 9 years ago
I am having the exact same issue, running chrome on a mac. Any tips?
W

Original comment by walkerca...@gmail.com on 5 Apr 2013 at 1:19

GoogleCodeExporter commented 9 years ago
Also experiencing this issue.

Chrome: 27.0.1453.12 dev-m
OS: Windows 8
Plugin: 1.1.10
ruTorrent: 3.5
Port: 443 (SSL is checked)
Relative path: /webui
Label: Blank
Directory: ~/watch/
Label / Directory Interactivity: Unchecked

Unlike the original poster, this failure occurs whenever I click to add a 
torrent. It does not matter if the interactivity is enabled or disabled - both 
result in a failure error (and with the interactivity unchecked, I do not even 
get a dialog box asking for the label or directory).

Original comment by phi...@codsteeth.com on 5 Apr 2013 at 5:56

GoogleCodeExporter commented 9 years ago
The full error message I get ever time, regardless of file, is:

Failure
Server didn't accept data: 200: 
noty(""+theUILang.addTorrentFailedDirectory,"error");

Original comment by phi...@codsteeth.com on 5 Apr 2013 at 5:58

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Exactly the same error here too.  This is uploading to a deluge seedbox.

Failure
Server didn't accept data: 200: 
noty(""+theUILang.addTorrentFailedDirectory,"error");

Original comment by dean.far...@gmail.com on 6 Apr 2013 at 9:16

GoogleCodeExporter commented 9 years ago
Can't debug this without reproducing. Is someone willing to share his rutorrent 
configuration? with sensitive information redacted, of course. 

dean: with deluge? I'm somewhat certain that the error message is specific to 
rutorrent. Check your RTA configuration. 

Original comment by jul...@gmail.com on 6 Apr 2013 at 9:19

GoogleCodeExporter commented 9 years ago
Absolutely willing to share the config - what files from /.config/rutorrent are 
you looking for? (It's the default whatbox config for me).

Original comment by phi...@codsteeth.com on 7 Apr 2013 at 4:43

GoogleCodeExporter commented 9 years ago
config.php and acces.ini/plugins.ini would be a start.

ideally, i'd take the entire rutorrent folder to find out what the differences 
are to the normal rutorrent version, but let's hope the changes are restricted 
to the configuration files.

Original comment by jul...@gmail.com on 7 Apr 2013 at 11:46

GoogleCodeExporter commented 9 years ago
I took a look, but in the shared environment I don't seem to have access to 
those files. I've posted a ticket for the server admins pointing them to this 
thread - hopefully they'll come and be able to help you out.

Cheers!

Original comment by phi...@codsteeth.com on 9 Apr 2013 at 5:03

GoogleCodeExporter commented 9 years ago
I represent Whatbox, the people behind the particular configuration causing 
this trouble for you.

I believe this issue is unique to our rutorrent environment and a bug on our 
end rather than in this plugin.

The rutorrent developers don't believe it's within the scope of their 
application to properly resolve symlinks which our environment contains due to 
the number of physical disks. I've updated our modifications to rutorrent to 
properly handle this case and behave in line with vanilla rutorrent, so this 
should be fixed for everyone using our services.

Also to my knowledge the intended behavior of rutorrent does not include 
creating the directories you specify when downloading. If you wish the content 
to be downloaded into a custom directory you will need to create the directory 
before you specify it using an extension like remote-torrent-adder.

This particular issue can be closed as invalid barring any opposition.

Original comment by anci...@whatbox.ca on 9 Apr 2013 at 6:22

GoogleCodeExporter commented 9 years ago
hey, cool of you to chime in.

i'd assume folder creation is in the scope of rtorrent. arbitrary folders are 
created just fine on my vm, guess the symlink thing screws the pooch for you 
guys.

anyway, closing this. if anyone isn't helped by the fix, just post again and 
i'll try to figure out what's going on.

Original comment by jul...@gmail.com on 9 Apr 2013 at 10:45