Jellyfin only showing a single movie

[TheDreadPirate]

Can you share examples of your folder and file names? And share your logs via pastebin.

[mohit kumar]

I am getting the same issue. Basically it only shows one movie. But if I go via search, then the movie is shown. But if 2 movies share the same prefix, again only one movie is shown.

[TheDreadPirate]

Just like the other posters that asked and never provided more info, we need more info.

OS, virtualization, file organization examples, library type, logs.

[keithf]

EDITED AS RESOLVED - I DISABLED IPV6 ON THE HOST AND EVERYTHING SUDDENLY WORKED AND DISPLAYED ALL LIBRARY DATA SEEN IN MEDADATA.

Seeing same issue here on a new Jellyfin install.

My original Jellyfin install was a bare-metal install of Debian 12, with internal storage, it was easy to set up, and worked fine.

I then set up a new server (to reduce power usage) which runs VirtualBox on Windows 11. I created a new VirtualBox VM for Jellyfin, installed Debian 12, attached a portable USB hard drive to the server, mounted the storage in the Debian VM (using mount --bind), and the movie/show files are all visible as you'd expect in Debian.

When I add anything into the Jellyfin library it simply shows the first media file alphabetically. You can watch the file. All other files in the same directory have been "found" when the library is updated, and can be found in metadata like the first poster in this discussion showed.

So unclear on why the library doesn't show anything but that first media file when the metadata looks complete.

Happy to provide whatever data is needed to help myself and the others in this thread who are having the same issue.

[Rory235]

I have just downloaded and installed Jellyfin on my windows PC, and am having the same issue. I think my files follow the naming convention and the I have disabled IPv6 in the dashboard but I still on see one file (i can see the rest in the metadata) Very new to all of this so any suggestions to someone who doesnt really know what they are dfoing would be great!

[TheDreadPirate]

Can you share your file and folder naming? And what library type the files are in for each example.

If IPv6 is properly setup on the host, you could enable IPv6 in Jellyfin. It does support IPv6 (my setup works with IPv6).

[Tedus]

Hi all, I have installed on my Synology (as they have killed Video Station) and I am having the same issue. Can someone give some suggestions for what to try?

Is there a tool to use to fix folder and file naming? Video Station seemed to handle the files fine.

[Rory235]

So I fixed it by delting my server and creating a new one with the media type set to "movies and programs" I can see all the files and play them now

[TheDreadPirate]

Hi all, I have installed on my Synology (as they have killed Video Station) and I am having the same issue. Can someone give some suggestions for what to try?

Is there a tool to use to fix folder and file naming? Video Station seemed to handle the files fine.

Tiny Media Manager is a great tool for reorganizing your media in a Jellyfin compliant way.

[Rudra Patel]

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.