First try at getting an episode with new instalation. Nothing happened. No error

Help & Support
1

Update. Turns out I just had trouble with one file, but I found other weird things. I’m bolding them. And I still don’t know why that first file I was trying was a problem!

Sonarr seems to be indicating everything is hunky dory, but Sabnzbd never started downloading the file.

This is a new installation. I successfully imported this and other series, no problems. Also, I clicked “test” on sabnzbd and several indexers, and the system did not complain. But this was my first download try.

The log events around the incident are here:

    15-6-13 16:05:42.3|Info|NzbSearchService|Searching 4 indexers for [Hannibal : S03E02]
15-6-13 16:05:42.3|Warn|Newznab|nzbs.in https://nzbs.in/api?t=tvsearch&cat=5030,5040&extended=1&apikey=<removed>&offset=0&limit=100&rid=30909&season=3&ep=2 The request was aborted: Could not create SSL/TLS secure channel.
15-6-13 16:05:42.5|Warn|Newznab|nzb.cat https://nzb.cat/api?t=tvsearch&cat=5030,5040&extended=1&apikey=<removed>&offset=0&limit=100&rid=30909&season=3&ep=2 The request was aborted: Could not create SSL/TLS secure channel.
15-6-13 16:05:43.0|Info|DownloadDecisionMaker|Processing 8 releases
15-6-13 16:05:44.4|Info|Sabnzbd|Adding report [Hannibal.S03E02.1080p.WEB-DL.DD5.1.H.264] to the queue.
15-6-13 16:05:44.5|Info|DownloadService|Report sent to download client. Hannibal.S03E02.1080p.WEB-DL.DD5.1.H.264
15-6-13 16:05:44.5|Info|EpisodeSearchService|Episode search completed. 1 reports downloaded.
15-6-13 16:07:12.6|Warn|DiskSpaceService|Unable to get free space for: D:\

System.IO.DirectoryNotFoundException: D:\
   at NzbDrone.Windows.DiskProvider.GetAvailableSpace(String path) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Windows\DiskProvider.cs:line 33
   at NzbDrone.Core.DiskSpace.DiskSpaceService.<GetDiskSpace>d__4.MoveNext() in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\DiskSpace\DiskSpaceService.cs:line 72

15-6-13 16:07:31.1|Info|RssSyncService|Starting RSS Sync
15-6-13 16:07:33.0|Info|DownloadDecisionMaker|Processing 500 releases
15-6-13 16:07:35.6|Info|RssSyncService|RSS Sync Completed. Reports found: 500, Reports grabbed: 0
15-6-13 16:10:57.8|Warn|DiskSpaceService|Unable to get free space for: D:\

System.IO.DirectoryNotFoundException: D:\
   at NzbDrone.Windows.DiskProvider.GetAvailableSpace(String path) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Windows\DiskProvider.cs:line 33
   at NzbDrone.Core.DiskSpace.DiskSpaceService.<GetDiskSpace>d__4.MoveNext() in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\DiskSpace\DiskSpaceService.cs:line 72

15-6-13 16:11:03.4|Warn|DiskSpaceService|Unable to get free space for: D:\

System.IO.DirectoryNotFoundException: D:\
   at NzbDrone.Windows.DiskProvider.GetAvailableSpace(String path) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Windows\DiskProvider.cs:line 33
   at NzbDrone.Core.DiskSpace.DiskSpaceService.<GetDiskSpace>d__4.MoveNext() in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\DiskSpace\DiskSpaceService.cs:line 72

15-6-13 16:11:37.9|Warn|DiskSpaceService|Unable to get free space for: D:\

System.IO.DirectoryNotFoundException: D:\
   at NzbDrone.Windows.DiskProvider.GetAvailableSpace(String path) in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Windows\DiskProvider.cs:line 33
   at NzbDrone.Core.DiskSpace.DiskSpaceService.<GetDiskSpace>d__4.MoveNext() in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\DiskSpace\DiskSpaceService.cs:line 72

Update: so I’m finding some weird stuff in the Sab logs:

**13 16:52:51,716::WARNING::[interface:190] API Key incorrect, Use the api key from Config->General in your 3rd party program: ::1>Sonarr/2.0.0.3212 (RestSharp/105.0.1.0; Windows/6.2)**

So what’s weird is, there are two API’s in Sonarr, and the second one is for “3rd party apps”. If I use that in Sonarr, Sonarr reports the key is incorrect. If I use the first API code, Sonarr says the test was complete, but this is the API that is causing this error in the Sab logs.

The error I’m getting in the Sab logs in records to this episode is “failed to make”. But I have other usenet download apps interacting with Sabnzbd, and Sab is making directories in the incomplete folder, no problems. I’m baffled!

The plot thickens. When I manual searched and selected a different file, Sab is now downloading it! I don’t understand how these things fit together.

Well, I went through the calendar of stuff I missed in the last two weeks due to this server rebuild, and automatic searches are downloading just fine. Some issue just with the one random file I happened to try, perhaps? Weird.

2

Hi

for nzb.cat - i think for the first part of your issue the SSL/TLS errors, you may have the problem i described here,

nzbs.in api may be the same behind cloudflare? not sure.

https://forums.sonarr.tv/t/nzbplanet-and-nzbcat-ssl-tls-error?source_topic_id=6019
3

That is to be expected.

Actually both keys in Sab are for 3rd party programs.
The first key (called API key) allows 3rd party programs to do “everything” in sab, e.g. adding nzb’s, deleting them, reading the queue, reading the completed downloads list, etc.
The second one (called NZB key) allows 3rd party programs to add nzb’s only, nothing else. This is more safe to use on your indexers site so you can manually send something over to sab for downloading. E.g. usually entering the key in your profile on the indexers site adds a little “send to sab” button next to each nzb when you’re browsing around and want to download something manually. It’s a matter of trust so that the indexer won’t abuse your “full” API key or they get hacked or something. The worst anyone can do with the NZB key is send things to your sab for downloading, not completely mess up your sab with the full API key.

Since sonarr is doing many things with Sab besides just adding nzb’s, it needs the “full” API key. The error quoted above is when you use the NZB key and sonarr tries to e.g. request sab’s queue, which is not possible with the NZB key.

Fixed. This tripped me over for a little while trying to parse your issue :wink:

4

Thanks yeah sorry to be such a PITA but I think it’s working now. :smile: That’s great info. Thanks.