Jump to content

Playback error when connecting via SSL


Recommended Posts

Posted

Hi there,

 

I can not play any video media through the emby web interface when accessing the server via HTTPS port 8920. Browsing and selecting works fine, but playback does not work. This also affects Live-TV. 

 

Here is my error log for a movie playback error.

 

I use a Ubuntu 16.04 64-Bit server and Safari on a Mac as a client. I remember there was a Mono update a few days ago which might be the cause for my errors. Everything was fine before that.

2016-09-12 14:34:29.1015 Info HttpServer: HTTP GET https://server:8920/emby/Playback/BitrateTest?Size=1000000. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.8 (KHTML, like Gecko) Version/9.1.3 Safari/601.7.8
2016-09-12 14:34:29.2437 Error HttpServer: Error in ProcessAccept
	*** Error Report ***
	Version: 3.0.7100.0
	Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh
	Operating system: Unix 4.4.0.36
	Processor count: 8
	64-Bit OS: True
	64-Bit Process: True
	Program data path: /var/lib/emby-server
	Mono: 4.4.2 (Stable 4.4.2.11/f72fe45 Tue Aug 30 15:49:18 UTC 2016)
	Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe
	The authentication or decryption has failed.
	System.IO.IOException
	  at Mono.Security.Protocol.Tls.SslStreamBase.EndRead (IAsyncResult asyncResult) <0x41f5b350 + 0x00157> in <filename unknown>:0 
	  at Mono.Net.Security.Private.LegacySslStream.EndAuthenticateAsServer (IAsyncResult asyncResult) <0x41f5b2b0 + 0x0003e> in <filename unknown>:0 
	  at Mono.Net.Security.Private.LegacySslStream.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate, Boolean clientCertificateRequired, SslProtocols enabledSslProtocols, Boolean checkCertificateRevocation) <0x41f4f670 + 0x00055> in <filename unknown>:0 
	  at Mono.Net.Security.Private.LegacySslStream.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate) <0x41f4f640 + 0x00022> in <filename unknown>:0 
	  at Mono.Net.Security.Private.MonoSslStreamImpl.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate) <0x41f4f4a0 + 0x0002b> in <filename unknown>:0 
	  at System.Net.Security.SslStream.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate) <0x41f4f3b0 + 0x00027> in <filename unknown>:0 
	  at SocketHttpListener.Net.HttpConnection..ctor (ILogger logger, System.Net.Sockets.Socket sock, SocketHttpListener.Net.EndPointListener epl, Boolean secure, System.Security.Cryptography.X509Certificates.X509Certificate cert, System.String connectionId) <0x41ea31d0 + 0x0025f> in <filename unknown>:0 
	  at SocketHttpListener.Net.EndPointListener.ProcessAccept (System.Net.Sockets.Socket accepted) <0x41ea2b90 + 0x0011f> in <filename unknown>:0 
	InnerException: Mono.Security.Protocol.Tls.TlsException
	The client stopped the handshake.
	  at Mono.Security.Protocol.Tls.SslServerStream.EndNegotiateHandshake (IAsyncResult asyncResult) <0x41f5ec90 + 0x0022b> in <filename unknown>:0 
	  at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (IAsyncResult asyncResult) <0x41f5ea20 + 0x0008d> in <filename unknown>:0 
	
2016-09-12 14:34:32.0441 Info HttpServer: HTTP GET https://server:8920/emby/ScheduledTasks?IsEnabled=true. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.8 (KHTML, like Gecko) Version/9.1.3 Safari/601.7.8
2016-09-12 14:34:32.0517 Info HttpServer: HTTP Response 200 to 10.100.100.1. Time: 8ms. https://server:8920/emby/ScheduledTasks?IsEnabled=true
2016-09-12 14:34:34.1319 Info HttpServer: HTTP POST https://server:8920/emby/Items/129f252199c36148d750ac7d2fcedd36/PlaybackInfo?UserId=f5b230bc3c0547ceba89428b83e990bc&StartTimeTicks=7780014125. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.8 (KHTML, like Gecko) Version/9.1.3 Safari/601.7.8

---<cut off due to information leakage>---

2016-09-12 14:34:34.1461 Info HttpServer: HTTP Response 200 to 10.100.100.1. Time: 14ms. https://server:8920/emby/Items/129f252199c36148d750ac7d2fcedd36/PlaybackInfo?UserId=f5b230bc3c0547ceba89428b83e990bc&StartTimeTicks=7780014125
2016-09-12 14:34:34.2068 Info HttpServer: HTTP GET https://server:8920/emby/Items/129f252199c36148d750ac7d2fcedd36/Images/Primary?width=800&tag=e5c37d60a7ef1e983edd02b3bd0f3aae&quality=90. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.8 (KHTML, like Gecko) Version/9.1.3 Safari/601.7.8
2016-09-12 14:34:34.2080 Info HttpServer: HTTP GET https://server:8920/emby/Items/129f252199c36148d750ac7d2fcedd36/Images/Logo?height=84&tag=bb26ff89d7bbdd5da826070b17da5a67&quality=90. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/601.7.8 (KHTML, like Gecko) Version/9.1.3 Safari/601.7.8
2016-09-12 14:34:34.3248 Info HttpServer: HTTP Response 200 to 10.100.100.1. Time: 117ms. https://server:8920/emby/Items/129f252199c36148d750ac7d2fcedd36/Images/Logo?height=84&tag=bb26ff89d7bbdd5da826070b17da5a67&quality=90
2016-09-12 14:34:34.4611 Error HttpServer: Error in ProcessAccept
	*** Error Report ***
	Version: 3.0.7100.0
	Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh
	Operating system: Unix 4.4.0.36
	Processor count: 8
	64-Bit OS: True
	64-Bit Process: True
	Program data path: /var/lib/emby-server
	Mono: 4.4.2 (Stable 4.4.2.11/f72fe45 Tue Aug 30 15:49:18 UTC 2016)
	Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe
	The authentication or decryption has failed.
	System.IO.IOException
	  at Mono.Security.Protocol.Tls.SslStreamBase.EndRead (IAsyncResult asyncResult) <0x41f5b350 + 0x00157> in <filename unknown>:0 
	  at Mono.Net.Security.Private.LegacySslStream.EndAuthenticateAsServer (IAsyncResult asyncResult) <0x41f5b2b0 + 0x0003e> in <filename unknown>:0 
	  at Mono.Net.Security.Private.LegacySslStream.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate, Boolean clientCertificateRequired, SslProtocols enabledSslProtocols, Boolean checkCertificateRevocation) <0x41f4f670 + 0x00055> in <filename unknown>:0 
	  at Mono.Net.Security.Private.LegacySslStream.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate) <0x41f4f640 + 0x00022> in <filename unknown>:0 
	  at Mono.Net.Security.Private.MonoSslStreamImpl.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate) <0x41f4f4a0 + 0x0002b> in <filename unknown>:0 
	  at System.Net.Security.SslStream.AuthenticateAsServer (System.Security.Cryptography.X509Certificates.X509Certificate serverCertificate) <0x41f4f3b0 + 0x00027> in <filename unknown>:0 
	  at SocketHttpListener.Net.HttpConnection..ctor (ILogger logger, System.Net.Sockets.Socket sock, SocketHttpListener.Net.EndPointListener epl, Boolean secure, System.Security.Cryptography.X509Certificates.X509Certificate cert, System.String connectionId) <0x41ea31d0 + 0x0025f> in <filename unknown>:0 
	  at SocketHttpListener.Net.EndPointListener.ProcessAccept (System.Net.Sockets.Socket accepted) <0x41ea2b90 + 0x0011f> in <filename unknown>:0 
	InnerException: Mono.Security.Protocol.Tls.TlsException
	The client stopped the handshake.
	  at Mono.Security.Protocol.Tls.SslServerStream.EndNegotiateHandshake (IAsyncResult asyncResult) <0x41f5ec90 + 0x0022b> in <filename unknown>:0 
	  at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (IAsyncResult asyncResult) <0x41f5ea20 + 0x0008d> in <filename unknown>:0 
	

Posted

Hi, are you sure this worked on a previous mono version?

Posted

Not a 100% sure, since I usually use my AppleTV to play my media. I definitely watched LiveTV in my browser a few times, but I am only about 90% sure I used HTTPS for that.

 

HTTP still works fine!

 

Regards

Posted

Ok, thanks for the clarification. Sad they do not support it already, but as HTTP still works, it's not that much of an issue.

 

Thanks! :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...