The mkdir in the setup steps has a quoting bug that silently creates the folders somewhere other than where the container expects. I think it explains the recurring "/srv/users: no such file or directory" reports in this thread.

The instructions say:

mkdir -p /mnt/user/FileBrowser Files/users

chown -R 1000:100 /mnt/user/FileBrowser Files/users

The share name contains a space and the path isn't quoted, so mkdir receives two arguments instead of one. It creates:

/mnt/user/FileBrowser (empty)
Files/users - relative to whatever directory you're currently in

...and never creates /mnt/user/FileBrowser Files/users, which is what /srv/users actually maps to. mkdir -p exits 0, so nothing appears to go wrong. In my case the second directory landed in /mnt/user/appdata/filebrowserQuantum/Files/users because that's where I happened to be cd'd to, and the chown -R followed it there.

The result after logging in is a 404, and this in the container log:

[ERROR] Failed to open root directory: open /srv/users: no such file or directory

[ERROR] could not update user: MakeUserDirs: scope folder does not exist: /srv/users

GET | 404 | admin | "/api/resources?path=%2F&source=My Files"

The fix is just quoting:

mkdir -p "/mnt/user/FileBrowser Files/users"

chown -R 1000:100 "/mnt/user/FileBrowser Files/users"

Worth clarifying that the share name is not the problem. A few people have suggested renaming the share to FileBrowser or FileBrowserFiles. That does work, but only because it sidesteps the unquoted argument. Mine is still named "FileBrowser Files" and works fine now that the directory exists.

Extra warning for anyone on a ZFS pool: the stray/mnt/user/FileBrowser isn't just an empty folder. Unraid provisions a ZFS dataset for a new directory at the pool root, so you end up with a phantom cache/FileBrowser dataset and an empty share in the UI. Clearing it needs zfs destroy cache/FileBrowser, and in my case that failed with "dataset is busy" until I restarted two unrelated containers that had inherited the mount into their own mount namespace at startup.

If you're already affected, to recover:

mkdir -p "/mnt/user/FileBrowser Files/users"

chown -R 1000:100 "/mnt/user/FileBrowser Files/users"

docker restart FileBrowserQuantum

Then clean up the two strays: /mnt/user/FileBrowser, and Files/users under whichever directory you originally ran the command from.

Could the Requires text in the template be updated to quote both paths? It would save the next person the same hunt.

39 minutes ago, cliffdog510 said:

Could the Requires text in the template be updated to quote both paths? It would save the next person the same hunt.

Yep, you right sorry for this I will fix it