I’ve got a membership to a private torrent site that uses cookies for authentication. Their RSS feed isn’t parseable by Sonarr so I’ve written a small rewriting proxy to fix it up. Sonarr now is able to get the feed, parse releases, and grab them with no problem.
Unfortunately, it looks like it might not be properly parsing the downloaded torrent file.
I can’t upload the exact torrent because I’m not interested in leaking the tracker or DNS of the site, but here’s a very lightly modified version of the .torrent file: modified.torrent
Any thoughts? Deluge opens & parses both the original .torrent and the modified one fine, so they seem to be correct at least superficially.
Its possible and likely that the torrent isn’t making it to Sonarr so it fails to parse, perhaps its downloading a webpage due to the cookie authentication required.
Nope, not in Jackett. I looked at how hard it would be to add it and it was more than I was willing to deal with especially since I can’t share it. Much faster for me to put together a rewriting proxy in Node.JS.
When Sonarr couldn’t download the file it said so in the log.
I am having to rewrite the RSS feed so that all the download links go through the proxy, otherwise Sonarr doesn’t seem to properly pass the cookie value configured in the UI. I tested downloading a torrent via the proxy using my browser w/o issue though so it appears to work.
The cookie is likely only passed in the RSS request because the proxy has a different address than the request to download the torrent, sounds like proxying the downloads through your proxy makes the most sense.
Cool, glad that doesn’t sound crazy. Any way of knowing what exactly is causing the torrent parser in Sonarr to barf? I mean I can read the log but I don’t know that package at all so it’s not giving me any obvious clues.
In this case: https://github.com/Sonarr/Sonarr/issues/799 we were seeing it because torcache was returning an HTML page instead of a torrent file, the easiest way to see the content that Sonarr is getting back would be to debug in in Visual Studio and check the content out for yourself.