Since 4.1.1.0 SSL not working

[byusinger84 1]

To be fair this may not be an issue with 4.1.1.0 but I know this is happening for two separate servers since this update. My certificates according to LetsEncrypt and IIS are showing that the certificates are indeed valid, but the Emby server is using an older expired certificate and not the renewed one. I have re-exported my pfx file from IIS to no avail. Rebooting the system does not help. According to the LetsEncrypt logs and the IIS certificates, all are valid with dates thru July. The certificates renewed a few days before the issue but was also right around the same time as 4.1.1.0 was installed so I can't be sure. Anyone have any thoughts?

 

Looking at the Emby logs I see a bunch of these errors over and over:

 

2019-05-05 08:47:26.805 Error HttpServer: Error in ProcessAccept

*** Error Report ***

Version: 4.1.1.0

Command line: C:\Users\Administrator\AppData\Roaming\Emby-Server\system\EmbyServer.dll

Operating system: Microsoft Windows NT 6.2.9200.0

64-Bit OS: True

64-Bit Process: True

User Interactive: True

Runtime: file:///C:/Users/Administrator/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll

Processor count: 12

Program data path: C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata

Application directory: C:\Users\Administrator\AppData\Roaming\Emby-Server\system

System.Security.Authentication.AuthenticationException: System.Security.Authentication.AuthenticationException: Authentication failed, see inner exception. ---> System.ComponentModel.Win32Exception: An unknown error occurred while processing the certificate

   --- End of inner exception stack trace ---

   at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, ExceptionDispatchInfo exception)

   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.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)

   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)

   at System.Net.Security.SslState.PartialFrameCallback(AsyncProtocolRequest asyncRequest)

--- End of stack trace from previous location where exception was thrown ---

   at System.Net.Security.SslState.ThrowIfExceptional()

   at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)

   at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)

   at System.Net.Security.SslStream.EndAuthenticateAsServer(IAsyncResult asyncResult)

   at System.Net.Security.SslStream.<>c.<AuthenticateAsServerAsync>b__50_2(IAsyncResult iar)

   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

--- End of stack trace from previous location where exception was thrown ---

   at SocketHttpListener.Net.HttpConnection.Init()

   at SocketHttpListener.Net.HttpEndPointListener.ProcessAccept(SocketAsyncEventArgs args)

Source: System.Private.CoreLib

TargetSite: Void Throw()

InnerException: System.ComponentModel.Win32Exception: An unknown error occurred while processing the certificate

Source: 

TargetSite: 

 

It looks like an authentication error with the certificate but I know the password is correct. I've even re-exported it and retyped the password several times. 

Edited May 5, 2019 by byusinger84

[Luke 42085]

Hi, I would try removing the certificate from Emby and then adding it back. Make sure to restart the server afterwards. Please let us know if this helps. Thanks.

[byusinger84 1]

That did the trick. Removing it. Restarting Emby. Re-adding it. Restarting Emby again. That resolved the issue. Thanks!

[Luke 42085]

Thanks for the feedback.