Emby stops responding to https every couple days

[Luke 37049]

It's being looked into, thanks. If you haven't attached an emby server log from an example, please make sure to do that. thanks.

[Jdiesel 1113]

Down again, PMed another log file. Once again the server became unresponsive following a LiveTV guide update. Only have the Trailers and Auto Box Set plugins installed at the moment.

[Jdiesel 1113]

This last time it only lasted for about 2 hours. Looks like the Auto Box Set plugin had just finished running. PMed some new logs.

 

I first reported it happening when on 3.2.70.17 but noticed it a few beta versions before that. I don't want to have to downgrade to 3.2.70.0 but at this point my server is almost unable for anyone but myself as it seems everytime I go to watch sometime I need to reboot it.

[vk_digi 1]

Hello,

 

Emby was running all the time very stable here. Since 2-3 days i have same problem. Emby is running but no connect via https anymore. After a restart it is working again but not very long and restart is needed again.

Because of this new problem i think it depends maybe on a client app update which works not find with the current emby-server version.

So this moring there was only one client "online". This client is a empy-app 2.9.87 (not sure where to find this info in log or reports). this client views via a mediatab (android) and when falling asleep ;-) this client goes idle. in server page i can see that the client watches a episode. the is a direct play mode but the time shown stays at same second. this is normal since many month this client is doing it same way and server never crashed or any other problem with that.

 

so this morning the server needs a restart every few minutes (mayme even seconds). nothing was running on server. no scans no other clients. only this client. 

i decided to block the ip of this client with iptables for in and out and restarted server again. server is now up more than one hour with out crashing or not answer anymore on https port.

 

i set debug logging on and found all the time an error in the log and after this one server stops to work correct.

 

here is the part of the logfile:

 

2018-03-10 07:26:13.111 Error HttpServer: Error in ProcessAccept

*** Error Report ***

Version: 3.3.1.0

Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -restartpath /usr/lib/emby-server/restart.sh

Operating system: Unix 4.13.0.36

64-Bit OS: True

64-Bit Process: True

User Interactive: False

Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Wed May  3 05:22:31 UTC 2017)

Processor count: 8

Program data path: /var/lib/emby-server

Application directory: /usr/lib/emby-server/bin

System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer. ---> System.Net.Sockets.SocketException: Connection reset by peer

  at System.Net.Sockets.Socket.Receive (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags) [0x00052] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, System.Int32 offset, System.Int32 size) [0x000b4] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

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

  at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, System.Int32 offset, System.Int32 size) [0x0010f] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at Mono.Net.Security.MobileAuthenticatedStream.InnerRead (System.Int32 requestedSize) [0x0003a] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream:InnerRead (int)

  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (Mono.Net.Security.AsyncOperationStatus status) [0x00026] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation () [0x0000d] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at Mono.Net.Security.AsyncProtocolRequest.StartOperation () [0x00000] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

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

  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 

  at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Net.LazyAsyncResult lazyResult) [0x00083] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at Mono.Net.Security.MobileAuthenticatedStream.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate, System.Boolean clientCertificateRequired, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00010] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at System.Net.Security.SslStream.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate, System.Boolean clientCertificateRequired, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00006] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at SocketHttpListener.Net.HttpConnection..ctor (MediaBrowser.Model.Logging.ILogger logger, System.Net.Sockets.Socket socket, SocketHttpListener.Net.EndPointListener epl, System.Boolean secure, System.Security.Cryptography.X509Certificates.X509Certificate cert, MediaBrowser.Model.Cryptography.ICryptoProvider cryptoProvider, MediaBrowser.Model.IO.IMemoryStreamFactory memoryStreamFactory, MediaBrowser.Model.Text.ITextEncoding textEncoding, MediaBrowser.Model.IO.IFileSystem fileSystem, MediaBrowser.Model.System.IEnvironmentInfo environment) [0x000cb] in <02aac24fae75429fabca4678403ca254>:0 

  at SocketHttpListener.Net.EndPointListener.ProcessAccept (System.Net.Sockets.Socket accepted) [0x00023] in <02aac24fae75429fabca4678403ca254>:0 

System.IO.IOException

  at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, System.Int32 offset, System.Int32 size) [0x0010f] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at Mono.Net.Security.MobileAuthenticatedStream.InnerRead (System.Int32 requestedSize) [0x0003a] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at (wrapper remoting-invoke-with-check) Mono.Net.Security.MobileAuthenticatedStream:InnerRead (int)

  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (Mono.Net.Security.AsyncOperationStatus status) [0x00026] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation () [0x0000d] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at Mono.Net.Security.AsyncProtocolRequest.StartOperation () [0x00000] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

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

  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 

  at Mono.Net.Security.MobileAuthenticatedStream.ProcessAuthentication (System.Net.LazyAsyncResult lazyResult) [0x00083] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at Mono.Net.Security.MobileAuthenticatedStream.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate, System.Boolean clientCertificateRequired, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00010] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at System.Net.Security.SslStream.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate, System.Boolean clientCertificateRequired, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00006] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at SocketHttpListener.Net.HttpConnection..ctor (MediaBrowser.Model.Logging.ILogger logger, System.Net.Sockets.Socket socket, SocketHttpListener.Net.EndPointListener epl, System.Boolean secure, System.Security.Cryptography.X509Certificates.X509Certificate cert, MediaBrowser.Model.Cryptography.ICryptoProvider cryptoProvider, MediaBrowser.Model.IO.IMemoryStreamFactory memoryStreamFactory, MediaBrowser.Model.Text.ITextEncoding textEncoding, MediaBrowser.Model.IO.IFileSystem fileSystem, MediaBrowser.Model.System.IEnvironmentInfo environment) [0x000cb] in <02aac24fae75429fabca4678403ca254>:0 

  at SocketHttpListener.Net.EndPointListener.ProcessAccept (System.Net.Sockets.Socket accepted) [0x00023] in <02aac24fae75429fabca4678403ca254>:0 

InnerException: System.Net.Sockets.SocketException

System.Net.Sockets.SocketException (0x80004005): Connection reset by peer

  at System.Net.Sockets.Socket.Receive (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags) [0x00052] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, System.Int32 offset, System.Int32 size) [0x000b4] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at System.Net.Sockets.Socket.Receive (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags) [0x00052] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

  at System.Net.Sockets.NetworkStream.Read (System.Byte[] buffer, System.Int32 offset, System.Int32 size) [0x000b4] in <5641e4edad4f4464ba58c620a7b8ea48>:0 

[mobamoba 12]

I don't know if this helps point toward a solution, but when the problem occurs and I try to access my server over HTTPS using Chrome on Android (not the Emby app - Chrome itself), I get the following error:

 

"No Certificates Found. The app Chrome has requested a certificate. Choosing a certificate will let the app use this identity with servers now and in the future. The app has identified the requesting server as (xxx.com), but you should only give the app access to the certificate if you trust the app. You can install certificates from a PKCS#12 file with a .pfx or a .p12 extension located in external storage."

 

After the server restart, as with everyone else, this problem vanishes. So it's looking like Emby Server somehow "loses" the HTTPS cert and this hangs up all connecting apps.

Edited March 10, 2018 by mobamoba

[Jdiesel 1113]

Is anyone using a reverse proxy experiencing this? Or just those using a SSL certificate directly in Emby?

[vk_digi 1]

Hello,

 

a real ugly bug or problem. i wrote a little script here checking for this: server running but not able to connect via https. last night same situation with this one client and server needed around 10 restarts until i blocked the client again within the script

 

bye volker

Edited March 11, 2018 by vk_digi

[Guest]

Hey guys, i think i resolved it by replacing the SSL cert with a new one, mine was expired.

Since i replaced the SSL cert, it works again. But im not sure if its really that whats causing this issues!

[Jdiesel 1113]

Hey guys, i think i resolved it by replacing the SSL cert with a new one, mine was expired.

Since i replaced the SSL cert, it works again. But im not sure if its really that whats causing this issues!

 

Everything still working for you? My cert doesn't expire until 2022 so I don't think that is my issue.

[Jdiesel 1113]

Any updates on this? Do you need any more log files or testing on our end?

[Luke 37049]

We're looking into it, thanks.

[Jdiesel 1113]

Any changes is 3.3.1.5 that address this? I downgraded to 3.2.70.6 and haven't seen the issue in 48 hours so I will still with it until further notice.

[Luke 37049]

If you could try it that would be helpful. Thanks.

[extensive 20]

happened again

 

https://www.dropbox.com/s/1fkm8n7zgkqesgv/server-63656668800.txt?dl=0

 

i am using last production release/non beta

 

has there been any movement with this?  should we expect a fix in the next release?

[extensive 20]

ignore this

Edited March 15, 2018 by extensive

[Jdiesel 1113]

I have been testing 3.3.1.5 but I am reluctant to say if it has been solved since I have only been up for just over 24 hours. I will give it a few more days of uptime before I start adding back my plugins.

[Jdiesel 1113]

I'm still having issues on 3.3.1.5 where they server won't respond to requests and there is not record of activity in the log file. On the plus side it eventually comes back on its own and doesn't require a restart. Back to 3.2.70 for me.

[extensive 20]

just happened again for me.  this is really frustrating.

[jhoff80 87]

Weirdly enough, mine went from doing this 3 times a day last weekend to doing it about once a day during the week.  To my knowledge, nothing has changed usage wise during the week, so it's just really odd.

[Guest]

Everything still working for you? My cert doesn't expire until 2022 so I don't think that is my issue.

yes since i replaced the cert, everything is working again

[extensive 20]

yes since i replaced the cert, everything is working again

yeah i replaced mine the other day and it is still happening to me.

[Jdiesel 1113]

I didn't even think it would come to this but I have started testing Plex on my server again. I am running 3.2.70 for now to see if it is work moving back to Plex which I'd rather avoid. The amount of grief this Emby issue is causing me has gotten to the tipping point though. I need something that needs isn't going to go down every few hours and need constant babysitting.

[socketman 1]

So this just started happening to me since i updated my emby server 2 days ago. The only way to get it working is to log on to my server and reinstall emby , not even a reboot of the machine will get it to start working. If anyone has some suggestions i am all ears.

[extensive 20]

I didn't even think it would come to this but I have started testing Plex on my server again. I am running 3.2.70 for now to see if it is work moving back to Plex which I'd rather avoid. The amount of grief this Emby issue is causing me has gotten to the tipping point though. I need something that needs isn't going to go down every few hours and need constant babysitting.

honestly the sheer lack of dev input on this thread is extremely disappointing.

[socketman 1]

Well i really love emby so i will hold out for a resolution to this issue for now , i am in no mood to change what i have working right now. Perhaps M$ is responsible with some stupid update they force on you, win7 is what i use and it just did some updates on the same day. I have confidence the dev team will tell us something when they know something themselves.