HTTPS connection causes fatal error

Help & Support
1

Sonarr Version
2.0.0.4689
Mono Version
4.6.2
Synology NAS

Enabled SSL
Converted key to PVK
setup HTTPCFG as requested

Everything works fine on HTTP, no issues, runs for hours.
The moment any connection is made to HTTPS, fatal error

Log:

17-4-28 12:35:35.8|Info|Bootstrap|Starting Sonarr - /volume1/@appstore/nzbdrone/share/NzbDrone/NzbDrone.exe - Version 2.0.0.4689
17-4-28 12:35:38.8|Info|MigrationLogger|*** Migrating data source=/var/services/homes/nzbdrone/.config/NzbDrone/nzbdrone.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
17-4-28 12:35:39.6|Info|MigrationLogger|*** Migrating data source=/var/services/homes/nzbdrone/.config/NzbDrone/logs.db;cache size=-10485760;datetimekind=Utc;journal mode=Wal;pooling=True;version=3 ***
17-4-28 12:35:39.8|Info|Router|Application mode: Interactive
17-4-28 12:35:39.8|Info|OwinHostController|Listening on the following URLs:
17-4-28 12:35:39.8|Info|OwinHostController|  http://*:8989/
17-4-28 12:35:39.8|Info|OwinHostController|  https://*:8083/
17-4-28 12:35:40.3|Info|NancyBootstrapper|Starting Web Server
17-4-28 12:37:25.1|Fatal|GlobalExceptionHandlers|EPIC FAIL.

[v2.0.0.4689] System.IO.IOException: The authentication or decryption has failed. ---> Mono.Security.Protocol.Tls.TlsException: The client stopped the handshake.
  at Mono.Security.Protocol.Tls.SslServerStream.EndNegotiateHandshake (System.IAsyncResult asyncResult) [0x00100] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/SslServerStream.cs:272 
  at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (System.IAsyncResult asyncResult) [0x0000c] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/SslStreamBase.cs:101 
   --- End of inner exception stack trace ---
  at Mono.Security.Protocol.Tls.SslStreamBase.EndRead (System.IAsyncResult asyncResult) [0x00058] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/Mono.Security/Mono.Security.Protocol.Tls/SslStreamBase.cs:886 
  at Mono.Net.Security.Private.LegacySslStream.EndAuthenticateAsServer (System.IAsyncResult asyncResult) [0x00011] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/Mono.Net.Security/LegacySslStream.cs:485 
  at Mono.Net.Security.Private.LegacySslStream.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate, System.Boolean clientCertificateRequired, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00000] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/Mono.Net.Security/LegacySslStream.cs:456 
  at System.Net.HttpConnection.Init () [0x0000b] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/System.Net/HttpConnection.cs:114 
  at System.Net.HttpConnection..ctor (System.Net.Sockets.Socket sock, System.Net.EndPointListener epl, System.Boolean secure, System.Security.Cryptography.X509Certificates.X509Certificate cert) [0x00096] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/System.Net/HttpConnection.cs:100 
  at System.Net.EndPointListener.ProcessAccept (System.Net.Sockets.SocketAsyncEventArgs args) [0x00052] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/System.Net/EndPointListener.cs:124 
  at System.Net.EndPointListener.OnAccept (System.Object sender, System.Net.Sockets.SocketAsyncEventArgs e) [0x00000] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/System.Net/EndPointListener.cs:133 
  at System.Net.Sockets.SocketAsyncEventArgs.OnCompleted (System.Net.Sockets.SocketAsyncEventArgs e) [0x00014] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/System.Net.Sockets/SocketAsyncEventArgs.cs:212 
  at System.Net.Sockets.SocketAsyncEventArgs.Complete () [0x00000] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/System.Net.Sockets/SocketAsyncEventArgs.cs:202 
  at System.Net.Sockets.Socket.<AcceptAsyncCallback>m__0 (System.IAsyncResult ares) [0x000a0] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/System.Net.Sockets/Socket.cs:974 
  at System.Net.Sockets.SocketAsyncResult+<Complete>c__AnonStorey0.<>m__0 (System.Object _) [0x00000] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/System/System.Net.Sockets/SocketAsyncResult.cs:150 
  at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00019] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/referencesource/mscorlib/system/threading/threadpool.cs:1277 
  at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/referencesource/mscorlib/system/threading/threadpool.cs:854 
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in /spksrc/native/mono/work-native/mono-4.6.2/mcs/class/referencesource/mscorlib/system/threading/threadpool.cs:1209
2

((Trace logs)) may provide more details on the request.

System.IO.IOException: The authentication or decryption has failed. ---> Mono.Security.Protocol.Tls.TlsException: The client stopped the handshake.

I’m not sure why that would be a fatal error, but that’s failing inside mono and may be due to mono’s limited support for TLS until 4.8 and most browsers rejecting the TLS it does support as it is insecure.

Using a reverse proxy (Synology has built-in support for that) is the recommended way to enable secure connections to Sonarr at this time.

3

Alright, I’ll probably just go no TLS for now then.
Once mono gets updated with full TLS support, i’ll give it another go.

Did you still want a trace log of the event?
I’d have to crash it again.

4

No, at this point I don’t see any reason to crash it again just for the logs.

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.