Jellyfin Unable to Access Media Files Through Symlinks Created by Riven

[bioengineered]

I’m currently experiencing an issue where Jellyfin is unable to read media files via symlinks created by Riven, even though it can access the same media files just fine through the direct Zurg (/mnt/zurg/movies) path. Here are the specifics of the setup and the issue:

Setup:

Jellyfin and Plex are both set up to point to the same library location.

Jellyfin is running in a Docker container.

Plex has no issue accessing media through the symlinked paths, but Jellyfin consistently throws errors.

Error in Jellyfin logs:
[ERR] Emby.Server.Implementations.IO.ManagedFileSystem: Reading the file size of the symlink at /movies/Interstellar (2014) failed. Marking the file as not existing.

Link to full Jellyfin log: https://pastebin.com/EQ8xCHvz

[mrichana]

Try "docker restart jellyfin" after zurg and rclone have started and see if it is a timing problem as it usually is.

[langerdennis]

Seems more like Jellyfin cannot find the path the symlink is pointing to - depending on how you setup the paths within riven, the symlink might not link to the full /mnt/zurg/movies movies path but to the path the file has within the riven container (assuming you are using Docker). Best is to check where the symlinks are linking to with ls -l in a respective folder and making sure Jellyfin can access the file under that exact path.

[machetie]

Consolidating symlink and media access issues:

Related issues:

• ERROR on symlink.run #823 - ERROR on symlink.run
• Queue plex.run update scans for new files. #873 - Queue plex.run update scans

These issues all relate to symlink creation and media server access. Will track all symlink-related improvements here.

[wolfemir]

@bioengineered looks like this is a permission/volume binding issue on your compose to me, were you able to sort it out?