BrettDioson 4 Posted December 8, 2016 Posted December 8, 2016 Hello, Just noticed today that I am unable to get information on new episodes that I add to the library. I am seeing the following error in the log: 2016-12-07 21:23:31.0871 Error HttpClient: Error getting response from https://www.thetvdb.com/api/B89CE93890E9419B/series/83237/all/en.zip *** Error Report *** Version: 3.0.8500.0 Command line: D:\Program Files\Emby-Server\System\MediaBrowser.ServerApplication.exe -service Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 24 64-Bit OS: True 64-Bit Process: True Program data path: D:\Program Files\Emby-Server Application Path: D:\Program Files\Emby-Server\System\MediaBrowser.ServerApplication.exe One or more errors occurred. System.AggregateException at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext() InnerException: System.Net.WebException The request was aborted: Could not create SSL/TLS secure channel. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) 2016-12-07 21:23:31.0871 Error App: Error in TheTVDB *** Error Report *** Version: 3.0.8500.0 Command line: D:\Program Files\Emby-Server\System\MediaBrowser.ServerApplication.exe -service Operating system: Microsoft Windows NT 6.2.9200.0 Processor count: 24 64-Bit OS: True 64-Bit Process: True Program data path: D:\Program Files\Emby-Server Application Path: D:\Program Files\Emby-Server\System\MediaBrowser.ServerApplication.exe One or more errors occurred. MediaBrowser.Model.Net.HttpException at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsync>d__17.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<Get>d__14.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Providers.TV.TvdbSeriesProvider.<DownloadSeriesZip>d__25.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Providers.TV.TvdbSeriesProvider.<DownloadSeriesZip>d__24.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Providers.TV.TvdbSeriesProvider.<EnsureSeriesInfo>d__29.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Providers.TV.TvdbEpisodeProvider.<GetMetadata>d__10.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at MediaBrowser.Providers.Manager.MetadataService`2.<ExecuteRemoteProviders>d__25.MoveNext() InnerException: System.AggregateException One or more errors occurred. at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at MediaBrowser.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext() InnerException: System.Net.WebException The request was aborted: Could not create SSL/TLS secure channel. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) I haven't seen this type of issue in the log before so wasn't sure if anyone else has come across this. I have seen issues in the past with rights assignments where emby wasn't able to create a new file or directory based on the account it was running under but this doesn't look like that issue. Thanks, BrettDioson
Solution mastrmind11 722 Posted December 8, 2016 Solution Posted December 8, 2016 Looks like a TVDB issue: Error HttpClient: Error getting response from https://www.thetvdb.com/api/B89CE93890E9419B/series/83237/all/en.zip I just tried to access directly in Chrome and it prompted me to download the file, so I'm guessing it was a network blip and it'll work now if you try it. 1
horstepipe 422 Posted December 8, 2016 Posted December 8, 2016 yeah tvdb had some downtime yesterday, I wasn't able to scrape episodes, either. Today everything is normal again.
BrettDioson 4 Posted December 8, 2016 Author Posted December 8, 2016 Confirmed it seems to be working again today. Sorry for the false alarm.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now