Skip to content
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

Open
n4tur3502 opened this issue Dec 12, 2024 · 7 comments
Open

bug(jellyfin): network paths not resolved correctly #132

n4tur3502 opened this issue Dec 12, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@n4tur3502
Copy link

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

@n4tur3502 n4tur3502 added the bug Something isn't working label Dec 12, 2024
@lukeeexd
Copy link

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

Can you post your config?

@n4tur3502
Copy link
Author

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.
https://pastebin.com/QRXnUtVL

@lukeeexd
Copy link

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 /media/Media/Video/TV/Regular before it moves to /media/TV/Regular and jellyfin reads TV shows from /media/TV/Regular then that's correct

@n4tur3502
Copy link
Author

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.

@lukeeexd
Copy link

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 /volume1/data/torrents/tv and from there it goes to /volume1/data/media/tv

@n4tur3502
Copy link
Author

n4tur3502 commented Dec 12, 2024

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?

@lukeeexd
Copy link

Can you join the discord? and I can try my best to help https://discord.gg/fYvSNCHx

@dan-online dan-online changed the title bug: cant find jellyfin paths bug: smb/nfs paths not found Dec 13, 2024
@dan-online dan-online changed the title bug: smb/nfs paths not found bug(jellyfin): smb/nfs paths not found Dec 15, 2024
@dan-online dan-online changed the title bug(jellyfin): smb/nfs paths not found bug(jellyfin): network paths not resolved correctly Dec 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants