starred/Radarr

Fork 0

mirror of https://github.com/Radarr/Radarr.git synced 2026-03-02 22:57:34 -05:00

Radarr can't grab any release from HeBits tracker #9340

New issue

Open

opened 2026-02-20 00:12:55 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-20 00:12:55 -05:00

Owner

Originally created by @Kirill200889 on GitHub (Jan 10, 2026).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

Hey team :)

First of all, thank you very much for maintaining and contributing to this amazing project.

Since approx. a month ago, radarr can't grab any release from the HeBits tracker. The search works and it displays results from HeBits. Tracker testing works too. However, it can't grab any release with the following error:

[v6.0.4.10291] MonoTorrent.TorrentException: Invalid torrent file specified ---> MonoTorrent.BEncoding.BEncodingException: Illegal BEncodedDictionary. The attributes are not ordered correctly. Old key: comment, New key: announce

Downloading the torrent manually from HeBits and loading in the client (qBittorrent) works without any issues.
Sonarr can grab from HeBits.
Search and download direclty in prowlarr works as well.

I believe something has been changed on HeBits side and the 'monotorrent' which wasn't updated for two years can't handle it or something.

Can it be checked please?

Expected Behavior

It should be able to grab releases from HeBits, it worked before.

Steps To Reproduce

Try to grab any release in radarr.

Environment

- OS: Windows 11 Pro 25H2 26200.7462
- Radarr: 6.0.4.10291
- Docker Install: No
- Using Reverse Proxy: No
- Browser: Chrome
- Database: Sqlite 3.50.4

What branch are you running?

Master

Trace Logs? Not Optional

radarr.trace.txt

Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @Kirill200889 on GitHub (Jan 10, 2026). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Current Behavior Hey team :) First of all, thank you very much for maintaining and contributing to this amazing project. Since approx. a month ago, radarr can't grab any release from the HeBits tracker. The search works and it displays results from HeBits. Tracker testing works too. However, it can't grab any release with the following error: `[v6.0.4.10291] MonoTorrent.TorrentException: Invalid torrent file specified ---> MonoTorrent.BEncoding.BEncodingException: Illegal BEncodedDictionary. The attributes are not ordered correctly. Old key: comment, New key: announce` - Downloading the torrent manually from HeBits and loading in the client (qBittorrent) works without any issues. - Sonarr can grab from HeBits. - Search and download direclty in prowlarr works as well. I believe something has been changed on HeBits side and the 'monotorrent' which wasn't updated for two years can't handle it or something. Can it be checked please? ### Expected Behavior It should be able to grab releases from HeBits, it worked before. ### Steps To Reproduce Try to grab any release in radarr. ### Environment ```markdown - OS: Windows 11 Pro 25H2 26200.7462 - Radarr: 6.0.4.10291 - Docker Install: No - Using Reverse Proxy: No - Browser: Chrome - Database: Sqlite 3.50.4 ``` ### What branch are you running? Master ### Trace Logs? **Not Optional** [radarr.trace.txt](https://github.com/user-attachments/files/24543557/radarr.trace.txt) ### Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided. - [x] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman added the

Type: Bug

Status: Needs Triage

labels

2026-02-20 00:12:55 -05:00

deekerman commented

2026-02-20 00:12:56 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Jan 10, 2026):

It's not a Radarr issues, and also not quite a MonoTorrent as the library just imposes the Bencode specifications.

https://code.google.com/archive/p/bencode-net/wikis/BEncode.wiki

A dictionary is encoded as d{contents}e. The elements of the dictionary are again encoded and concatenated, in such a way that each value immediately follows the key associated with it. All keys must be byte strings and must appear in lexicographical order. A dictionary that associates the values 42 and "spam" with the keys "foo" and "bar", respectively, would be encoded as follows: "d3:bar4:spam3:fooi42ee". (This might be easier to read by inserting some spaces: "d 3:bar 4:spam 3:foo i42e e".)

@mynameisbogdan commented on GitHub (Jan 10, 2026): It's not a Radarr issues, and also not quite a [MonoTorrent](https://github.com/alanmcgovern/monotorrent/) as the library just imposes the Bencode specifications. https://code.google.com/archive/p/bencode-net/wikis/BEncode.wiki > A dictionary is encoded as d{contents}e. The elements of the dictionary are again encoded and concatenated, in such a way that each value immediately follows the key associated with it. **_All keys must be byte strings and must appear in lexicographical order._** A dictionary that associates the values 42 and "spam" with the keys "foo" and "bar", respectively, would be encoded as follows: "d3:bar4:spam3:fooi42ee". (This might be easier to read by inserting some spaces: "d 3:bar 4:spam 3:foo i42e e".)

deekerman commented

2026-02-20 00:12:56 -05:00

Author

Owner

@Kirill200889 commented on GitHub (Jan 10, 2026):

It's not a Radarr issues, and also not quite a MonoTorrent as the library just imposes the Bencode specifications.

https://code.google.com/archive/p/bencode-net/wikis/BEncode.wiki

A dictionary is encoded as d{contents}e. The elements of the dictionary are again encoded and concatenated, in such a way that each value immediately follows the key associated with it. All keys must be byte strings and must appear in lexicographical order. A dictionary that associates the values 42 and "spam" with the keys "foo" and "bar", respectively, would be encoded as follows: "d3:bar4:spam3:fooi42ee". (This might be easier to read by inserting some spaces: "d 3:bar 4:spam 3:foo i42e e".)

Thank you for looking into it! Is there anything I can do on my side to fix it?

@Kirill200889 commented on GitHub (Jan 10, 2026): > It's not a Radarr issues, and also not quite a [MonoTorrent](https://github.com/alanmcgovern/monotorrent/) as the library just imposes the Bencode specifications. > > https://code.google.com/archive/p/bencode-net/wikis/BEncode.wiki > > > A dictionary is encoded as d{contents}e. The elements of the dictionary are again encoded and concatenated, in such a way that each value immediately follows the key associated with it. **_All keys must be byte strings and must appear in lexicographical order._** A dictionary that associates the values 42 and "spam" with the keys "foo" and "bar", respectively, would be encoded as follows: "d3:bar4:spam3:fooi42ee". (This might be easier to read by inserting some spaces: "d 3:bar 4:spam 3:foo i42e e".) Thank you for looking into it! Is there anything I can do on my side to fix it?

deekerman commented

2026-02-20 00:12:56 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Jan 10, 2026):

Sadly this needs to addressed by the tracker to follow the BEncode specifications and sort the dictionary.

I'm not aware of an app that might fix this on fly, and would not be possible to hook it to Radarr anyway.

@mynameisbogdan commented on GitHub (Jan 10, 2026): Sadly this needs to addressed by the tracker to follow the BEncode specifications and sort the dictionary. I'm not aware of an app that might fix this on fly, and would not be possible to hook it to Radarr anyway.

deekerman commented

2026-02-20 00:12:57 -05:00

Author

Owner

@Kirill200889 commented on GitHub (Jan 10, 2026):

@mynameisbogdan
Thank you for the right direction. Checked the tracker's forum, found many threads.
The last update on the 17th of November, broke it. Unfortunately, they are not going to fix it, since "the tracker isn't supposed or planned to work with the *Arrs"... That's sad.

@Kirill200889 commented on GitHub (Jan 10, 2026): @mynameisbogdan Thank you for the right direction. Checked the tracker's forum, found many threads. The last update on the 17th of November, broke it. Unfortunately, they are not going to fix it, since "the tracker isn't supposed or planned to work with the *Arrs"... That's sad.

deekerman commented

2026-02-20 00:12:57 -05:00

Author

Owner

@KovaLavan commented on GitHub (Jan 27, 2026):

I ran into the same issue specifically with HeBits.

In my case the torrent files returned by HeBits download fine and work when added
manually to qBittorrent, but Radarr fails with MonoTorrent parsing errors
(e.g. Invalid torrent file specified, BEncodingException).

As a workaround, I built a small reverse proxy that sits between Radarr/Sonarr
and the Torznab indexer (Prowlarr/Jackett). It normalizes non-canonical bencoded
.torrent files before Radarr sees them, without modifying the info dictionary
or infohash (safe for private trackers).

This avoids patching Radarr or MonoTorrent and allows grabs from HeBits to succeed.

Docker + usage:
https://hub.docker.com/r/kovalavan/arr-monotorrent-fix

Source:
https://github.com/KovaLavan/arr-monotorrent-fix

@KovaLavan commented on GitHub (Jan 27, 2026): I ran into the same issue specifically with HeBits. In my case the torrent files returned by HeBits download fine and work when added manually to qBittorrent, but Radarr fails with MonoTorrent parsing errors (e.g. `Invalid torrent file specified`, `BEncodingException`). As a workaround, I built a small reverse proxy that sits between Radarr/Sonarr and the Torznab indexer (Prowlarr/Jackett). It normalizes non-canonical bencoded .torrent files before Radarr sees them, without modifying the info dictionary or infohash (safe for private trackers). This avoids patching Radarr or MonoTorrent and allows grabs from HeBits to succeed. Docker + usage: https://hub.docker.com/r/kovalavan/arr-monotorrent-fix Source: https://github.com/KovaLavan/arr-monotorrent-fix

deekerman commented

2026-02-20 00:12:57 -05:00

Author

Owner

@sagipael commented on GitHub (Feb 5, 2026):

I ran into the same issue specifically with HeBits.

In my case the torrent files returned by HeBits download fine and work when added manually to qBittorrent, but Radarr fails with MonoTorrent parsing errors (e.g. Invalid torrent file specified, BEncodingException).

As a workaround, I built a small reverse proxy that sits between Radarr/Sonarr and the Torznab indexer (Prowlarr/Jackett). It normalizes non-canonical bencoded .torrent files before Radarr sees them, without modifying the info dictionary or infohash (safe for private trackers).

This avoids patching Radarr or MonoTorrent and allows grabs from HeBits to succeed.

Docker + usage: https://hub.docker.com/r/kovalavan/arr-monotorrent-fix

Source: https://github.com/KovaLavan/arr-monotorrent-fix

Thanks!
Working like a charm

@sagipael commented on GitHub (Feb 5, 2026): > I ran into the same issue specifically with HeBits. > > In my case the torrent files returned by HeBits download fine and work when added manually to qBittorrent, but Radarr fails with MonoTorrent parsing errors (e.g. `Invalid torrent file specified`, `BEncodingException`). > > As a workaround, I built a small reverse proxy that sits between Radarr/Sonarr and the Torznab indexer (Prowlarr/Jackett). It normalizes non-canonical bencoded .torrent files before Radarr sees them, without modifying the info dictionary or infohash (safe for private trackers). > > This avoids patching Radarr or MonoTorrent and allows grabs from HeBits to succeed. > > Docker + usage: https://hub.docker.com/r/kovalavan/arr-monotorrent-fix > > Source: https://github.com/KovaLavan/arr-monotorrent-fix Thanks! Working like a charm