New files permission

I use jellyfin server on a pi 4 with ubuntu 20.04.
My data are on a hdd ext 4.
I use coreelec as a client to see movies.

No problem to access libraries.
I have a samba share to copy files from my pc win 10 to the hdd on the pi 4.

When i copy a file, i have a permission denied to read this new movie added in the library.

Do you have any solution?

Hi Ronan,

I have a similar setup, Debian server for Jellyfin, Samba share to access the files on the server and Jellyfin, running smooth without problems. All the files copied via Samba are owned by the Samba user, Jellyfin is able to play anything from this user without problems.

What settings do you have in Samba smb.conf ?
My Samba “Share” folder is setup as:

    path = /var/share
    available = yes
    force user = arnaud
    read only = no
    browsable = yes
    public = yes
    writable = yes

thanks for your answer
this is my smb.conf

comment = nas
path = /mnt/maxtor
valid users = ubuntu,jellyfin
force group = ubuntu
create mask = 0660
directory mask = 0771
read only = no
browseable = yes

i have to use this
sudo setfacl -R -m u:jellyfin:rx /mnt/maxtor/
to be able to read file.

when i copy the file, with ls -l i can see the file in purple, and when i use setfacl, the file goes green…

ok maybe something here, i don’t have heritage with this so i will try
sudo setfacl -Rm d:u:jellyfin:rx /mnt/maxtor/

Hi Ronan,

Updated: I have corrected the information below

I will say the issue come from your create mask.
Try changing create mask value to 0664 instead of 0660, that will apply to all new files you are copying. I believe Jellyfin needs to read the file so 0664 should allow your Jellyfin user to only read the file (as well as all other users on that Ubuntu machine), if you need any user able to read & execute change the 4 to 5 (so, 0665).

Just try changing this in your smb.conf and restart samba services to apply.
Then try copy a new file from your windows PC to your samba share and check if Jellyfin can play it.

Note that will not change permissions for any existing files, those will have to be updated manually as you already did.

ok thanks, it seems far better…
i also changed acl for write permission group with
sudo setfacl -Rm g::rwx /mnt/maxtor
but it seems working. Happy!