Jellyfin can not download POSTER from TMDB

[netduke999]

1，Jellyfin was able to synchronize TMDB normally until a few days ago when it suddenly couldn't synchronize POSTER, but other metadata could still be synchronized normally.
2， The images of actors, crew, and series are recognized for normal synchronous download. Only three types of images, POSTER, BACK DROPS, and MARK, from movie and TV, can be seen in JELLYFIN but cannot be downloaded locally. At the same time, posters, backdrops, and marks on websites such as Fanart and Tvmaze can still be displayed, synchronized, and downloaded normally.
3，The TMDB test shows that my network configuration is normal, except that it cannot automatically synchronize three types of images. Everything else is normal, including the series of posters that can also be automatically synchronized.
4，I consulted TMDB and they suggested suspecting it to be Jellyfin's problem. They also admitted that their website had some issues a few days ago. 

5，My Jellyfin ver 10.8.13 ，QNAP Nas doker 。
Below is a copy of their email.


@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 " [b]tmdb-image[/b] "
https://status.themoviedb.org/#/componen...D1xTbABEoG
Maybe this has affected your access.
I just tested it and received it without problems.
https://image.tmdb.org/t/p/original/jbwY...KQjCEB.jpg
https://image.tmdb.org/t/p/w500/jbwYaoYW...KQjCEB.jpg

---

[b]EDIT[/b]
This base URL is old.
[b]media.themoviedb.org[/b]
It refers to the current one.
[b]image.tmdb.org[/b]
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.

[TheDreadPirate]

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

[netduke999]

[netduke@Nas ~]$ curl -vvv https://image.tmdb.org/t/p/original/uqIV...xiyY4z.jpg -o /tmp/futurama.jpg

  % Total    % Received % Xferd  Average Speed  Time    Time    Time  Current
                                Dload  Upload  Total  Spent    Left  Speed
  0    0    0    0    0    0      0      0 --:--:-- --:--:-- --:--:--    0* Host image.tmdb.org:443 was resolved.
* IPv6: (none)
* IPv4: 169.150.249.168
*  Trying 169.150.249.168:443...
* Connected to image.tmdb.org (169.150.249.16 port 443
* ALPN: curl offers http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
*  CAfile: none
*  CApath: /etc/ssl/certs
* Recv failure: Connection reset by peer
* OpenSSL SSL_connect: Connection reset by peer in connection to image.tmdb.org:443
  0    0    0    0    0    0      0      0 --:--:-- --:--:-- --:--:--    0
* Closing connection

curl: (35) Recv failure: Connection reset by peer

[TheDreadPirate]

And what happens when you open a bash shell for the jellyfin container and run that same curl command there?

[netduke999]

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

[TheDreadPirate]

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?

[netduke999]

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?

Thank you for your response.

[TheDreadPirate]

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?

Thank you for your response.

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://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.

[netduke999]

I understand, I am consulting with my local ISP. Thank you very much for your support, thank you!