starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

TMDB Backdrop Scraping is Broken #7381

New Issue
Closed
opened 2026-02-07 04:52:46 +03:00 by OVERLORD · 28 comments
OVERLORD commented 2026-02-07 04:52:46 +03:00
Owner
Copy Link

Originally created by @mikewesten on GitHub (Oct 1, 2025).

Description of the bug

TMDB must have updated something on their end.
Backdrop images marked "No Language (xx-XX)" are now being scraped as Thumbs by Jellyfin instead of as Backdrops.
This may be something for the plugin developer to look into versus the Jellyfin Server developers, I'm not really sure.
Unless I'm mistaken this bug should be easily reproducible and is fairly self-explanatory without the need of a lengthy, detailed report.

Reproduction steps

See above

What is the current bug behavior?

See above

What is the expected correct behavior?

Scrape TMDB backdrop images marked "No Language (xx-XX)" as Backdrops instead of as Thumbs.

Jellyfin Server version

10.10.0+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

No response

Specify the build version

10.10.7

Environment

- OS:
- Linux Kernel:
- Virtualization:
- Clients:
- Browser:
- FFmpeg Version:
- Playback Method:
- Hardware Acceleration:
- GPU Model:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Jellyfin Data Storage:
- Media Storage:
- External Integrations:

Jellyfin logs

...

FFmpeg logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @mikewesten on GitHub (Oct 1, 2025). ### Description of the bug TMDB must have updated something on their end. Backdrop images marked "No Language (xx-XX)" are now being scraped as Thumbs by Jellyfin instead of as Backdrops. This may be something for the plugin developer to look into versus the Jellyfin Server developers, I'm not really sure. Unless I'm mistaken this bug should be easily reproducible and is fairly self-explanatory without the need of a lengthy, detailed report. ### Reproduction steps See above ### What is the current _bug_ behavior? See above ### What is the expected _correct_ behavior? Scrape TMDB backdrop images marked "No Language (xx-XX)" as Backdrops instead of as Thumbs. ### Jellyfin Server version 10.10.0+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number _No response_ ### Specify the build version 10.10.7 ### Environment ```markdown - OS: - Linux Kernel: - Virtualization: - Clients: - Browser: - FFmpeg Version: - Playback Method: - Hardware Acceleration: - GPU Model: - Plugins: - Reverse Proxy: - Base URL: - Networking: - Jellyfin Data Storage: - Media Storage: - External Integrations: ``` ### Jellyfin logs ```shell ... ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_
OVERLORD added the bugconfirmed labels 2026-02-07 04:52:46 +03:00
OVERLORD commented 2026-02-07 04:52:49 +03:00
Author
Owner
Copy Link

@mikewesten commented on GitHub (Oct 1, 2025):

Okay this is likely related to an API change at TMDB that just went live today
See here: https://www.themoviedb.org/talk/68c797b755b9cafed2a0f53f

@mikewesten commented on GitHub (Oct 1, 2025): Okay this is likely related to an API change at TMDB that just went live today See here: https://www.themoviedb.org/talk/68c797b755b9cafed2a0f53f
OVERLORD commented 2026-02-07 04:52:50 +03:00
Author
Owner
Copy Link

@Imgkl commented on GitHub (Oct 2, 2025):

I am able to reproduce this on my end too. Any tentative timeline on when the fix will land for this?

@Imgkl commented on GitHub (Oct 2, 2025): I am able to reproduce this on my end too. Any tentative timeline on when the fix will land for this?
OVERLORD commented 2026-02-07 04:52:52 +03:00
Author
Owner
Copy Link

@kandykarter commented on GitHub (Oct 2, 2025):

Seems like all the backdrop images are loading into the Thumbnail image area, visible if you select "All Languages". Decent workaround until a fix lands.

@kandykarter commented on GitHub (Oct 2, 2025): Seems like all the backdrop images are loading into the Thumbnail image area, visible if you select "All Languages". Decent workaround until a fix lands.
OVERLORD commented 2026-02-07 04:52:53 +03:00
Author
Owner
Copy Link

@Imgkl commented on GitHub (Oct 2, 2025):

Oh. That's good to know. Thanks @kandykarter

But the problem is many 3rd party apps and even swiftfin picks up only the backdrop and if it's not available, it falls back to primary image as backdrop or in some cases empty image icon. Hope this gets fixed soon.

@Imgkl commented on GitHub (Oct 2, 2025): Oh. That's good to know. Thanks @kandykarter But the problem is many 3rd party apps and even swiftfin picks up only the backdrop and if it's not available, it falls back to primary image as backdrop or in some cases empty image icon. Hope this gets fixed soon.
OVERLORD commented 2026-02-07 04:52:54 +03:00
Author
Owner
Copy Link

@kandykarter commented on GitHub (Oct 2, 2025):

Oh yeah I meant you can still search from the interface, you just have to manually save the images and set them as backdrops, still easier than a google search

@kandykarter commented on GitHub (Oct 2, 2025): Oh yeah I meant you can still search from the interface, you just have to manually save the images and set them as backdrops, still easier than a google search
OVERLORD commented 2026-02-07 04:52:55 +03:00
Author
Owner
Copy Link

@Shadowghost commented on GitHub (Oct 2, 2025):

This would likely need fixing in TMDbLib directly.

@Shadowghost commented on GitHub (Oct 2, 2025): This would likely need fixing in TMDbLib directly.
OVERLORD commented 2026-02-07 04:52:55 +03:00
Author
Owner
Copy Link

@Kockah commented on GitHub (Oct 3, 2025):

I also encountered the same issue.

It is also affecting the "Edit Images" for the images of actors, the UI will just return as empty/blank, but the workaround of selecting "All Languages" suggested by @kandykarter works for this too.

@Kockah commented on GitHub (Oct 3, 2025): I also encountered the same issue. It is also affecting the "Edit Images" for the images of actors, the UI will just return as empty/blank, but the workaround of selecting "All Languages" suggested by @kandykarter works for this too.
OVERLORD commented 2026-02-07 04:52:56 +03:00
Author
Owner
Copy Link

@francotosqui commented on GitHub (Oct 3, 2025):

Hi, I just wanted to confirm I’m experiencing this issue as well.

Backdrops from TMDB that are tagged with “no language” don’t show up in the media item detail view.

Instead, they appear only under the “Thumbnail” image area when selecting “All languages”.

Posters load fine, but the backdrop slot is always empty.

This affects the detail page backgrounds, not the home screen carousels.

As a workaround, I can manually upload or use “All languages”, but it would be great if Jellyfin could properly fetch and classify these backdrops.

Could this fix be considered for the 10.11.0 milestone?
This bug makes a lot of libraries look incomplete, even though the artwork is available on TMDB.

Thanks for your work, and happy to provide logs or test builds if needed!

@francotosqui commented on GitHub (Oct 3, 2025): Hi, I just wanted to confirm I’m experiencing this issue as well. Backdrops from TMDB that are tagged with “no language” don’t show up in the media item detail view. Instead, they appear only under the “Thumbnail” image area when selecting “All languages”. Posters load fine, but the backdrop slot is always empty. This affects the detail page backgrounds, not the home screen carousels. As a workaround, I can manually upload or use “All languages”, but it would be great if Jellyfin could properly fetch and classify these backdrops. Could this fix be considered for the 10.11.0 milestone? This bug makes a lot of libraries look incomplete, even though the artwork is available on TMDB. Thanks for your work, and happy to provide logs or test builds if needed!
OVERLORD commented 2026-02-07 04:52:56 +03:00
Author
Owner
Copy Link

@crobibero commented on GitHub (Oct 4, 2025):

What movie / tv show are you having this issue with? In my quick test I wasn't getting images under the wrong type

@crobibero commented on GitHub (Oct 4, 2025): What movie / tv show are you having this issue with? In my quick test I wasn't getting images under the wrong type
OVERLORD commented 2026-02-07 04:52:57 +03:00
Author
Owner
Copy Link

@seblu commented on GitHub (Oct 4, 2025):

What movie / tv show are you having this issue with? In my quick test I wasn't getting images under the wrong type

All movies/tv shows.

@seblu commented on GitHub (Oct 4, 2025): > What movie / tv show are you having this issue with? In my quick test I wasn't getting images under the wrong type All movies/tv shows.
OVERLORD commented 2026-02-07 04:52:57 +03:00
Author
Owner
Copy Link

@ValentinDragomir commented on GitHub (Oct 4, 2025):

I have the same issue, so any new movies that I add are not getting any backdrop (blank background instead).

@ValentinDragomir commented on GitHub (Oct 4, 2025): I have the same issue, so any new movies that I add are not getting any backdrop (blank background instead).
OVERLORD commented 2026-02-07 04:52:58 +03:00
Author
Owner
Copy Link

@theguymadmax commented on GitHub (Oct 4, 2025):

This issue has already been resolved and the fix will be included in the upcoming 10.11 release. As there are no further 10.10.x releases planned, users who want Jellyfin to automatically fetch backdrop images are advised to install the TVDB plugin from the plugin catalog.

@theguymadmax commented on GitHub (Oct 4, 2025): This issue has already been resolved and the fix will be included in the upcoming 10.11 release. As there are no further 10.10.x releases planned, users who want Jellyfin to automatically fetch backdrop images are advised to install the TVDB plugin from the plugin catalog.
OVERLORD commented 2026-02-07 04:52:59 +03:00
Author
Owner
Copy Link

@maru801 commented on GitHub (Oct 8, 2025):

Please re-open the issue or stop marking other BRs are dupes. There is still very clearly a bug somewhere.

RC8 was released the Sunday before this past Sunday (September 28, 2025).
The fix for this was merged 3 days ago (October 4, 2025).

Edit: @ultratiem You forgot to remove the thumbs down on this post.

@maru801 commented on GitHub (Oct 8, 2025): > Please re-open the issue or stop marking other BRs are dupes. There is still very clearly a bug somewhere. RC8 was released the Sunday before this past Sunday (September 28, 2025). The fix for this was merged 3 days ago (October 4, 2025). Edit: @ultratiem You forgot to remove the thumbs down on this post.
OVERLORD commented 2026-02-07 04:52:59 +03:00
Author
Owner
Copy Link

@Imgkl commented on GitHub (Oct 8, 2025):

Hey @theguymadmax, Any tentative timeline on the 10.11 release?

@Imgkl commented on GitHub (Oct 8, 2025): Hey @theguymadmax, Any tentative timeline on the 10.11 release?
OVERLORD commented 2026-02-07 04:53:00 +03:00
Author
Owner
Copy Link

@maru801 commented on GitHub (Oct 8, 2025):

Hey @theguymadmax, Any tentative timeline on the 10.11 release?

Probably soon, but no guarantees like all other Jellyfin releases. If more issues are found, more delays will come.

@maru801 commented on GitHub (Oct 8, 2025): > Hey @theguymadmax, Any tentative timeline on the 10.11 release? Probably soon, but no guarantees like all other Jellyfin releases. If more issues are found, more delays will come.
OVERLORD commented 2026-02-07 04:53:00 +03:00
Author
Owner
Copy Link

@seblu commented on GitHub (Oct 8, 2025):

Applying #14941 on top of the 10.10.7 release (Arch Linux package) fix the issue.

@seblu commented on GitHub (Oct 8, 2025): Applying #14941 on top of the 10.10.7 release (Arch Linux package) fix the issue.
OVERLORD commented 2026-02-07 04:53:01 +03:00
Author
Owner
Copy Link

@francotosqui commented on GitHub (Oct 8, 2025):

Applying #14941 on top of the 10.10.7 release (Arch Linux package) fix the issue.

How do I do that?

@francotosqui commented on GitHub (Oct 8, 2025): > Applying [#14941](https://github.com/jellyfin/jellyfin/pull/14941) on top of the 10.10.7 release (Arch Linux package) fix the issue. How do I do that?
OVERLORD commented 2026-02-07 04:53:01 +03:00
Author
Owner
Copy Link

@Imgkl commented on GitHub (Oct 8, 2025):

@seblu You'd think being a developer I would have thought this too, NOPE.

But thanks for the idea.

So @francotosqui or anyone who stumbles upon this issue and can't wait for the fix to land. Here is what I did to fix this issue, it hardly took 10 mins.

  • do brew install dotnet@8
  • Get the 10.10.7 release's zip code.
  • cd into it and find the file called TmdbUtils.cs. It should be under jellyfin-10.10.7/MediaBrowser.Providers/Plugins/Tmdb/TmdbUtils.cs
  • On line 188 replace the existing return statement with this.
return string.Equals(imageLanguage, "xx", StringComparison.OrdinalIgnoreCase)
                ? string.Empty
                : imageLanguage;
  • Now compile this by running
dotnet build MediaBrowser.Providers/MediaBrowser.Providers.csproj -c Release
  • Now you can find the compiled dll in your project in this path.
jellyfin-10.10.7/MediaBrowser.Providers/bin/Release/net8.0/MediaBrowser.Providers.dll
  • That's it. In my case, my jellyfin server is a docker container running on my pi. I had to replace the existing dll with the newly complied dll.
# Copy to your server
scp jellyfin-10.10.7/MediaBrowser.Providers/bin/Release/net8.0/MediaBrowser.Providers.dll user@your-server:~/

# On your server:
# Backup original
sudo docker cp jellyfin:/usr/lib/jellyfin/bin/MediaBrowser.Providers.dll ~/MediaBrowser.Providers.dll.backup

# Apply patch
sudo docker cp ~/MediaBrowser.Providers.dll jellyfin:/usr/lib/jellyfin/bin/MediaBrowser.Providers.dll

# Restart
sudo docker restart jellyfin

Now the backdrops are properly populated. Wouldn't it be funny if the new version just releases a day later? With major releases happening almost every 6 months and the last stable release was in April, 10.11.0 could really drop soon. 😅

@Imgkl commented on GitHub (Oct 8, 2025): @seblu You'd think being a developer I would have thought this too, NOPE. But thanks for the idea. So @francotosqui or anyone who stumbles upon this issue and can't wait for the fix to land. Here is what I did to fix this issue, it hardly took 10 mins. - do `brew install dotnet@8` - Get the [10.10.7](https://github.com/jellyfin/jellyfin/releases/tag/v10.10.7) release's zip code. - cd into it and find the file called `TmdbUtils.cs`. It should be under `jellyfin-10.10.7/MediaBrowser.Providers/Plugins/Tmdb/TmdbUtils.cs` - On line 188 replace the existing return statement with this. ````csharp return string.Equals(imageLanguage, "xx", StringComparison.OrdinalIgnoreCase) ? string.Empty : imageLanguage; ```` - Now compile this by running ```` dotnet build MediaBrowser.Providers/MediaBrowser.Providers.csproj -c Release ```` - Now you can find the compiled dll in your project in this path. ```` jellyfin-10.10.7/MediaBrowser.Providers/bin/Release/net8.0/MediaBrowser.Providers.dll ```` - That's it. In my case, my jellyfin server is a docker container running on my pi. I had to replace the existing dll with the newly complied dll. ```` # Copy to your server scp jellyfin-10.10.7/MediaBrowser.Providers/bin/Release/net8.0/MediaBrowser.Providers.dll user@your-server:~/ # On your server: # Backup original sudo docker cp jellyfin:/usr/lib/jellyfin/bin/MediaBrowser.Providers.dll ~/MediaBrowser.Providers.dll.backup # Apply patch sudo docker cp ~/MediaBrowser.Providers.dll jellyfin:/usr/lib/jellyfin/bin/MediaBrowser.Providers.dll # Restart sudo docker restart jellyfin ```` Now the backdrops are properly populated. Wouldn't it be funny if the new version just releases a day later? With major releases happening almost every 6 months and the last stable release was in April, 10.11.0 could really drop soon. 😅
OVERLORD commented 2026-02-07 04:53:02 +03:00
Author
Owner
Copy Link

@jathek commented on GitHub (Oct 9, 2025):

Here is what I did to fix this issue, it hardly took 10 mins.

A couple of notes for another environment (Windows and official jellyfin container):

  • On Windows, install the .NET 8 SDK with winget install Microsoft.DotNet.SDK.8. After that the build command from above should work.
  • The path for the official Jellyfin container is /jellyfin/MediaBrowser.Providers.dll. The path provided above (/usr/lib/jellyfin/bin/MediaBrowser.Providers.dll) is for the LinuxServer container, I believe.
  • I was able to just mount the file with the below code in docker compose:
  jellyfin:
    volumes:
      - $CONTDIR/jellyfin/MediaBrowser.Providers.dll:/jellyfin/MediaBrowser.Providers.dll

This will survive container restarts, but make sure to remove that volume when you update Jellyfin!

@jathek commented on GitHub (Oct 9, 2025): > Here is what I did to fix this issue, it hardly took 10 mins. A couple of notes for another environment (Windows and official jellyfin container): - On Windows, install the .NET 8 SDK with `winget install Microsoft.DotNet.SDK.8`. After that the build command from above should work. - The path for the official Jellyfin container is `/jellyfin/MediaBrowser.Providers.dll`. The path provided above (`/usr/lib/jellyfin/bin/MediaBrowser.Providers.dll`) is for the LinuxServer container, I believe. - I was able to just mount the file with the below code in docker compose: ```yml jellyfin: volumes: - $CONTDIR/jellyfin/MediaBrowser.Providers.dll:/jellyfin/MediaBrowser.Providers.dll ``` This will survive container restarts, but make sure to remove that volume when you update Jellyfin!
OVERLORD commented 2026-02-07 04:53:02 +03:00
Author
Owner
Copy Link

@joshuaboniface commented on GitHub (Oct 9, 2025):

Unfortunately, there will not be a 10.10.x backport to fix this. While the change seems trivial, our build infrastructure around this is not; we are way past the point where we can reasonably put out another backport for 10.10.x.

I have left comments noting my displeasure on the following TMDB thread: https://www.themoviedb.org/talk/68e6ebdcb6e920b962b7a8dd#68e7c336463b4ecdd35f62c5

There have been changes on the management of images by TMDB.

You have broken your stable, public API and this will affect every user of Jellyfin 10.10.x and earlier (quite literally hundreds of thousands of users by our estimate).

Changes to the applications may be needed.

This is so far from an acceptable response that it is not funny. As a project, we trust your API to be stable, and you have broken that trust. And you expect us to scramble to deploy a fix, in the middle of our work to build a new release, for a change that was done without any consultation to users?

Jellyfin users, I'm sorry but we are unable to "fix" this in 10.10.x or any earlier version; the changes are too extensive and we are too far along in 10.11.0 preparations to backport a fix. Your options are to wait for 10.11.0, or switch to a different metadata provider to obtain images, since this non-response makes it clear that they will not reconsider this decision.

I do apologize, but this is an unacceptable move from TMDB. Unannounced breaking changes to a stable public API are antithetical to the idea of a stable public API. If this had happened 6 months ago, we may have been able to provide a fix, or if we had been consulted at ALL regarding this change, we may have been able to work something out. But we are now in the very final stages of 10.11.0, with all of our build infrastructure updated for the new version, and that makes putting something out very very time consuming and difficult, time we cannot afford to spend on this while still trying to (finally) ship 10.11.0 to users.

The short-term "fixes" are outlined above. My hope would be that TMDB realizes what an unacceptable situation they have now put you - and us - in, and reverts this change, but I will not hold my breath. We suggest adding OMDB to your libraries as a secondary metadata provider for now to obtain images from them.

@joshuaboniface commented on GitHub (Oct 9, 2025): Unfortunately, there will not be a 10.10.x backport to fix this. While the change seems trivial, our build infrastructure around this is not; we are way past the point where we can reasonably put out another backport for 10.10.x. I have left comments noting my displeasure on the following TMDB thread: https://www.themoviedb.org/talk/68e6ebdcb6e920b962b7a8dd#68e7c336463b4ecdd35f62c5 --- > There have been changes on the management of images by TMDB. You have broken your stable, public API and this will affect every user of Jellyfin 10.10.x and earlier (quite literally hundreds of thousands of users by our estimate). > Changes to the applications may be needed. This is so far from an acceptable response that it is not funny. As a project, we trust your API to be stable, and you have broken that trust. And you expect us to scramble to deploy a fix, in the middle of our work to build a new release, for a change that was done without any consultation to users? Jellyfin users, I'm sorry but we are unable to "fix" this in 10.10.x or any earlier version; the changes are too extensive and we are too far along in 10.11.0 preparations to backport a fix. Your options are to wait for 10.11.0, or switch to a different metadata provider to obtain images, since this non-response makes it clear that they will not reconsider this decision. --- I do apologize, but this is an unacceptable move from TMDB. Unannounced breaking changes to a stable public API are antithetical to the idea of a stable public API. If this had happened 6 months ago, we may have been able to provide a fix, or if we had been consulted at ALL regarding this change, we may have been able to work something out. But we are now in the very final stages of 10.11.0, with all of our build infrastructure updated for the new version, and that makes putting something out very very time consuming and difficult, time we cannot afford to spend on this while still trying to (finally) ship 10.11.0 to users. The short-term "fixes" are outlined above. My hope would be that TMDB realizes what an unacceptable situation they have now put you - and us - in, and reverts this change, but I will not hold my breath. We suggest adding OMDB to your libraries as a secondary metadata provider for now to obtain images from them.
OVERLORD commented 2026-02-07 04:53:03 +03:00
Author
Owner
Copy Link

@francotosqui commented on GitHub (Oct 9, 2025):

Unfortunately, there will not be a 10.10.x backport to fix this. While the change seems trivial, our build infrastructure around this is not; we are way past the point where we can reasonably put out another backport for 10.10.x.

I have left comments noting my displeasure on the following TMDB thread: https://www.themoviedb.org/talk/68e6ebdcb6e920b962b7a8dd#68e7c336463b4ecdd35f62c5

There have been changes on the management of images by TMDB.

You have broken your stable, public API and this will affect every user of Jellyfin 10.10.x and earlier (quite literally hundreds of thousands of users by our estimate).

Changes to the applications may be needed.

This is so far from an acceptable response that it is not funny. As a project, we trust your API to be stable, and you have broken that trust. And you expect us to scramble to deploy a fix, in the middle of our work to build a new release, for a change that was done without any consultation to users?

Jellyfin users, I'm sorry but we are unable to "fix" this in 10.10.x or any earlier version; the changes are too extensive and we are too far along in 10.11.0 preparations to backport a fix. Your options are to wait for 10.11.0, or switch to a different metadata provider to obtain images, since this non-response makes it clear that they will not reconsider this decision.

I do apologize, but this is an unacceptable move from TMDB. Unannounced breaking changes to a stable public API are antithetical to the idea of a stable public API. If this had happened 6 months ago, we may have been able to provide a fix, or if we had been consulted at ALL regarding this change, we may have been able to work something out. But we are now in the very final stages of 10.11.0, with all of our build infrastructure updated for the new version, and that makes putting something out very very time consuming and difficult, time we cannot afford to spend on this while still trying to (finally) ship 10.11.0 to users.

The short-term "fixes" are outlined above. My hope would be that TVDB realizes what an unacceptable situation they have now put you - and us - in, and reverts this change, but I will not hold my breath. We suggest adding OMDB to your libraries as a secondary metadata provider for now to obtain images from them.
final release.

No worries — Jellyfin has been one of the best projects I’ve worked with this year. The situation with TMDB was clearly an unannounced change on their part. I’m really looking forward to the official release of version 10.11. Amazing job.

@francotosqui commented on GitHub (Oct 9, 2025): > Unfortunately, there will not be a 10.10.x backport to fix this. While the change seems trivial, our build infrastructure around this is not; we are way past the point where we can reasonably put out another backport for 10.10.x. > > I have left comments noting my displeasure on the following TMDB thread: https://www.themoviedb.org/talk/68e6ebdcb6e920b962b7a8dd#68e7c336463b4ecdd35f62c5 > > > There have been changes on the management of images by TMDB. > > You have broken your stable, public API and this will affect every user of Jellyfin 10.10.x and earlier (quite literally hundreds of thousands of users by our estimate). > > > Changes to the applications may be needed. > > This is so far from an acceptable response that it is not funny. As a project, we trust your API to be stable, and you have broken that trust. And you expect us to scramble to deploy a fix, in the middle of our work to build a new release, for a change that was done without any consultation to users? > > Jellyfin users, I'm sorry but we are unable to "fix" this in 10.10.x or any earlier version; the changes are too extensive and we are too far along in 10.11.0 preparations to backport a fix. Your options are to wait for 10.11.0, or switch to a different metadata provider to obtain images, since this non-response makes it clear that they will not reconsider this decision. > > I do apologize, but this is an unacceptable move from TMDB. Unannounced breaking changes to a stable public API are antithetical to the idea of a stable public API. If this had happened 6 months ago, we may have been able to provide a fix, or if we had been consulted at ALL regarding this change, we may have been able to work something out. But we are now in the very final stages of 10.11.0, with all of our build infrastructure updated for the new version, and that makes putting something out very very time consuming and difficult, time we cannot afford to spend on this while still trying to (finally) ship 10.11.0 to users. > > The short-term "fixes" are outlined above. My hope would be that TVDB realizes what an unacceptable situation they have now put you - and us - in, and reverts this change, but I will not hold my breath. We suggest adding OMDB to your libraries as a secondary metadata provider for now to obtain images from them. final release. No worries — Jellyfin has been one of the best projects I’ve worked with this year. The situation with TMDB was clearly an unannounced change on their part. I’m really looking forward to the official release of version 10.11. Amazing job.
OVERLORD commented 2026-02-07 04:53:04 +03:00
Author
Owner
Copy Link

@joshuaboniface commented on GitHub (Oct 9, 2025):

As confirmed by Travis in the above thread - this was actually an unintentional bug (and affected Kodi too). A fix should be pushed out later today.

@joshuaboniface commented on GitHub (Oct 9, 2025): As confirmed by Travis in the above thread - this was actually an unintentional bug (and affected Kodi too). A fix should be pushed out later today.
OVERLORD commented 2026-02-07 04:53:04 +03:00
Author
Owner
Copy Link

@francotosqui commented on GitHub (Oct 9, 2025):

As confirmed by Travis in the above thread - this was actually an unintentional bug (and affected Kodi too). A fix should be pushed out later today.

Is it a TMDB fix? So we don't need to do anything, just wait?

@francotosqui commented on GitHub (Oct 9, 2025): > As confirmed by Travis in the above thread - this was actually an unintentional bug (and affected Kodi too). A fix should be pushed out later today. Is it a TMDB fix? So we don't need to do anything, just wait?
OVERLORD commented 2026-02-07 04:53:04 +03:00
Author
Owner
Copy Link

@nielsvanvelzen commented on GitHub (Oct 9, 2025):

The fix is on the side of TMDB. It can take up to 8 hours after their fix is deployed before everything is working correctly again, according to their message.
There is no need to update Jellyfin or change any configuration in Jellyfin.

@nielsvanvelzen commented on GitHub (Oct 9, 2025): The fix is on the side of TMDB. It can take up to 8 hours after their fix is deployed before everything is working correctly again, according to their message. There is no need to update Jellyfin or change any configuration in Jellyfin.
OVERLORD commented 2026-02-07 04:53:05 +03:00
Author
Owner
Copy Link

@Retr0Jay commented on GitHub (Oct 10, 2025):

Backdrop scrapping Seems to be working again now, well at least for me it is anyways😃

@Retr0Jay commented on GitHub (Oct 10, 2025): Backdrop scrapping Seems to be working again now, well at least for me it is anyways😃
OVERLORD commented 2026-02-07 04:53:06 +03:00
Author
Owner
Copy Link

@RickStrife commented on GitHub (Oct 10, 2025):

Hello, I know it seems like there's an obvious answer for this question, but since a fix from the Jellyfin side was already underway, I suppose it is no longer necessary, right? So when 10.11 hits, it will not affect what TMDB already corrected.

@RickStrife commented on GitHub (Oct 10, 2025): Hello, I know it seems like there's an obvious answer for this question, but since a fix from the Jellyfin side was already underway, I suppose it is no longer necessary, right? So when 10.11 hits, it will not affect what TMDB already corrected.
OVERLORD commented 2026-02-07 04:53:06 +03:00
Author
Owner
Copy Link

@crobibero commented on GitHub (Oct 10, 2025):

The change within Jellyfin isn't needed but we will just keep it in place as "xx" isn't a valid language.

@crobibero commented on GitHub (Oct 10, 2025): The change within Jellyfin isn't needed but we will just keep it in place as "xx" isn't a valid language.
OVERLORD commented 2026-02-07 04:53:07 +03:00
Author
Owner
Copy Link

@PANICBUTT0N commented on GitHub (Oct 10, 2025):

It appears to be working for me as well now.

@PANICBUTT0N commented on GitHub (Oct 10, 2025): It appears to be working for me as well now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label bug confirmed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#7381
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?