Nyaa indexer not getting seed/peer #

v3 Testing
#1

Sonarr version (exact version): 3.0.1.470
Mono version (if Sonarr is not running on Windows): 5.20.1.19
OS: Debian 9
Debug logs:
https://pastebin.com/NWiMdmF1
Description of issue:
The Nyaa indexer (configured to use nyaa.si) is not pulling the number of seeders and peers from each entry parsed. It looks like the RSS feed does contain such data. For example:

<item>
<title>
[BlueLobster] Magic Users Club (01-19) [480p] (Batch) (Mahou Tsukai Tai!)
</title>
<link>https://nyaa.si/download/1140736.torrent</link>
<guid isPermaLink=“true”>https://nyaa.si/view/1140736</guid>
<pubDate>Sat, 04 May 2019 03:06:34 -0000</pubDate>
<nyaa:seeders>3</nyaa:seeders>
<nyaa:leechers>35</nyaa:leechers>
<nyaa:downloads>0</nyaa:downloads>
<nyaa:infoHash>1af26a891aa8e596ff8538c628d3e610b3b7b7ee</nyaa:infoHash>
<nyaa:categoryId>1_2</nyaa:categoryId>
<nyaa:category>Anime - English-translated</nyaa:category>
<nyaa:size>5.3 GiB</nyaa:size>
<nyaa:comments>0</nyaa:comments>
<description>
<![CDATA[
<a href=“https://nyaa.si/view/1140736”>#1140736 | [BlueLobster] Magic Users Club (01-19) [480p] (Batch) (Mahou Tsukai Tai!)</a> | 5.3 GiB | Anime - English-translated | 1AF26A891AA8E596FF8538C628D3E610B3B7B7EE
]]>
</description>
</item>

The size, language, and quality still appear to be parsed correctly. The trace logs have been attached above. Please let me know if you need anymore info.

#2

Forgot to mention that outside of changing the website url to ‘https://nyaa.si’, I also changed the Additional Parameters to ‘&c=1_2’ so it would only search the English-Only category. The feed contents are still the same, though

https://nyaa.si/?page=rss&c=1_2&term=Sewayaki+Kitsune+no+Senko+san+1

#3

Hello. Any update on this problem? The thread was going to close

#4

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

#5
#6

That is the old nyaa API which isn’t something we have maintained since the original site when offline. If they’re interested in supporting the torznab API it’s soemthing they could implement, but we don’t have plans to update the parsing on Sonarr’s side.