Without custom configuration using a local user with group ftp, I was able to navigate the home directory and create a file.

scameras isn’t a group, it’s the name of the AD user that nominally owns and creates the camera uploads

However, reinterpreting the idea, I have adjusted the DefaultRoot line to make the local ftp user’s root in accordance, and this does work as expected:

I suppose this is an acceptable workaround for this instance, as the ACLs on this folder still allow domain users to read and modify the folders/files created this way, but it’s still in no way actually addressing the underlying issue: authentication is not working.

Make sure your datasets are healthy.

Start with a simple configuration with a local user.

Temporarily remove the optional configuration. Create a new local user with a home directory and include ftp as an auxiliary group. Add some data to the new users home directory.

From a Linux client or other FTP client, via FTP login to the server as that user. List the contents of the home directory.

If that works, then log out and add the scameras group to the local user and add the DefaultRoot /mnt/internal/DISK1/Security scameras to Auxiliary Parameters.

Login to FTP with the local FTP user. The user should be able to list the contents of /mnt/internal/DISK1/Security.

Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.

https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153