Getting chmod errors in TN scale filebrowser app

Hi all,

I have an issue with trying to move files between data shares between two pools. I’m trying to use filebrowser to move files in between them but get a 403 error.

After looking at the app logs I get this

2025-02-19 00:37:58.035873+00:002025/02/19 00:37:58 /hdd_mirror_samba/something.tt: 403 192.168.1.81 chmod /data/ssd_samba/something.tt: operation not permitted
2025-02-23 16:23:20.845794+00:002025/02/23 16:23:20 /api/renew: 401 192.168.1.81 <nil>
2025-02-23 16:23:20.868684+00:002025/02/23 16:23:20 /api/renew: 401 192.168.1.81 <nil>
2025-02-23 16:24:46.859435+00:002025/02/23 16:24:46 /ssd_samba/something.tt: 403 192.168.1.81 chmod /data/hdd_mirror_samba/something.tt: operation not permitted

I would assume that it has something to do with acl permissions but I’m not sure how to fix it.

Any help/feedback would be appreciated - if there is a better way or more proper way of doing it pls lmk.

Thanks!

You might want to look into ACL modes. When a docker container / app wants to chmod something in an dataset generally it won’t work without being set to passthrough. You can find the setting under the “advanced options” when editing a dataset.

1 Like

Do note that getting these errors may be an indication that the app is insufficiently ACL-aware and will probably break permissions in subtle ways.

Had that same “not permitted” error when I tried to use Filebrowser on a 3 year old dataset/SMB share even though I changed its permissions by adding apps as a user with full control recursively. I could acess the old SMB share but not acess/copy its files or sub folders. Eventually, I solved it by making a new SMB share/dataset with all the correct permissions, apps as a user, and copied the old data into the new share.

What kind of permissions are ideal for an smb share in a case like this?