Nzbdrone does not seem to work with nzbgeek's public and VIG indexers

Help & Support
1

I currently have 7 Newznab indexers set up, and for some reason both nzbgeek indexes do not work with nzbdrone. I at first thought the API key may have been wrong, but it works without problems in sickbeard. Below are the logs.

I replaced my APIKey with *'s

13-5-21 18:26:10.8|Core.Providers.Indexer.Newznab|Error|An error occurred while processing feed. https://vig.nzbgeek.info/api?t=tvsearch&cat=5030,5040,5070,5090&apikey=********************************&limit=100&q=Mad%20Men&season=3&ep=4|System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream. at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) 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.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(​TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) 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.HttpProvider.DownloadStream(String url, NetworkCredential credential) in c:\\Source\zbDrone.Common\\HttpProvider.cs:line 58 at NzbDrone.Core.Providers.Indexer.IndexerBase.Fetch(IEnumerable1 urls) in c:\\Source\zbDrone.Core\\Providers\\Indexer\\IndexerBase.cs:line 187

Thanks for any help regarding this issue, and thanks so much for this alternative to sickbeard. So far it’s great and I could never go back to sickbeard, even with these two indexers not working :stuck_out_tongue:

2

Install .net 4.5 as it allows more SSL protocols to be used and solves this issue for nzbgeek.

3

I don’t think it’s the framework version, as far as I can tell it’s caused by a bad cert on their side. which causes the runtime to abort the connection for security reasons.

We could force the runtime to ignore ssl errors, but I’m not sure if that would be a great idea. but defiantly something to think about.

4

Looks like they changed their URL to match the SSL cert, likely there is a post on their VIG forums with the new URL, or you can pull it from the SSL cert.

I’m on the same boat as @kayone about ignoring SSL cert issues, its good and bad.

5

I use nzbgeek and when I first set it up had issues. Installing .net 4.5 fixed it for me back then. I read something on their forums about moving to new servers.