Trailers errors in logs

[kesm 25]

Hi, 

I activate trailers on my Synology DS414 and I got no trailers added after a full scan.

When I check logs I have this errors : 

2018-02-07 09:33:52.382 Info HttpServer: HTTP Response 200 to 188.165.111.26. Time: 52ms. http://mynas:myport/emby/Users/a8195095ead24e69860801819e4ca7f4/Items/efd489614dbf0141d36e9acfbe45d0cf 
2018-02-07 09:33:52.398 Info HttpClient: HttpClientManager GET: https://mediabrowser.github.io/Trailers/listingswithmetadata.txt?v=66
2018-02-07 09:33:52.661 Error HttpClient: Error SecureChannelFailure getting response from https://mediabrowser.github.io/Trailers/listingswithmetadata.txt?v=66
	*** Error Report ***
	Version: 3.2.70.0
	Command line: /var/packages/EmbyServer/target/server/MediaBrowser.Server.Mono.exe -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -restartpath /var/packages/EmbyServer/scripts/restart
	Operating system: Unix 3.2.40.0
	64-Bit OS: False
	64-Bit Process: False
	User Interactive: False
	Mono: 5.2.0.224 (tarball Thu Sep 21 22:27:13 CST 2017)
	Processor count: 2
	Program data path: /var/packages/EmbyServer/target/var
	Application directory: /volume1/@appstore/EmbyServer/releases/v3.2.70.0
	System.Net.WebException: Error: SecureChannelFailure (The authentication or decryption has failed.) ---> System.IO.IOException: The authentication or decryption has failed. ---> 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.EndReceiveRecord (System.IAsyncResult asyncResult) [0x00037] in <7ae599ac10074937b32461b1c1c1c5ab>:0 
	  at Mono.Security.Protocol.Tls.SslClientStream.SafeEndReceiveRecord (System.IAsyncResult ar, System.Boolean ignoreEmpty) [0x00000] in <7ae599ac10074937b32461b1c1c1c5ab>:0 
	  at Mono.Security.Protocol.Tls.SslClientStream.NegotiateAsyncWorker (System.IAsyncResult result) [0x00071] in <7ae599ac10074937b32461b1c1c1c5ab>:0 
	   --- End of inner exception stack trace ---
	  at Mono.Security.Protocol.Tls.SslClientStream.EndNegotiateHandshake (System.IAsyncResult result) [0x00032] in <7ae599ac10074937b32461b1c1c1c5ab>:0 
	  at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (System.IAsyncResult asyncResult) [0x0000c] in <7ae599ac10074937b32461b1c1c1c5ab>:0 
	   --- End of inner exception stack trace ---
	  at Mono.Security.Protocol.Tls.SslStreamBase.EndRead (System.IAsyncResult asyncResult) [0x0004b] in <7ae599ac10074937b32461b1c1c1c5ab>:0 
	  at Mono.Net.Security.Private.LegacySslStream.EndAuthenticateAsClient (System.IAsyncResult asyncResult) [0x0000e] in <7bc83f72cfb44c1eac96d11ef998e9a2>:0 
	  at Mono.Net.Security.Private.LegacySslStream.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x0000e] in <7bc83f72cfb44c1eac96d11ef998e9a2>:0 
	  at Mono.Net.Security.MonoTlsStream.CreateStream (System.Byte[] buffer) [0x0007b] in <7bc83f72cfb44c1eac96d11ef998e9a2>:0 
	  at System.Net.WebConnection.CreateStream (System.Net.HttpWebRequest request) [0x00073] in <7bc83f72cfb44c1eac96d11ef998e9a2>:0 
	   --- End of inner exception stack trace ---
	  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00058] in <7bc83f72cfb44c1eac96d11ef998e9a2>:0 
	  at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <d31cad56a57f4677b3b2262d472abcad>:0 
	System.Net.WebException
	  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00058] in <7bc83f72cfb44c1eac96d11ef998e9a2>:0 
	  at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <d31cad56a57f4677b3b2262d472abcad>:0 

trailers.log

[Luke 39620]

hi @@kesm, that's strange. is this still happening today?

[kesm 25]

I do a complete reinstall and I still got a problem, here is a new full log

trailers.log

Edited February 12, 2018 by kesm

[Luke 39620]

@@kesm looks like this will be getting resolved soon based on the discussions in other topics. thanks.

[solabc16 379]

Hello @@kesm

 

Have you installed the beta I've made available via PM, in response to our conversation here: https://emby.media/community/index.php?/topic/56391-error-securechannelfailure-when-checking-for-application-updates/

 

This is the same issue, @@DarWun has reported back with a positive result for the same platform you are running on.

 

Best

- James

[DarWun 306]

@@Luke @@solabc16, @@kesm 's post that started out this particular thread is from February.  I checked the attached log, and the problem is being reported using v3.2.70.0 of Emby. So I think it predates the recent work that was done to resolve the SecureChannelFailure issues with Emby Synology.  I do not have Emby set up to play or retrieve trailers so I'm not sure if that particular problem is resolved with the recent fix for the platform.  It seems likely that it would be given the information in the log.  Hopefully @@kesm will post back to confirm that it has been fixed.

Edited March 26, 2018 by DarWun

[Luke 39620]

It's not something that started with a server version, it started due to GitHub api changes.

[DarWun 306]

It's not something that started with a server version, it started due to GitHub api changes.

@@Luke I realize that.  But the error didn't start showing up until after a specific Emby server update.  So whether or not the change was related to the server update or a GitHub api change is not obvious to those of us that aren't on the development team.  All we know is that after update number xxx Emby started acting differently than it had previously.  Maybe I'm just speaking for myself, and others do understand this.  Anyway, I've tested the trailer download functionality after the recent updates pushed out by @@solabc16 for the Synology platform, and I'm not seeing the errors reported by @@kesm.  Hopefully he will confirm the same.

Edited March 27, 2018 by DarWun

[Luke 39620]

https://blog.github.com/2018-02-23-weak-cryptographic-standards-removed/

[DarWun 306]

https://blog.github.com/2018-02-23-weak-cryptographic-standards-removed/

Thanks @@Luke. I think we're getting side tracked here.  The reason I responded to this post was to identify that I had not tested the trailer features that were reported at the top of this thread after installing the Synology update pushed out recently by @@solabc16.  Whether or not the issue was related to Emby or a GitHub api change was not relevant to making that point.  I've since confirmed that after enabling trailer features, I'm not seeing the issue with the latest update on the platform.  Hopefully others confirm the same, and all is good moving forward.

 

Having said the above, the information in the link you provided told me nothing that would have changed my understanding of the issue.  Rightly or wrongly as an end user of Emby I don't care that it was a GitHub change that resulted in the issue.  All I care about is that there is an issue.  There was no finger pointing intended here.  The issue was acknowledged and resolved with clear communication from the Emby team in the PMs between @@solabc16, @@kesm and myself as well as posts from you...that is all I care about. 

Edited March 27, 2018 by DarWun

[Luke 39620]

Thanks for the feedback.

[DarWun 306]

Thanks for the feedback.

@@Luke And just so it is clear...that was intended as positive feedback.  Hopefully it came across that way (but I realize after re-reading it that it might not have).

[kesm 25]

Trailers seems to work fine now, thanks!

[Luke 39620]

Thanks for the feedback.