Nightreaver 8 Posted August 7, 2022 Share Posted August 7, 2022 (edited) Hello, recently I'm hitting the issues that next to the ssl errors i'ave seen in the past, im getting these timeouts: 2022-08-08 00:45:34.327 Error HttpClient: Connection to https://private.omdbapi.com?apikey=fe53f97e&i=tt8337158&plot=short&tomatoes=true&r=json timed out 2022-08-08 00:45:34.335 Error ProviderManager: OmdbImageProvider failed in GetImageInfos for type Movie *** Error Report *** Version: 4.7.6.0 Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.dll -programdata /volume1/Emby -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -ignore_vaapi_enabled_flag -pidfile /volume1/Emby/EmbyServer.pid -defaultdirectory /volume1/Public -updatepackage emby-server-synology_{version}_x86_64.spk -noautorunwebapp Operating system: Linux version 4.4.59+ (root@build3) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #25556 SMP PREEMPT Sat Aug 28 02:17:26 CST 2021 Framework: .NET 6.0.2 OS/Process: x64/x64 Runtime: volume1/@appstore/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Data path: /volume1/Emby Application path: /volume1/@appstore/EmbyServer/system MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Connection to https://private.omdbapi.com?apikey=fe53f97e&i=tt8337158&plot=short&tomatoes=true&r=json timed out ---> System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 20 seconds elapsing. ---> System.TimeoutException: A task was canceled. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled. at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken) at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) --- End of inner exception stack trace --- --- End of inner exception stack trace --- at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) --- End of inner exception stack trace --- at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod) at OMDb.Common.OmdbProvider.GetRootObject(String imdbId, IDirectoryService directoryService, CancellationToken cancellationToken) at OMDb.Common.OmdbImageProvider.GetImages(RemoteImageFetchOptions options, CancellationToken cancellationToken) at Emby.Providers.Manager.ProviderManager.GetImages(BaseItem item, LibraryOptions libraryOptions, CancellationToken cancellationToken, IRemoteImageProvider provider, IDirectoryService directoryService, Int32 providerIndex) Source: Emby.Server.Implementations TargetSite: Void MoveNext() InnerException: System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 20 seconds elapsing. Source: System.Net.Http TargetSite: Void HandleFailure(System.Exception, Boolean, System.Net.Http.HttpResponseMessage, System.Threading.CancellationTokenSource, System.Threading.CancellationToken, System.Threading.CancellationTokenSource) at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod) InnerException: System.TimeoutException: A task was canceled. Source: TargetSite: InnerException: System.Threading.Tasks.TaskCanceledException: A task was canceled. Source: System.Private.CoreLib TargetSite: Void ThrowForNonSuccess(System.Threading.Tasks.Task) at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.GetHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken) at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken) I cannot tell why or how that works. If I connect to the NAS and run a curl on the same url it works fine. Me@Home:~$ curl -v https://private.omdbapi.com?apikey=fe53f97e&i=tt8337158&plot=short&tomatoes=true&r=json [1] 10894 [2] 10895 [3] 10896 [4] 10898 Me@Home:~$ * TLSv1.2 (OUT), TLS header, Certificate Status (22): * TLSv1.2 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Client hello (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS change cipher, Client hello (1): * TLSv1.2 (IN), TLS handshake, Finished (20): > GET /?apikey=fe53f97e HTTP/2 > Host: private.omdbapi.com > User-Agent: curl/7.54.0 > Accept: */* > < HTTP/2 200 < date: Sun, 07 Aug 2022 22:51:31 GMT < content-type: application/json; charset=utf-8 < content-length: 49 < cache-control: public, max-age=86400 < expires: Sun, 07 Aug 2022 02:40:19 GMT < last-modified: Sun, 07 Aug 2022 01:40:19 GMT < vary: * < x-aspnet-version: 4.0.30319 < x-powered-by: ASP.NET < access-control-allow-origin: * < cf-cache-status: HIT < age: 76272 < accept-ranges: bytes < expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" < server: cloudflare < cf-ray: 737393d21918be35-CPH < {"Response":"False","Error":"Incorrect IMDb ID."} [1] Done curl -v https://private.omdbapi.com?apikey=fe53f97e [2] Done i=tt8337158 [3]- Done plot=short [4]+ Done tomatoes=true Me@Home:~$ Im not aware that Synology NAS has any outgoing firewall or something else that could prevent emby from connecting to any website. If I check "Secuurity > Firewall" its disabled. Overall Emby works well, beside querying and new movies/shows, no other issues with the NAS as well, connection to internal external work well overall. Synology DS918+ @ DSM 6.2.4-25556 Update 6 Urls dont matter, everything timing out. No other issues in my network are known so far. Edited August 7, 2022 by Nightreaver Link to comment Share on other sites More sharing options...
Luke 36886 Posted August 7, 2022 Share Posted August 7, 2022 Hi there, please attach the complete emby server log. Also are you able to update to DSM 7? Link to comment Share on other sites More sharing options...
Nightreaver 8 Posted August 7, 2022 Author Share Posted August 7, 2022 (edited) Log attached, I didnt want to update to DSM7 yet, any reason? Edited August 8, 2022 by Nightreaver Link to comment Share on other sites More sharing options...
Luke 36886 Posted August 7, 2022 Share Posted August 7, 2022 Are you using a VPN? It looks like something is blocking the server from sending outgoing communications. Link to comment Share on other sites More sharing options...
Nightreaver 8 Posted August 7, 2022 Author Share Posted August 7, 2022 Yes, something is blocking outgoing connections on emby, tho not vpn, firewall or any other known. Question is, why internet work for whole NAS but not for emby running on that NAS? Link to comment Share on other sites More sharing options...
Nightreaver 8 Posted August 8, 2022 Author Share Posted August 8, 2022 I solved it by activating the firewall , then suddenly everything works well again. Cannot remember it was ever enabled before but anyways. Link to comment Share on other sites More sharing options...
Luke 36886 Posted August 8, 2022 Share Posted August 8, 2022 Well that is strange indeed, but thanks for following up .! Link to comment Share on other sites More sharing options...
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