Cannot connect to any Indexers

I am having an issue connecting to all of my indexers. I have four right now, and as of 3ish or so weeks ago, none of them connect. I can hit the API outside of Sonarr and it works as expected. But, for some reason, when Sonarr goes to connect, it fails. I haven’t touched the system outside of adding and removing a series. For example, I can hit https://api.dognzb.cr/api?t=caps&apikey=[api key] without issue from a browser (yep, replaced [api key] with my actual api key) and I see the XML

Sonarr version: 2.0.0.5344
OS: Microsoft Windows Server 2012 R2 Standard

Debug Log:

20-9-7 16:55:24.3|Debug|NewznabCapabilitiesProvider|Failed to get newznab api capabilities from http://api.dognzb.cr/

Debug log file: https://www.dropbox.com/s/m58wh7vqoj51z7a/debug.txt?dl=0

Snippet of the issue.

[v2.0.0.5344] System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. —> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
— End of inner exception stack trace —
at System.Net.HttpWebRequest.GetResponse()
at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse(HttpRequest request, CookieContainer cookies) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:line 117
at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse(HttpRequest request, CookieContainer cookies) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:line 53
at NzbDrone.Common.Http.HttpClient.ExecuteRequest(HttpRequest request, CookieContainer cookieContainer) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:line 121
at NzbDrone.Common.Http.HttpClient.Execute(HttpRequest request) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:line 76
at NzbDrone.Common.Http.HttpClient.Get(HttpRequest request) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:line 264
at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.FetchCapabilities(NewznabSettings indexerSettings) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:line 57

I’ve found that restarting Sonarr will solve the issue temporarily, but I typically have to do this workaround at least every day unfortunately.

Yes. I setup a job to do restart sonarr. And it seemed to help for a couple days. Then stopped working. Then I setup a job to just restart the whole server. That also seemed to work for a couple days. Now, neither work and it just won’t connect to any indexers. So weird.

1 Like

From which browser? IE11 will be the closest to Sonarr’s behaviour.

The only other thing would be the lack of .net 4.5 leading to SSL issues, but I think that issue was different.

Just adding another voice of someone who’s having to do this. After a restart (and then “testing” the indexers) it works for a few days and then craps out again with the log message “The request was aborted: Could not create SSL/TLS secure channel.”

I ended up redeploying the entire thing (from OS to all apps). I backed every up. Reinstalled. Restored the backup. Now things are fine. So far.