Populating media files - Printable Version

Populating media files - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions)
+--- Thread: Populating media files (/t-populating-media-files)

Pages: 1 2

RE: Populating media files - VulcanRidr - 2024-11-20

[*]

(2024-11-20, 03:33 PM)TheDreadPirate Wrote: I mean what is the TEXT output of the command in the terminal. I know what the image is. I just use it for testing whether your host can reach TMDB's API or media servers. Did you run that command from the host? Or did you run it in the jail for Jellyfin?

Okay, I apologize. I ran it from the jail. I pasted the entire thing into https://pastebin.com/DtXn3i2j

I'm guessing you don't need the binary data, but out of an abundance of caution... Grinning-face

RE: Populating media files - TheDreadPirate - 2024-11-20

The host is resolving IPv6 addresses for TMDB.

Code:
15:41:02.312512 [0-0] == Info: IPv6: 2400:52e0:1a00::1067:1

You have IPv6 enabled to some degree. At least from your DNS provider. I'm not familiar with the differences between jails and docker container/LXC's. But in Docker/LXCs, I've seen similar situations as this where Jellyfin's container is not setup for IPv6, or Jellyfin itself is not configured to allow IPv6.

For some users they either enabled IPv6 in Jellyfin, if their host interface had an IPv6 address, or took additional steps to prevent IPv6 DNS resolution.

RE: Populating media files - VulcanRidr - 2024-11-25

(2024-11-20, 09:36 PM)TheDreadPirate Wrote: The host is resolving IPv6 addresses for TMDB.

Code:
15:41:02.312512 [0-0] == Info: IPv6: 2400:52e0:1a00::1067:1

You have IPv6 enabled to some degree. At least from your DNS provider. I'm not familiar with the differences between jails and docker container/LXC's. But in Docker/LXCs, I've seen similar situations as this where Jellyfin's container is not setup for IPv6, or Jellyfin itself is not configured to allow IPv6.

Okay, First of all, and I am not sure how long you have been doing linux...But if you remember OpenVZ or maybe linux-vserver, they were both based on FreeBSD jails.

In any case, I have gone in and (hopefully) killed ipv6 in the interface. I added

Code:
plugin query "filter-aaaa.so" {

           filter-aaaa-on-v4 yes;

           };

in my named.conf files and restarted bind9...So in theory, it should not be receiving AAAA, and then I restarted the jail and jellyfin. However, I am still getting the same behavior from the interface, in that I will get one mnew movie added to the interface, and I have to start it, and (usually) then I reload the UI, and maybe will get another move. Right now, I have a total of 25 movies out of just north of 350. And my Shows, I have one episode, and when I click on it, I get

Code:
Playback Error

Unable to find a valid media source to play.

Quote:For some users they either enabled IPv6 in Jellyfin, if their host interface had an IPv6 address, or took additional steps to prevent IPv6 DNS resolution.

Hopefully this is fixed. Should at least the existing movies start getting posters instead of random screenshots of from the movies?