@netduk said:

Question:

1. In Jellyfin, movies can be identified by their names in TMDB, and cover images from TMDB and Fanart can also be displayed. However, TMDB images cannot be downloaded, and they can be downloaded normally in FANART.
2. The hosts have been configured normally, media.themoviedb.org， Both image.tmdb.org and can be pinged normally.
3. Everything seemed normal yesterday.
4. Preliminary judgment is that it is a website issue. I would like to inquire about the situation?

Thank you for your response

Yesterday there was an excess of requests.
https://status.themoviedb.org/
In " tmdb-image "
https://status.themoviedb.org/#/components/CV8aDz4Xn5ikJZrRQr_JNPHGtfSICRu-BHYPYCxe7yG6bHGKqrBzcWD1xTbABEoG
Maybe this has affected your access.
I just tested it and received it without problems.
https://image.tmdb.org/t/p/original/jbwYaoYWZwxtPP76AZnfYKQjCEB.jpg
https://image.tmdb.org/t/p/w500/jbwYaoYWZwxtPP76AZnfYKQjCEB.jpg

EDIT
This base URL is old.
media.themoviedb.org
It refers to the current one.
image.tmdb.org
I suggest you use only the current one.

@ticao2 said:

@netduk said:

Question:

1. In Jellyfin, movies can be identified by their names in TMDB, and cover images from TMDB and Fanart can also be displayed. However, TMDB images cannot be downloaded, and they can be downloaded normally in FANART.
2. The hosts have been configured normally, media.themoviedb.org， Both image.tmdb.org and can be pinged normally.
3. Everything seemed normal yesterday.
4. Preliminary judgment is that it is a website issue. I would like to inquire about the situation?

Thank you for your response

Yesterday there was an excess of requests.
https://status.themoviedb.org/
In " tmdb-image "
https://status.themoviedb.org/#/components/CV8aDz4Xn5ikJZrRQr_JNPHGtfSICRu-BHYPYCxe7yG6bHGKqrBzcWD1xTbABEoG
Maybe this has affected your access.
I just tested it and received it without problems.
https://image.tmdb.org/t/p/original/jbwYaoYWZwxtPP76AZnfYKQjCEB.jpg
https://image.tmdb.org/t/p/w500/jbwYaoYWZwxtPP76AZnfYKQjCEB.jpg

---

EDIT
This base URL is old.
media.themoviedb.org
It refers to the current one.
image.tmdb.org
I suggest you use only the current one.

Thank you for your reply.

1、Firstly, based on your suggestion, I have disabled "media. themoviedb. org" in the HOSTS file and only used "image. tmdb. org".

2、According to your reply, my test results show that everything is normal, and the results are as follows:

https://imgse.com/i/pAGJ8YR
https://imgse.com/i/pAGJlTJ

3、Accessing the website from CHROME is normal, and images can be uploaded and downloaded.

4、However, only images can be displayed from Jellyfin, but images cannot be downloaded from TMDB, while they can be downloaded normally from FANART and TVMAZE.

The following picture is an example of 'Detective Poirot'. You can see that the cover can be replaced with images from FANART and TVMAZE normally, but if TMDB is selected, it will display as continuously downloading. This circle is constantly rotating.

https://imgse.com/i/pAGJMmF
https://imgse.com/i/pAGJ3k9
https://imgse.com/i/pAGJQw4
https://imgse.com/i/pAGJGf1
https://imgse.com/i/pAGJYSx

5、In addition, although Jellyfin can recognize movies and TV shows in TDMB and synchronize metadata normally, it cannot synchronize images. However, images can still be downloaded normally from FANART and OPEN MOVIE. Jellyfin accesses TMDB through API. Currently, except for the inability to download images, all other functions are normal. I don't know why? Is it a problem with Jellyfin TMDB API?

6、In addition, actor avatars can be automatically synchronized, but POSTER, BACK DROPS, MARK cannot be downloaded and synchronized.

Hmm, I think the problem is with Jellyfin.
After all, you can access the images but Jellyfin can't.
I suggest asking for help on the Jellyfin forum.
https://forum.jellyfin.org/

@ticao2 said:

Hmm, I think the problem is with Jellyfin.
After all, you can access the images but Jellyfin can't.
I suggest asking for help on the Jellyfin forum.
https://forum.jellyfin.org/

I consulted Jellyfin and they said TMDB is locked. But the problem is that except for the three types of images, all other scraping information is normal, including actor image information and movie series POSTER, which can be scraped to the local area normally. Therefore, I suspect that there may be a problem with my TMDB API authorization. It is not the local operator that is locked, but the TMDB website that is locked. Could you please help verify this issue? Thank you.

Here is my consultation with Jellyfin.

TheDreadPirate Offline Community Moderator

Can you open a terminal on your NAS and run this command? Then share the output.

Code: curl -vvv https://image.tmdb.org/t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg -o /tmp/futurama.jpg

Thank you very much for your reply.

Do you mean to start the shell for each container from the container manager?

I have taken the following picture:

https://imgse.com/i/pAJ3ECt

https://imgse.com/i/pAJ3k4I

I am pretty sure your connection is being blocked. Either by your ISP or by your country. Can you try switching disabling TMDB in your library settings and setting TVDB as the top priority? A couple users from Russia discovered TMDB was blocked in their country but TVDB wasn't. Can you test if that is also the case for you? Or perhaps use a VPN?

1. I have always suspected this reason, but I have been using it for several years and only discovered this issue this week. At this time, the TMDB website is experiencing overload and website replacement issues, so I suspect that there may be a problem with the API and website coordination.
2. In addition, TMDB images can still be seen from Jellyfin, but they cannot be downloaded. Other metadata, actor information, and images can all be scraped normally. POSTER, MARK, BACK DROPS cannot automatically scrape from TMDB to the local area. And TVDB and FANART are both normal, but the information on these two websites is not as comprehensive as TMDB's.
3. These three types of images can still be uploaded and downloaded from CHROME, but cannot be automatically completed by Jellyfin. They can be manually downloaded separately and then manually added to the scraping process by Jellyfin. In fact, 80% of the scraping work can still be completed normally in the current situation, after all, the three types of images are not very heavy by hand, and FANART can provide a good alternative, while scraping data is more and more heavy.
4. By the way, the POSTER, MARK, and BACK DROPS in the movie series are all normal and can be automatically scraped by Jellyfin. So if it's a problem with the ISP, it's hard to explain this situation.
5. Is it possible that my API authorization has been locked by TMDB?

Many possibilities.
Let's try to eliminate some.

Is it possible that my API authorization has been locked by TMDB?

I don't think so, but...
Let's check your API Key

Take a Test
Using a computer, desktop or notebook.
On some mobile devices this test may not work correctly.
In the URL below, change THE_KEY to your API Key.
https://api.themoviedb.org/3/movie/550?api_key=THE_KEY
Use this example to do a search using a new tab or window in your browser.
You will receive the basic data of the Movie Fight Club (1999)
https://www.themoviedb.org/movie/550-fight-club
If it works, your Key is OK.

When there is a problem, the TMDb Server sends a message.
Can you tell which message the server sent?
Here is a list of possible messages:
https://developer.themoviedb.org/docs/errors

If it does not work, let us know right here.

Some other possibilities.

First: Go to this page again.
https://status.themoviedb.org/
While there, refresh with F5.
Then click on each of the 3 services.

• tmdb-api
• tmdb-image
• tmdb-web

While there, refresh with F5.
Let us know if everything is ok

Second: What country are you in?
Russia is blocked.
India is also blocked
And so is China.
It could be a new block from some country.

Third: Try changing your DNS.
Try Google 8.8.8.8
In some countries Cloudflare, 1.1.1.1, is causing problems.

Fourth: If possible, try using a VPN.

I just received Jellyfin's latest reply, and some of the knowledge is beyond my ability. I am currently learning... Now I will reply and paste it for you to refer to:

I noticed that depending on what you're doing with TMDB it uses different certs. What happens when you curl just the TMDB api URL?

Code: curl -vvv https://api.tmdb.org

A good result would be a "301 Moved Permanently" message.

Another thing I noticed is that images.tmdb.org using a different cert when you are actually downloading an image. What happens when you curl JUST the base images.tmdb.org URL?

Code: curl -vvv https://images.tmdb.org

Here are the various certs I see when accessing those URLs.

curl -vvv https://api.tmdb.org Code:

• Server certificate:

• subject: CN=*.tmdb.org

• start date: Sep 22 00:00:00 2024 GMT

• expire date: Oct 20 23:59:59 2025 GMT

• subjectAltName: host "api.tmdb.org" matched cert's "*.tmdb.org"

• issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M03

curl -vvv https://images.tmdb.org Code:

• Server certificate:

• subject: CN=images.tmdb.org

• start date: Sep 22 02:12:51 2024 GMT

• expire date: Dec 21 02:12:50 2024 GMT

• subjectAltName: host "images.tmdb.org" matched cert's "images.tmdb.org"

• issuer: C=US; O=Let's Encrypt; CN=R11

BUT, if I curl the images URL to download an image it uses yet another cert that has a validity date of Oct 6.

curl -vvv https://images.tmdb.orgcurl -vvv https://image.tmdb.org/t/p/original/uqIV...xiyY4z.jpg -o /tmp/futurama.jpg Code:

• Server certificate:

• subject: CN=image.tmdb.org

• start date: Oct 6 12:45:51 2024 GMT

• expire date: Jan 4 12:45:50 2025 GMT

• subjectAltName: host "image.tmdb.org" matched cert's "image.tmdb.org"

• issuer: C=US; O=Let's Encrypt; CN=R10

Now, I don't know how the Internet in your country works, but if your country is acting as a proxy for all TLS connections that leave your country, but your country's proxy doesn't recognize the new cert used when downloading images, that could be why the connection is getting reset.

@netduk said:
I just received Jellyfin's latest reply, and some of the knowledge is beyond my ability. I am currently learning...

And it's far from my capacity, too. :-)
The person who can help with this issue is Travis Bell, TMDb's admin.
Let's wait for him to come by.

@ticao2 said:

Many possibilities.
Let's try to eliminate some.

Is it possible that my API authorization has been locked by TMDB?

I don't think so, but...
Let's check your API Key

Take a Test
Using a computer, desktop or notebook.
On some mobile devices this test may not work correctly.
In the URL below, change THE_KEY to your API Key.
https://api.themoviedb.org/3/movie/550?api_key=THE_KEY
Use this example to do a search using a new tab or window in your browser.
You will receive the basic data of the Movie Fight Club (1999)
https://www.themoviedb.org/movie/550-fight-club
If it works, your Key is OK.

When there is a problem, the TMDb Server sends a message.
Can you tell which message the server sent?
Here is a list of possible messages:
https://developer.themoviedb.org/docs/errors

If it does not work, let us know right here.

This part of the test is normal, the authorization code is normal, and data from FIght Club can be received.

@ticao2 said:

@netduk said:
I just received Jellyfin's latest reply, and some of the knowledge is beyond my ability. I am currently learning...

And it's far from my capacity, too. :-)
The person who can help with this issue is Travis Bell, TMDb's admin.
Let's wait for him to come by.

Okay, it's just that a few pictures cannot be automatically scraped, but they can still be manually added without much effort. After all, a large amount of information can still automatically complete scraping. Ask another question: Why is it not supported to use IMDB ID directly for searching. Thank you for your reply, thank you!

@netduk said:

Ask another question: Why is it not supported to use IMDB ID directly for searching.
Thank you for your reply, thank you!

External IDs are supported only for finding the TMDb ID.
https://developer.themoviedb.org/reference/find-by-id