2024-12-31, 09:31 AM
(This post was last modified: 2024-12-31, 09:33 AM by Rudra Patel. Edited 1 time in total.)
I have also encountered a similar issue.
The issue I encountered was that Jellyfin only displayed one movie without any metadata, even though all the movies were visible in the Metadata Manager. But in my case I have a dual-boot pc with Windows-11 and EndeavourOS and I was able to run Jellyfin on Windows-11 easily without any issues. When trying to run Jellyfin on EndeavourOS it did not work. So, here is the solution.
I found a solution while working on a project involving the use of the TMDB API to fetch data. When I sent the API request using a browser, I received a response without any issues. However, when using cURL to make the same API query, I didn't get any response.
The root of the issue turned out to be DNS configuration. My browser's DNS was set to 1.1.1.1 Cloudflare DNS, while my computer was using my ISP's default DNS (JIO). After some investigation, I discovered that JIO blocks certain parts of TMDB.
Since Jellyfin relies on TMDB to fetch metadata, fixing the issue with TMDB API requests resolved the problem. I also tested using a VPN, which worked as an alternative solution.
For anyone facing a similar problem, I suggest testing the TMDB API using cURL. Follow the instructions in the TMDB API authentication guide. If you don’t get a response, it likely means there is an issue with your network—most likely your ISP is blocking TMDB. To resolve this, try changing your DNS settings to a service like Cloudflare (1.1.1.1) or Google DNS (8.8.8.8), or use a VPN to bypass the restriction.
I hope this post might help people who have similar issues.
The issue I encountered was that Jellyfin only displayed one movie without any metadata, even though all the movies were visible in the Metadata Manager. But in my case I have a dual-boot pc with Windows-11 and EndeavourOS and I was able to run Jellyfin on Windows-11 easily without any issues. When trying to run Jellyfin on EndeavourOS it did not work. So, here is the solution.
I found a solution while working on a project involving the use of the TMDB API to fetch data. When I sent the API request using a browser, I received a response without any issues. However, when using cURL to make the same API query, I didn't get any response.
The root of the issue turned out to be DNS configuration. My browser's DNS was set to 1.1.1.1 Cloudflare DNS, while my computer was using my ISP's default DNS (JIO). After some investigation, I discovered that JIO blocks certain parts of TMDB.
Since Jellyfin relies on TMDB to fetch metadata, fixing the issue with TMDB API requests resolved the problem. I also tested using a VPN, which worked as an alternative solution.
For anyone facing a similar problem, I suggest testing the TMDB API using cURL. Follow the instructions in the TMDB API authentication guide. If you don’t get a response, it likely means there is an issue with your network—most likely your ISP is blocking TMDB. To resolve this, try changing your DNS settings to a service like Cloudflare (1.1.1.1) or Google DNS (8.8.8.8), or use a VPN to bypass the restriction.
I hope this post might help people who have similar issues.