Downloading nzb for episode failed

Sonarr version (exact version): 3.0.4.1023
Mono version (if Sonarr is not running on Windows): 6.10.0
OS: Unraid 6.8.3
Debug logs: https://pastebin.com/KfNvfP6V
Description of issue:

I seem to be having issues downloading nzb files from my indexer which in turn disables the indexer due to failures.

Here is the relevant parts of the log:

20-12-21 12:32:02.2|Error|Sabnzbd|Downloading nzb for episode ‘Le*****.S01E09.720p.HDTV.x264-W4F’ failed (http://192.168.1.217:5075/getnzb?apikey=(removed)&searchresultid=80002e1efbc694asdfue234j75f3ec4)

[v3.0.4.1023] System.Net.WebException: Error: ProtocolError: 'https://api.omgwtfnzbs.me/api?t=get&id=Cih87gkr&apikey=(removed) —> System.Net.WebException: Error: ProtocolError
at System.Net.WebConnection.InitConnection (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x0015e] in /build/mono/src/mono/mcs/class/System/System.Net/WebConnection.cs:282

If I enter the url of either directly they both work fine. I recently upgraded to v3 in attempt to fix this issue as it was also happening before I upgraded.

Fyi, I’m also using the exact same setup for Radarr and it works fine as well.

My current setup involves Sonarr 3 > Hydra 2 (sole indexer) > Sabnzbd with VPN using privoxy

Thx

Some additional updates based on latest troubleshooting:

  1. This issue is also happening on Radarr
  2. If I disable the proxy it seems to work fine which lead me to believe it’s an issue with the Sabnzbd+VPN container I’m using which uses privoxy
  3. However I’m not seeing any issues in the sab logs and more importantly the proxy seems to work fine with other apps (Hydra) or even using it on my mac to proxy traffic.

Any ideas??

Does hydra have an option to proxy the downloads through it instead of Sonarr fetching the NZB directly from the indexer?

Either that or avoiding the VPN are my only suggestions currently.

Finally figured this out!

Turns out my indexer had blocked the proxied ip I was using through my VPN due to abuse by other users using the same dynamic ip range.

The solve was to connect to a different server which then generated a new ip.

1 Like

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