Plugin catalog empty 10.10.3

[Krosis]

Hello everyone,

I am having a small problem with Jellyfin and would apprechiate some advice.

I have Jellyfin 10.10.3 installed on a N100 MiniPC running CasaOS v0.4.15 on Debian 12. I only changed the installation settings to include an external harddrive with movies on it.

My problem is that Jellyfin does not pull any metadata for the movies. I went to check if a plugin needed to be updated/installed but the catalog is not showing any results or is loading indefinitly. I have seen in a previous post (https://forum.jellyfin.org/t-jellyfin-10...-catalogue) that this issus might be due to DNS error, which boils down to Jellyfin not beeing able to establish a connection to the internet?

I am also running a Pihole to block advertisement in the network but cant see any blocking of Jellyfin stuff. Are there any domains I need to whitlist?

I have tried the solution from the thread above (changing the network_mode from bridge to host in the drop down menu of CasaOs custom installation) but then I can not acces Jellyfin anymore.

Thanks in advance and have a nice day.

[crobibero]

Please include server logs when it tries to reach the plugin repo

[Krosis]

Here is a Pastebin of the logfile https://pastebin.com/dDpz2Dpt

[TheDreadPirate]

Looks like your server isn't able to access TMDB either.

Code:

[2024-12-26 03:00:57.400 +01:00] [ERR] [110] MediaBrowser.Providers.Movies.MovieMetadataService: Error in "TheMovieDb"
System.Net.Http.HttpRequestException: Resource temporarily unavailable (api.themoviedb.org:443)
....
[2024-12-26 10:05:34.229 +01:00] [ERR] [85] Emby.Server.Implementations.Updates.InstallationManager: An error occurred while accessing the plugin manifest: "https://repo.jellyfin.org/files/plugin/manifest.json"
System.Net.Http.HttpRequestException: Resource temporarily unavailable (repo.jellyfin.org:443)

I noticed that there are IPv6 addresses in the log. Do you have IPv6 enabled in Jellyfin?

[Krosis]

I have enabled IPv6 and IPv4 in the networking section if thats what you mean.

[TheDreadPirate]

Make sure that every step in the chain from the host to the container supports IPv6. OR go the opposite direction and disable IPv6.

Another thing we can do is see how your host and container are resolving addresses. Run this command on the host and container command line and share the output.

Code:

curl -vvv https://image.tmdb.org/t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg -o /tmp/futurama.jpg

[Krosis]

I am guessing the host command line is the terminal of CasaOs. Here is the output in a Pastebin: https://pastebin.com/7YHSS4P2

For the container command line I use the terminal in the settings menu of the Jellyfin installation. Here is the output: https://pastebin.com/HREpUdFe

[TheDreadPirate]

So the host is getting IPv6 addresses when resolving a hostname. But the container can't resolve anything at all. Even if IPv6 wasn't supported by the container it should still get SOMETHING when it tries to resolve an address. This tells me something with your pihole or your container config isn't quite right.

Are there any allow lists on the pihole that would block devices not on the approved list?