-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug(jellyfin): network paths not resolved correctly #132
Comments
Can you post your config? |
I just changed the rewrite section to what you see in the config now. I "think" it may be working because i now see a couple "completed" items on the webui. |
Your rewrite should be from where the file is before it moves to the folder where jellyfin will see it. So if a TV show is in |
oh ok, so in my case it starts off in /media/Media/Downloads/Torrents/sonarr-tv. So that would go in the top one. got ya. |
Yes, for example mine is |
ok, so i put /media/Media/Downloads/Torrents/sonarr-tv into the config and it is giving the error again. I think i understand what is going on now. It has to do with how ive got the share mounted in my jellyfin container. on the ubuntu server it self the path is /media/Media/Downloads/Torrents/sonarr-tv. but that path isnt available to the container because i have the video folder mounted directly. Or does it have to do with the path that sonarr sees? |
Can you join the discord? and I can try my best to help https://discord.gg/fYvSNCHx |
Description of the bug
After you helped me earlier to get the trigger setup I am seeing the following error ERROR autopulse::service::targets::emby: unable to find library for file: /media/Media/Video/TV/Regular/show/episode.mkv
sorry to keep bothering you.
Steps To Reproduce
add new download to sonarr and let it finish.
Additional Information
No response
The text was updated successfully, but these errors were encountered: