Do I have a corrupt mono package? Is my error different from the documented mono issues?

Help & Support
1

Yesterday, an indexer that I’ve been using without issue for months threw a warning. I am no longer able to connect to that indexer. For reference, I’m running Sonarr on a Mac (should be apparent from the log)

Is this issue different from the other mono issues that have been documented?

Thanks in advance!

Here’s the warning from the log:

Message:
Unable to connect to indexer: Error: SendFailure (Error writing headers): Error: SendFailure (Error writing headers)

Exception:
System.Net.WebException: Error: SendFailure (Error writing headers) —> System.Net.WebException: Error writing headers —> System.IO.IOException: The authentication or decryption has failed. —> Mono.Security.Protocol.Tls.TlsException: The authentication or decryption has failed.
at Mono.Security.Protocol.Tls.RecordProtocol.ProcessAlert (AlertLevel alertLevel, AlertDescription alertDesc) [0x00013] in /private/tmp/source-mono-mac-3.12.99-branch-32/bockbuild-mono-3.12.0-branch/profiles/mono-mac-xamarin/build-root/mono-3.12.1/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/RecordProtocol.cs:574
at Mono.Security.Protocol.Tls.RecordProtocol.InternalReceiveRecordCallback (IAsyncResult asyncResult) [0x000d0] in /private/tmp/source-mono-mac-3.12.99-branch-32/bockbuild-mono-3.12.0-branch/profiles/mono-mac-xamarin/build-root/mono-3.12.1/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/RecordProtocol.cs:376
— End of inner exception stack trace —
at Mono.Security.Protocol.Tls.SslClientStream.EndNegotiateHandshake (IAsyncResult result) [0x00035] in /private/tmp/source-mono-mac-3.12.99-branch-32/bockbuild-mono-3.12.0-branch/profiles/mono-mac-xamarin/build-root/mono-3.12.1/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/SslClientStream.cs:425
at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (IAsyncResult asyncResult) [0x0000c] in /private/tmp/source-mono-mac-3.12.99-branch-32/bockbuild-mono-3.12.0-branch/profiles/mono-mac-xamarin/build-root/mono-3.12.1/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/SslStreamBase.cs:99
— End of inner exception stack trace —
— End of inner exception stack trace —
at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00065] in /private/tmp/source-mono-mac-3.12.99-branch-32/bockbuild-mono-3.12.0-branch/profiles/mono-mac-xamarin/build-root/mono-3.12.1/mcs/class/System/System.Net/HttpWebRequest.cs:971
at System.Net.HttpWebRequest.GetResponse () [0x0000e] in /private/tmp/source-mono-mac-3.12.99-branch-32/bockbuild-mono-3.12.0-branch/profiles/mono-mac-xamarin/build-root/mono-3.12.1/mcs/class/System/System.Net/HttpWebRequest.cs:985
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x001e1] in m:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Common\Http\HttpClient.cs:105

2

Your indexer is using an SSL protocol that mono does not support.

I’d say based on past experience with this issue that your indexer is using Cloud Flare for SSL which doesn’t work with Sonarr if the free version is used.

1 Like
3

Thanks for the quick response Marcus. So would it be reasonable to say that it’s possible my indexer moved to a new SSL system without my knowledge? I personally made no changes to my indexer or settings in Sonarr

Thanks again.

4

Its definitely on your indexer’s side. Which indexer is it?

5

Chicas NZB - Standard Newsnab from what I can tell (at least it has been since NZB Matrix bit the dust a few years back)

6

Looking at: https://www.ssllabs.com/ssltest/analyze.html?d=nzbs.chica.be They seem to support IE 8 on Windows XP which is the requirement.

Which OS and mono version?

7

OS: OSX Yosemite 10.10.3
Mono: 3.12.1.macos10.xamarin.x86

8

Give mono 4.0.1 a shot, but its probably worth asking the indexer if anything changed regarding SSL.

9

thanks - I already posted in their forum just to cover my bases.

10

just to close the loop. I uninstalled mono 3.12.1 and installed 14.0.0 (that was the most recent posting for mac). Indexer still doesn’t want to load, so I’m fully blaming them :smile:

11

Yep, indexer admin let me know that he made a change to the indexer’s ssl_ciphers. He reverted back to old values and all is well.

Thanks for the support Marcus.