SOLVED: Consistent Failures Fetching Metadata from TheMovieDB

SOLVED: Consistent Failures Fetching Metadata from TheMovieDB - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Consistent Failures Fetching Metadata from TheMovieDB (/t-solved-consistent-failures-fetching-metadata-from-themoviedb)

Consistent Failures Fetching Metadata from TheMovieDB - nxl4 - 2024-05-26

For the past week, all attempts to fetch metadata for TV shows have been failing, with the error logs consistently indicating the unavailability of TheMovieDB API. Here's an example from this morning:

Code:
[2024-05-26 04:58:58.182 -05:00] [ERR] [81] MediaBrowser.Providers.TV.SeriesMetadataService: Error in "TheMovieDb"

System.Net.Http.HttpRequestException: Resource temporarily unavailable (api.themoviedb.org:443)

Is there a current known issue with this service in Jellyfin? And, if so, is there a workaround that people are currently using (e.g. a different API)?

RE: Consistent Failures Fetching Metadata from TheMovieDB - TheDreadPirate - 2024-05-26

On the command line are you able to ping themoviedb.org?

RE: Consistent Failures Fetching Metadata from TheMovieDB - nxl4 - 2024-05-26

(2024-05-26, 03:57 PM)TheDreadPirate Wrote: On the command line are you able to ping themoviedb.org?

Yeah, ping shows the host being responsive:

Code:
PING api.themoviedb.org (52.85.247.33) 56(84) bytes of data.

64 bytes from server-52-85-247-33.ord51.r.cloudfront.net (52.85.247.33): icmp_seq=1 ttl=247 time=54.5 ms

64 bytes from server-52-85-247-33.ord51.r.cloudfront.net (52.85.247.33): icmp_seq=2 ttl=247 time=56.0 ms

64 bytes from server-52-85-247-33.ord51.r.cloudfront.net (52.85.247.33): icmp_seq=3 ttl=247 time=57.2 ms

And, nmap shows port 443 being open for HTTPS service:

Code:
Starting Nmap 7.80 ( https://nmap.org ) at 2024-05-26 15:04 EDT

Nmap scan report for api.themoviedb.org (52.85.247.30)

Host is up (0.057s latency).

Other addresses for api.themoviedb.org (not scanned): 52.85.247.81 52.85.247.33 52.85.247.69 2600:9000:2211:7600:c:174a:c400:93a1 2600:9000:2211:ea00:c:174a:c400:93a1 2600:9000:2211:b200:c:174a:c400:93a1 2600:9000:2211:f600:c:174a:c400:93a1 2600:9000:2211:9e00:c:174a:c400:93a1 2600:9000:2211:3200:c:174a:c400:93a1 2600:9000:2211:ac00:c:174a:c400:93a1 2600:9000:2211:9a00:c:174a:c400:93a1

rDNS record for 52.85.247.30: server-52-85-247-30.ord51.r.cloudfront.net

Not shown: 997 filtered ports

PORT    STATE  SERVICE

53/tcp  closed domain

80/tcp  open  http

443/tcp open  https

Nmap done: 1 IP address (1 host up) scanned in 6.37 seconds

It's pretty strange, especially if other users aren't seeing the same kind of error.

RE: Consistent Failures Fetching Metadata from TheMovieDB - TheDreadPirate - 2024-05-26

Do you have a pihole or some other DNS based adblocker on your network?

RE: Consistent Failures Fetching Metadata from TheMovieDB - nxl4 - 2024-05-26

(2024-05-26, 07:37 PM)TheDreadPirate Wrote: Do you have a pihole or some other DNS based adblocker on your network?

Nope, nothing is between the NAS on which Jellyfin is hosted and my router. I just realized that this must be a networking issue on my end though, although I'm at a loss. The ping and nmap results I showed above were directly from my laptop. When I try and run a ping from an SSH into my NAS, it fails to resolve the host name:

Code:
ping: api.themoviedb.org: Temporary failure in name resolution

In fact, it appears that I get the same error when trying to ping any host name from my NAS. However, if I ping an IP address directly, this works fine. Definitely a "me" issue, then, and not anything that's even specific to Jellyfin.

EDIT: Aaand, it turns out that rebooting the server fixed the DNS issue!

RE: Consistent Failures Fetching Metadata from TheMovieDB - TheDreadPirate - 2024-05-26

Restart the NAS, restart the router?

RE: Consistent Failures Fetching Metadata from TheMovieDB - nxl4 - 2024-05-26

(2024-05-26, 08:39 PM)TheDreadPirate Wrote: Restart the NAS, restart the router?

Hah, posted just as I was editing my last one. A reboot did the trick. Somehow, in the last few months of continuous uptime, my DNS resolution got screwy.