Emby admin user has no access to shared folder

[JPgruenewald 8]

Hi everyone,

I encounter some access problems when I want to connect to the shared folder "DB" of my media database.

The "DB"-folder is the root node of my shared folder (= shared folder).
Now I want to access this folder during the setup of a new music database using the emby web interface.
The shared folder permissions are set for the admin-group to RW, the default QNAP admin user is disabled (I created a new user, this user is also part of the admin-group). 
In the GUI for user and user group management there is no "emby"-user existing. 

Now finally my question: How can I tell emby which user to use to access shared folders?

Access to public folders is given. My setup info is shown below.

Thanks in advance, regards
JP

-------------------------
QNAP TS-673A with QNAP QuTS Hero h5.0.0.2069
emby-server-qnap_4.7.6.0_x86_64.qpkg

Edited August 12, 2022 by JPgruenewald

[Luke 37099]

Hi, I've passed this onto our QNAP packaging developer to review and comment on. 

@PenkethBoy may also have some QNAP permissions tips. Thanks.

[alucryd 216]

I have mine set to read-only for everyone, does that work for you?

[JPgruenewald 8]

Hi @alucryd,

first of all thank for your help. This setting works for me because my public shared folders do have this setting too. The main issue here is, that I don't want to give every user of my NAS access to the whole media folder just to give emby the ability to access it. What I expect is that there should exists an 'emby-system-admin' user for which I can setup the access to the media folder explicitly.

W. r. t. this (click me) thread there is an "emby" user existing on a Synology NAS?
 

Of course, maybe it's possible to grant access for the "everybody" user group and then doing some blacklisting to block all other users again (to overwrite the access settings again). But this is not convenient at all. Especially when the media data is stored in a folder that is located in some other (family)member's private space.

[alucryd 216]

Unlike Synology, Qnap doesn't support running as another user natively, and doing so manually was a lot of trouble back when we first produced the package because the OS was lacking essential tools to do so. Maybe it's changed today but historically the server has been running as admin because of that. Not sure what user it uses when the default admin user is disabled though, if you can check that. Maybe you don't even need to be read-only for everyone if it's running as your admin user.

[JPgruenewald 8]

My analysis result is, that when your default admin user was disabled the fallback user is the guest user account. In the following mockup the shared folder is "TestShare" and the "Database" folder contains the media files. Moreover, the admin user was replaced by "MyAdmin" that is part of the "administrators" user group.

The settings that do not work look like this

 

The settings that work look like this

 

 

Then the path is found in the web interface as follows:

 

[JPgruenewald 8]

Even after enabling the default admin again there is no access. 

Here are the permission settings:

 

[alucryd 216]

Thanks for the analysis, I'll revisit that next time I start the qnap. But if we do move to a dedicated user, we're bound to break quite a few installations so I'm not sure it's a smart move for us at this point, will have to discuss it internally.

[JPgruenewald 8]

Thank you @alucryd for your openness to this topic. I think a dedicated user would be a better solution. I understand that this is not easy and above all not immediately realizable. I would be very happy if you would keep me informed about the internal decision. If I can support you somehow (e.g. as a beta tester) I can do that with pleasure.

[JPgruenewald 8]

I would like to inform you that unfortunately I cancelled my Premiere subscription today. I still hope that you will fix the issue with access rights or user rights in the near future so that I can switch back to emby. Please give me feedback via this thread as soon as you have news about this. Thanks a lot and hope to hear you soon!

[Luke 37099]

I notice you setup your library using a UNC network path, e.g. \\ip\testshare\database

This will make things much more complicated. Why not just setup the library using the direct local path? I suspect that will resolve your issue.

[JPgruenewald 8]

Ahhhh now it's working! Thanks for helping me @Luke and @alucryd 

Edited September 3, 2022 by JPgruenewald

[Luke 37099]

Thanks for the feedback.