-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't add torrents from private trackers #16
Comments
Not sure what's happening there TBH. Does this happen on all links or just some? I'm currently working on refactoring the code a huge amount, so hopefully this won't be a problem in the next release. |
hmm now that I check, it seems to only happen with my torrent site.. a general test from https://www.ubuntu.com/download/alternative-downloads works fine. |
Sounds like a bug I'd like to get fixed though... any way you could provide me a page that this is happening on? |
private site, i've sent you an invite. :) |
Aha. So the issue here is that the server requires your user session cookie, or else you get sent a 404. Since Deluge doesn't have your cookies, it gets a 404 and just sees it as a bad link. I need to have the extension download the .torrent locally (so that your user session cookie is used) and send the raw data to deluge. This has been on my internal to-do list for a while. |
ahh cool. no rush, awesome you could figure out the reason though. Thanks! |
I'd love to see this implemented as well. |
Any updates on this? Having the same issue with a private tracker. Torrent files from regular sites seem to get added just fine. |
+1 for this feature, would be a great addition as it's my main use-case. (thanks for building this awesome chrome extension in your spare time!) |
Hi, I'm unsure if my update to Deluge 1.3.12 caused this, or the fact that I moved it to a new VM in my local network, but I'm unable to add torrents anymore via the context menu. The chrome addon "deluge siphon" still seems to work but I prefer yours. :)
All I'm seeing in the background page log is:
Any ideas?
The text was updated successfully, but these errors were encountered: