![]() |
Jellyfin indexing library paths that are not mapped anymore - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: Jellyfin indexing library paths that are not mapped anymore (/t-jellyfin-indexing-library-paths-that-are-not-mapped-anymore) |
Jellyfin indexing library paths that are not mapped anymore - vitalessandro - 2025-05-15 Hey everybody I have a weird issue with my Jellyfin instance. I've installed jellysearch on my server to get better search results. Due to jellysearch not being able to discern library permissions, and most of my users not supporting 4K playback, I disabled all 4K libraries and removed all the library paths of the 4K libraries. However, jellysearch still provides 4K content with its search results - and weirdly enough, every user, no matter the library permissions, can play them. How does Jellyfin (running in docker) still index those files somehow, even if the directory paths of those files should not be scanned by the app? RE: Jellyfin indexing library paths that are not mapped anymore - vitalessandro - 2025-05-19 I've been able to circumvent this issue by adding a new path to the 4K libraries with an empty directory. Seems just adding any directory path fixes the issue and removes the previous files |