Jump to content

Emby not scraping images


lesensei
 Share

Go to solution Solved by solabc16,

Recommended Posts

lesensei

Hello,

 

I just discovered Emby while looking for a better way to manage my movie collection both on the NAS and on kodi. It looks like it's working great and the initial movies scrape did retrieve every bit of info I could have expected, except images :-(

 

When I try to choose the image manually, I can get to the screen that lists them all, but every item on that screen shows me the metadata (image origin, size, votes, ...) without displaying any image whatsoever.

If I click on one of the items, I get the following error: "Error: SecureChannelFailure (SIGILL)".

 

One such instance is with the following URL: https://mynasip:8920/emby/Images/Remote?imageUrl=https%3A%2F%2Fimage.tmdb.org%2Ft%2Fp%2Foriginal%2F4bUd3nUGD2XnhLkYNCXHFjPHEH5.jpg (I tried with and without HTTPS on my side, just in case, but it doesn't make a difference). The URL pointed to (https://image.tmdb.org/t/p/original/4bUd3nUGD2XnhLkYNCXHFjPHEH5.jpg) seems to work OK if I try to display it directly in my browser. If I modify the URL to https://mynasip:8920/emby/Images/Remote?imageUrl=http%3A%2F%2Fimage.tmdb.org%2Ft%2Fp%2Foriginal%2F4bUd3nUGD2XnhLkYNCXHFjPHEH5.jpg of course it does work, but I  have yet to find where I can configure Emby to scrape images with an unsecured connection.

 

Some context: this is on xpen DSM 5.2-5967 with Emby 3.2.30.0-1.

 

Is there anything I can do to work around this ? I mean, the library would definitely look way better with the cover art :-)

 

Thanks a lot for Emby, for reading this and for any help you might be able to provide.

Link to comment
Share on other sites

lesensei

Hello,
 
Thanks for your reply. Sorry I didn't attach the server log, I should have thought of doing that. I know I should post the full log, but it's quite huge and I believe the following excerpt show the problem quite well. If necessary, I'll still post the full log, of course.

2017-09-04 00:18:06.726 Info App: MovieDbProvider: Finding id for item: Harry Potter Philosopher Stone
2017-09-04 00:18:06.726 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/search/movie?api_key=f6bd687ffa63cd282b6ff2c6877f2669&query=Harry+Potter+Philosopher+Stone&language=fr
2017-09-04 00:18:07.026 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/movie/671?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=casts,releases,images,keywords,trailers&language=fr&include_image_language=fr,null,en
2017-09-04 00:18:07.380 Info HttpClient: HttpClientManager GET: https://api.themoviedb.org/3/movie/671?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=casts,releases,images,keywords,trailers
2017-09-04 00:18:07.516 Info HttpClient: HttpClientManager GET: https://image.tmdb.org/t/p/original/4bUd3nUGD2XnhLkYNCXHFjPHEH5.jpg
2017-09-04 00:18:07.530 Error HttpClient: Error SecureChannelFailure getting response from https://image.tmdb.org/t/p/original/4bUd3nUGD2XnhLkYNCXHFjPHEH5.jpg
	*** Error Report ***
	Version: 3.2.30.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.10.35.0
	64-Bit OS: True
	64-Bit Process: True
	Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Sat Apr 22 22:46:32 CST 2017)
	Processor count: 2
	Program data path: /var/packages/EmbyServer/target/var
	Application directory: /volume1/@appstore/EmbyServer/releases/v3.2.30.0
	System.Net.WebException: Error: SecureChannelFailure (SIGILL) ---> System.ExecutionEngineException: SIGILL
	  at (wrapper managed-to-native) Mono.Btls.MonoBtlsSsl:mono_btls_ssl_connect (intptr)
	  at Mono.Btls.MonoBtlsSsl.Connect () [0x00011] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.DoProcessHandshake () [0x0002e] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncProtocolRequest asyncRequest, Mono.Net.Security.AsyncOperationStatus status) [0x00033] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (Mono.Net.Security.AsyncOperationStatus status) [0x00086] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation () [0x0000d] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.StartOperation () [0x00000] in <f8255d9ef0594d18ae2c0d97286b9a80>: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 <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.Private.MonoSslStreamWrapper.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00006] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MonoTlsStream.CreateStream (System.Byte[] buffer) [0x0006a] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	   --- End of inner exception stack trace ---
	  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00064] in <f8255d9ef0594d18ae2c0d97286b9a80>: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) [0x00014] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	System.Net.WebException
	  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00064] in <f8255d9ef0594d18ae2c0d97286b9a80>: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) [0x00014] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	InnerException: System.ExecutionEngineException
	System.ExecutionEngineException: SIGILL
	  at (wrapper managed-to-native) Mono.Btls.MonoBtlsSsl:mono_btls_ssl_connect (intptr)
	  at Mono.Btls.MonoBtlsSsl.Connect () [0x00011] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.DoProcessHandshake () [0x0002e] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncProtocolRequest asyncRequest, Mono.Net.Security.AsyncOperationStatus status) [0x00033] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (Mono.Net.Security.AsyncOperationStatus status) [0x00086] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation () [0x0000d] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.StartOperation () [0x00000] in <f8255d9ef0594d18ae2c0d97286b9a80>: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 <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.Private.MonoSslStreamWrapper.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00006] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MonoTlsStream.CreateStream (System.Byte[] buffer) [0x0006a] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at (wrapper managed-to-native) Mono.Btls.MonoBtlsSsl:mono_btls_ssl_connect (intptr)
	  at Mono.Btls.MonoBtlsSsl.Connect () [0x00011] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.DoProcessHandshake () [0x0002e] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncProtocolRequest asyncRequest, Mono.Net.Security.AsyncOperationStatus status) [0x00033] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (Mono.Net.Security.AsyncOperationStatus status) [0x00086] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation () [0x0000d] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.StartOperation () [0x00000] in <f8255d9ef0594d18ae2c0d97286b9a80>: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 <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.Private.MonoSslStreamWrapper.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00006] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MonoTlsStream.CreateStream (System.Byte[] buffer) [0x0006a] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 

However, when I modify the URL to fetch the image without TLS, I get the following log:

2017-09-04 00:53:09.801 Info HttpServer: HTTP GET http://mynasip:8096/emby/Images/Remote?imageUrl=http%3A%2F%2Fimage.tmdb.org%2Ft%2Fp%2Foriginal%2F4bUd3nUGD2XnhLkYNCXHFjPHEH5.jpg. UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
2017-09-04 00:53:09.803 Info HttpClient: HttpClientManager GET: http://image.tmdb.org/t/p/original/4bUd3nUGD2XnhLkYNCXHFjPHEH5.jpg
2017-09-04 00:53:10.677 Info HttpResultFactory: Transmit file /var/packages/EmbyServer/target/var/cache/remote-images/1/1dfa05d0-fb15-2204-ceb4-d61917e9427f.jpeg
2017-09-04 00:53:10.705 Info HttpServer: HTTP Response 200 to 192.168.1.11. Time: 904ms. http://mynasip:8096/emby/Images/Remote?imageUrl=http%3A%2F%2Fimage.tmdb.org%2Ft%2Fp%2Foriginal%2F4bUd3nUGD2XnhLkYNCXHFjPHEH5.jpg 

I haven't found a way to make the scraper use non-TLS connections simply by looking on the github, and I have no clue where the error comes from.

 

From what I can tell trying both the api and the image URLs in the browser, the problem might come from the image URL using cloudflare. In that certificate, the *.tmdb.org CN is not the main one, only one of the alternate CNs. But I guess Mono doesn't have a problem with that, or I wouldn't be the only one facing this problem. So once again, no clue :-(

 

Thanks for your help !

Edited by lesensei
Link to comment
Share on other sites

lesensei

Hello everyone,

 

I figured that since stable Emby wasn't working here anyway, I might as well try the beta version. And so thanks to @@solabc16, I've installed version 3.2.30.8-1-beta. Now I'm getting a different error when loading a movie details page that crashes the Emby server (relevant logs attached). I've now updated my xpenology to DSM 6.0.2-8451, but the result is the same (SIGILL on external images loading with stable version, crash on movie details with beta version).

 

What can I do to help find the source of the error(s) ?

 

Regards,

 

embysvr.stderr.txt

Link to comment
Share on other sites

solabc16

Hello @@lesensei

 

If possible, can you run the diagnostics (https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Run-Diagnostics) and send logs (https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs) utilities.

 

We need to make sure you have the package that targets the correct processor architecture, as you are running on XPEnology.

 

Best

- James

Link to comment
Share on other sites

solabc16

Hello @@lesensei

 

Thanks for the diags, if you can run the send logs utility, that would help.

 

What URL do you have configured in Package Centre for Emby LLC?

 

Best

- James

Link to comment
Share on other sites

lesensei

Sorry @@solabc16

 

I forgot about the log part, that's done: sendlogs_MegaBloub_synology_bromolow_3615xs_20170907T163949UTC.tgz

 

I am currently using the beta repository (the URL you sent me), but to try with DSM 6 and the stable Emby, I unchecked the "beta" checkbox after uninstalling the beta version.

 

Thanks again.

 

Regards,

Link to comment
Share on other sites

  • Solution
solabc16

Hello @@lesensei

 

Thanks for the logs. As your XPEnology system is AMD based, you need to use a package that is tailored to this processor architecture.

 

Please can you configure Package Center to use the following URL, then uninstall and reinstall Emby Server.

https://synology.emby.media/?package_repository=360efc6e-de72-4073-b603-2bfbd7001586&package_architecture=xpen-barcelona
There's some background information here (https://emby.media/community/index.php?/topic/40411-xpenology-users-read-me/) and here (https://github.com/MediaBrowser/Wiki/wiki/Synology-:-Custom-Package-Architectures-for-XPEnology).

 

Let me know how you get on...

 

Best

- James

Edited by solabc16
  • Like 1
Link to comment
Share on other sites

lesensei

Hello @@solabc16

 

I'm pretty ashamed to say this was the problem. I had read said pages, but had understood that the Turion in the N54L was amongst the processors supporting the necessary set of instructions for the default repository. In retrospect, I have no clue how I ended up with this belief, and I guess I was just convinced beforehand.

 

Sorry for the time you lost on me, and many thanks for your help: the stable version is now running without so much as a hiccup.

 

Regards,

Link to comment
Share on other sites

Hello!

I have the same problem.

Emby worked well on my xpenology until latest update.

Now it started and worked well in order to serve content, but it shows same symptoms as topic starter said.

Part of the log:

2017-09-12 15:36:04.143 Error HttpClient: Error SecureChannelFailure getting response from https://image.tmdb.org/t/p/original/4Q9cwBtZiML2kr2h24AMfHuVdYI.jpg
	*** Error Report ***
	Version: 3.2.30.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.10.102.0
	64-Bit OS: True
	64-Bit Process: True
	Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Sat Apr 22 22:46:32 CST 2017)
	Processor count: 4
	Program data path: /var/packages/EmbyServer/target/var
	Application directory: /volume3/@appstore/EmbyServer/releases/v3.2.30.0
	System.Net.WebException: Error: SecureChannelFailure (SIGILL) ---> System.ExecutionEngineException: SIGILL
	  at (wrapper managed-to-native) Mono.Btls.MonoBtlsSsl:mono_btls_ssl_connect (intptr)
	  at Mono.Btls.MonoBtlsSsl.Connect () [0x00011] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.DoProcessHandshake () [0x0002e] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncProtocolRequest asyncRequest, Mono.Net.Security.AsyncOperationStatus status) [0x00033] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (Mono.Net.Security.AsyncOperationStatus status) [0x00086] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation () [0x0000d] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.StartOperation () [0x00000] in <f8255d9ef0594d18ae2c0d97286b9a80>: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 <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.Private.MonoSslStreamWrapper.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00006] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MonoTlsStream.CreateStream (System.Byte[] buffer) [0x0006a] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	   --- End of inner exception stack trace ---
	  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00064] in <f8255d9ef0594d18ae2c0d97286b9a80>: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) [0x00014] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	System.Net.WebException
	  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00064] in <f8255d9ef0594d18ae2c0d97286b9a80>: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) [0x00014] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 
	InnerException: System.ExecutionEngineException
	System.ExecutionEngineException: SIGILL
	  at (wrapper managed-to-native) Mono.Btls.MonoBtlsSsl:mono_btls_ssl_connect (intptr)
	  at Mono.Btls.MonoBtlsSsl.Connect () [0x00011] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.DoProcessHandshake () [0x0002e] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncProtocolRequest asyncRequest, Mono.Net.Security.AsyncOperationStatus status) [0x00033] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (Mono.Net.Security.AsyncOperationStatus status) [0x00086] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation () [0x0000d] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.StartOperation () [0x00000] in <f8255d9ef0594d18ae2c0d97286b9a80>: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 <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.Private.MonoSslStreamWrapper.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00006] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MonoTlsStream.CreateStream (System.Byte[] buffer) [0x0006a] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at (wrapper managed-to-native) Mono.Btls.MonoBtlsSsl:mono_btls_ssl_connect (intptr)
	  at Mono.Btls.MonoBtlsSsl.Connect () [0x00011] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.DoProcessHandshake () [0x0002e] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Btls.MonoBtlsContext.ProcessHandshake () [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.ProcessHandshake (Mono.Net.Security.AsyncProtocolRequest asyncRequest, Mono.Net.Security.AsyncOperationStatus status) [0x00033] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation (Mono.Net.Security.AsyncOperationStatus status) [0x00086] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.ProcessOperation () [0x0000d] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.AsyncProtocolRequest.StartOperation () [0x00000] in <f8255d9ef0594d18ae2c0d97286b9a80>: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 <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MobileAuthenticatedStream.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x0000c] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.Private.MonoSslStreamWrapper.AuthenticateAsClient (System.String targetHost, System.Security.Cryptography.X509Certificates.X509CertificateCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) [0x00006] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
	  at Mono.Net.Security.MonoTlsStream.CreateStream (System.Byte[] buffer) [0x0006a] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 

Package Center use this URL for packages: https://synology.emby.media/?package_repository=360efc6e-de72-4073-b603-2bfbd7001586

Real processor model used for NAS: INTEL Core i3-4130

Link to comment
Share on other sites

solabc16

Hello @@mizhgan

 

Thanks for getting in touch. If possible, can you run the diagnostics (https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Run-Diagnostics) and send logs https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs) utilities - that will give me some more information to work on.

 

At face value, this shouldn't be a problem on you system. Is this a bare-metal system or a VM?

 

Best

- James

Edited by solabc16
Link to comment
Share on other sites

Hello!

As you requested -> sendlogs_NAS_synology_bromolow_3615xs_20170914T060942UTC.tgz

And my bad, real processor model used in my NAS is: AMD Phenom 9850 Quad-Core Processor

My system is bare-metal as well.

Link to comment
Share on other sites

solabc16

Hello @@mizhgan

 

No problem, that all makes sense then. The AMD Phenom is based on the K10 microarchitecture, so we already have a more suitable package available.

 

See https://emby.media/community/index.php?/topic/50599-emby-not-scraping-images/?p=485189

 

If your system is already setup and you don't want to re-install Emby Server, let me know and I'll message you with instructions.

 

Best

- James

  • Like 1
Link to comment
Share on other sites

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
 Share

×
×
  • Create New...