Timed Out - Error in TheMovieDb / getting available plugin updates

[Endymion 6]

Any new content I've added in the past few days is only getting partial nfo or not at all. Most of the nfo comes from TheMovieDb, but that is timing out.

I was going to try uninstalling and reinstalling the plugin But, I get just a spinning circle when I go to Plugins/Catalog. So, I didn't try that. It seems something else may be happening.

I do not know what is going on. I've reset every devices and restarted Emby several times. I haven't messed with any settings or changed any hardware in months. It is just something that just started happening (few days ago). I was thinking that maybe TheMovieDb api was down. So, I just let it be, for a couple of days. And that maybe the case, but I haven't seen any news on that (through searches).

So, I've come here for some help and see if anybody can point me in the right direction to solves this. I've included a log from server start till I tried up dating a movie nfo.

embyserver.12.3.txt

[Neminem 1518]

Quote

Error in TheMovieDb    *** Error Report ***
    Version: 4.9.1.90
    Command line: /volume1/.@plugins/AppCentral/emby-server/system/EmbyServer.dll -programdata /home/emby -ffdetect /usr/local/AppCentral/emby-server/bin/ffdetect -ffmpeg /usr/local/AppCentral/emby-server/bin/ffmpeg -ffprobe /usr/local/AppCentral/emby-server/bin/ffprobe -pidfile /var/run/emby-server.pid -defaultdirectory /volume1/Public -updatepackage emby-server-asustor_{version}_x86-64.apk
    Operating system: Linux version 5.13.x (root@sw1-dailybuild) (x86_64-asustor_x64_g3_2020.12.24-linux-gnu-gcc (crosstool-NG 1.24.0) 7.4.0, GNU ld (crosstool-NG 1.24.0) 2
    OS/Process: x64/x64
    Framework: .NET 8.0.11
    Runtime: volume1/.@plugins/AppCentral/emby-server/system/System.Private.CoreLib.dll
    Processor count: 4
    Data path: /home/emby
    Application path: /volume1/.@plugins/AppCentral/emby-server/system
    MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Connection to https://api.themoviedb.org/3/configuration/primary_translations?api_key=x_secret4_x 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.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, 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 MovieDb.MovieDbProviderBase.GetMovieDbResponse(HttpRequestOptions options)
       at MovieDb.MovieDbProviderBase.GetTmdbLanguages(CancellationToken cancellationToken)
       at MovieDb.GenericMovieDbInfo`1.GetMetadata(ItemLookupInfo searchInfo, CancellationToken cancellationToken)
       at Emby.Providers.Manager.MetadataService`2.ExecuteRemoteProviders(MetadataResult`1 temp, LibraryOptions libraryOptions, String logName, TIdType id, IRemoteMetadataProvider`2[] providers, MetadataRefreshOptions options, CancellationToken cancellationToken)
    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.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, 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)
    
 

See marked in red are you having DNS, firewall, network, internet or security software issues, that is blocking those requests?

[Endymion 6]

I'll look into that more. That seems to be the case, as some connections are going through and other are not. It has really thrown me for a loop on why it suddenly started happening. I'll have to dig though my router settings to see what may have changed. That is the only thing that I can think of that may have been changed (auto updated?) recently, besides Emby and that was/is working fine.

[Luke 42077]

Hi, please let us know what you find. Thanks.

[Endymion 6]

I really do not get it. Something crazy has happened and I can not figure it out.

I've went through my router settings and I don't see anything that has changed. Everything else on my network works fine. So, that leaves to believe, that something wonky has happened in my NAS. Either something got corrupted in my NAS software or in Emby's software. At least, that is what I'm thinking.

I've also went through all my NAS settings and I did not see anything there, either.

I've tried uninstalling Emby... which it really doesn't seem to uninstall anything. I went in and manually deleted the cache and all the plugins (to force a reinstall on those, since they were still there). I reinstalled Emby and it is doing the same exact thing.

I'm not sure what maybe corrupted or what is safe to delete and have reinstalled without having to do a complete rebuild. With 10+yrs of data (100+TB) will take a very long time to rebuild. And before anybody ask, yes I have back ups. It just takes a long time to move all that data.

I'll try a factory rest on my router, when no one is on it, but I doubt that is my issue. Any other pointers is more then welcome.

Thanks

[Luke 42077]

Did you try rebooting the router?

[Endymion 6]

Yes... everything on the network was either off or rebooted, including the modems. I have also discontented everything to the router, except the NAS and this PC. I've tried using different ports on the router with the same results.

Before I start digging more into my NAS... I will try the most direct approach. I'll try connecting directly to my modems (2 internet providers). If the problem persist, I'll try a factory rest on those and the router. I'll even try a test install of Emby on a different machine and see if I have the same issues. That is what I'll probably do next. That should tell me if it's a network thing or a machine thing.

I honestly believe something got corrupted in my NAS. Being, that I have no other issues on the network and no one else is having the issue. The Emby test install should confirm. I'll try all sorts of stuff to avoid that complete rebuild.

[Luke 42077]

You could also try disabling ipv6 in your router.

[Endymion 6]

Thanks... I'll try that too. I believe that is enabled in both.

[Endymion 6]

I can't believe it... ipv6 was the problem. I don't understand why it suddenly started acting up. It has been on for awhile. So, I didn't even think to check that.

Thanks for that... you saved me from all that mess I was about to put myself through. The simplest things we miss. Cheers

[lal 4]

I had the same issue moving media around and struggling to get media from tmdb refreshed

To troubleshoot I installed tinymediamanager ... metadata and art was grabbing without any issues, so I started storing nfo's and art to my folders so I could change emby to read from my local drives ... started a full emby scan to regrab and read nfo locally but still fetch artwork from tmdb through emby ...that's where I noticed all the timeouts in the log. Changed my modem to ipv4 and the timeouts stopped.

ipv6 works with tmm to tmdb

ipv6 does not work with emby to tmdb