I installed Jellyfin on MEDIA, set it's service to run as the service account, started it up, went through the wizard, got stuck at trying to add the path to my content on STORAGE. I made sure that MEDIA can reach the files on STORAGE. I created a service account on both with the same username/password. I have a storage server with all my content on Windows Server 2019 Core ("STORAGE"), and a media server on Windows Server 2019 (non-core) ("MEDIA"), non-domain. Hello - just wanted to add to this (apologies if its not the correct place, new to jellyfin, github, etc): The account automatically is granted the log on as a service right when adding it in step 3, so it must be something else. Right now the service throws an error 143 in the event log. Now I only have to figure out what rights the service accounts needs so that it doesn't need to run as a local admin user. And you must use UNC path, not mapped drives. When adding a library in Jellyfin, only use the Folder option, NOT the shared network folder.Change the log on as to the account you created in step 2. In Windows, open Services, and locate the Jellyfin Server service.For now this user must also be a member of the local Adminsitrators group for this configuration to work! :( Regardless of options during the installation of Jellyfin, in Windows create a user account with the same account name and password as you did on the NAS (so JellyMedia).If you don't have a dedicated (non-admin) user to access your media shares, then create one on your NAS and give it the correct permissions.I just installed a new Windows Server 2022 VM, and was struggling with this same issue. (It's guest access in the samba config) That should work, although I'm not 100% on can you perhaps give a tutorial on how to achieve this? I tried net use but I don't think I'm doing it right. I suppose the other option is to do full public samba shares, but that is very insecure. Then Jellyfin should be able to enumerate the shares. Your best bet is to create a new user that is named (for example Jellyfin) and use the net use and runas commands to give that user the credentials to the share. So outside a domain the target host has no idea about the client host and can't give it access. Since they identify themselves as the computer account on the network. ![]() Network Service (and Local System) for that matter can only access network shares or mounted drives in a Windows Domain environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |