Sonarr version (exact version): 2.0.0.4913
Mono version (if Sonarr is not running on Windows): 4.2.2
OS: OS X 10.11.6
((Debug logs)): https://pastebin.com/KenbdzPX
Description of issue: Since Sonarr automatically updated to the latest version today it won’t connect to the Rarbg indexer any more. I’ve tried generating a new token but that didn’t fix it.
Same here. Ubuntu 16.04. None of the torrent search engines that I have set up are working. Happened right after the update.
It’ll be fixed in a hotfix as soon as I can confirm it’s working.
3 Likes
Yep same here
Same here!
Version
2.0.0.4913
Mono Version
4.3.0
On a Raspberry Pi 2 with Jessie!
Same here! but torrentleach seem to work completely fine for me, i just tested it and only RARBG seem to have this issue at this stage. Will the update be pushed to everyone?
4919 Now works with anything except RARBG … I’m assuming it’s on their end.
same here for all indexers but newer version
Sonarr version (exact version): 2.0.0.4919
Mono version (if Sonarr is not running on Windows): 4.4.2
OS: OS X 10.12.5
Description of issue: Since Sonarr automatically updated to the latest version no usenet indexers are available.
ystem.Net.WebException: Error: ConnectFailure (TLS Support not available.): 'https://api.nzb.su/api/api?t=caps&apikey=997a63243d853534871b826295db5248’
at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0017f] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:87
at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0003c] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:35
at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request) [0x0007e] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:122
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00019] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:59
at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00007] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:223
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.FetchCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x00068] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:57
That’s actually an interesting one. It’s OSX specific, unexpected and what’s even more surprising is that no-one on the develop branch reported issues, despite it being out there for 5 days.
Then I push it to master and the shit hits the fan within 5h.
Quite frustrating.
Can you switch to the ‘connectfailure’ branch, I’m using that to diagnose OSX specific issues.
It was, if you look in the logs their backend went down and you were just getting proxy messages, they are back now BTW.
Thanks! That was some pretty fast turn around. Works great again.
1 Like
I don’t think it’s fixed for me in Ubuntu 16.04:
17-8-3 08:29:40.9|Info|RssSyncService|Starting RSS Sync
17-8-3 08:29:41.3|Warn|Newznab|OZnzb.com Error: ConnectFailure (TLS Support not available.): 'https://api.oznzb.com/api?t=caps&apikey=(removed)
17-8-3 08:29:42.0|Warn|Newznab|nzbplanet.net Error: ConnectFailure (TLS Support not available.): 'https://api.nzbplanet.net/api?t=caps&apikey=(removed)
17-8-3 08:29:42.0|Info|DownloadDecisionMaker|No results found
17-8-3 08:29:42.0|Info|RssSyncService|RSS Sync Completed. Reports found: 0, Reports grabbed: 0
17-8-3 08:35:42.4|Warn|Newznab|Unable to connect to indexer
[v2.0.0.4919] System.Net.WebException: Error: ConnectFailure (TLS Support not available.): 'https://api.nzbplanet.net/api?t=caps&apikey=(removed) at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0017f] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:87
at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0003c] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:35
at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request) [0x0007e] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:122
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00019] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:59
at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00007] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:223
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.FetchCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x00068] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:57
17-8-3 08:35:42.4|Warn|NzbDroneErrorPipeline|Invalid request Validation failed:
– Unable to connect to indexer, check the log for more details
17-8-3 08:35:51.8|Warn|Newznab|Unable to connect to indexer
[v2.0.0.4919] System.Net.WebException: Error: ConnectFailure (TLS Support not available.): 'https://api.oznzb.com/api?t=caps&apikey=(removed) at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0017f] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:87
at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0003c] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:35
at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request) [0x0007e] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:122
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00019] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:59
at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00007] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:223
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.FetchCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x00068] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:57
17-8-3 08:35:51.8|Warn|NzbDroneErrorPipeline|Invalid request Validation failed:
– Unable to connect to indexer, check the log for more details
17-8-3 08:35:52.7|Warn|DownloadMonitoringService|Unable to retrieve queue and history items from NZBGet
[v2.0.0.4919] System.ObjectDisposedException: Cannot access a disposed object.
Object name: ‘System.Net.Sockets.NetworkStream’.
at System.Net.WebConnectionStream.EndWrite (IAsyncResult r) <0x41ab35f0 + 0x003ab> in :0
at System.Net.WebConnectionStream.Write (System.Byte[] buffer, Int32 offset, Int32 size) <0x41ab1e90 + 0x000bb> in :0
at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x000d1] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:55
at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x000b5] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:53
at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request) [0x0007e] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:122
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00019] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Http\HttpClient.cs:59
at NzbDrone.Core.Download.Clients.Nzbget.NzbgetProxy.ProcessRequest[T] (NzbDrone.Core.Download.Clients.Nzbget.NzbgetSettings settings, System.String method, System.Object[] parameters) [0x00047] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Download\Clients\Nzbget\NzbgetProxy.cs:232
at NzbDrone.Core.Download.Clients.Nzbget.NzbgetProxy.GetHistory (NzbDrone.Core.Download.Clients.Nzbget.NzbgetSettings settings) [0x00000] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Download\Clients\Nzbget\NzbgetProxy.cs:135
at NzbDrone.Core.Download.Clients.Nzbget.Nzbget.GetHistory () [0x00000] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Download\Clients\Nzbget\Nzbget.cs:112
at NzbDrone.Core.Download.Clients.Nzbget.Nzbget.GetItems () [0x00000] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Download\Clients\Nzbget\Nzbget.cs:184
at NzbDrone.Core.Download.TrackedDownloads.DownloadMonitoringService.ProcessClientDownloads (IDownloadClient downloadClient) [0x0000c] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Core\Download\TrackedDownloads\DownloadMonitoringService.cs:89
@ktdt00
That depends on how mono was compiled. It should be cleared up on the next release, but I’m testing it first on a few select individuals on that branch I mentioned earlier.
sorry for opening another thread without finding this first, but it seems hdbits also is affected.
I am also still unable to connect to any indexers (using Hydra primarily) even after installing version 4928.
I must see the exact errors from the log files if you want me to help you.
Is this the relevant section?
Problems here too, for example NZBGeek:
On Raspberry PI 2, Jessie:
Version
2.0.0.4928
Mono Version
4.3.0
AppData directory
/home/pi/.config/NzbDrone
Startup directory
/opt/NzbDrone
@ejdme Yes.
[v2.0.0.4919] System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. —> System.IO.IOException: The handshake failed due to an unexpected packet format.
First: A couple of years ago I had the bright idea to add the version number to all exceptions, and it’s useful in these cases. The log entry indicates that at that time Sonarr was running version 4919, not 4928. So you’re still running the older version. Perhaps Sonarr must be restarted? Either that or this is an older log message.
Secondly, you might want to enable Trace log level in Settings->General. At those levels you’ll see the exact urls it’s querying.
Thirdly, the error message itself is “The handshake failed due to an unexpected packet format.”, this is usually caused when you try to perform an https call on a http port. The tracelog mentioned earlier would probably provide more insight, but it might be a good idea to check your indexer settings in Sonarr.
New log with trace activated:
https://pastebin.com/nr5u8cEQ