"Not allowed because you don't have permissions to create subfolders in that folder"

[jcklpe]

Installed client on Windows machine. Synced my "Documents" folder no issue. Documents folder is on my Ubuntu stored as one of the internal data path folders.

I try to sync my empty "Work" folder which is mounted as an external folder on the desktop. I create a test folder on my Windows machine and I get this error message.

Also I have mounted my files to my laptop via webdav. When I open up Work and try to create a test folder I get this response:

When I got to any of the other folders though that I can acess through this mount, Media, Resources, etc, and create a folder, I have zero problems.

Server configuration

Operating system: Ubuntu 18

Web server: Nginx

Database: MySql

PHP version: 7.2

Nextcloud version: 13

Updated from an older Nextcloud/ownCloud or fresh install: Fresh

Where did you install Nextcloud from:

Client configuration

Browser: Firefox

Operating system: Windows 10

Logs

Web server error log

8/10/2018 9:27:27 PM, test, Work,Not allowed because you don't have permission to add subfolders to that folder
8/10/2018 9:27:27 PM, Testfolder, Work,Not allowed because you don't have permission to add subfolders to that folder
8/10/2018 9:10:37 PM, test, Work,Not allowed because you don't have permission to add subfolders to that folder
8/10/2018 9:10:19 PM, desktop.ini, Documents,File is listed on the ignore list.
8/10/2018 9:10:19 PM, My Videos, Documents,Directory not accessible on client, permission denied.
8/10/2018 9:10:19 PM, My Pictures, Documents,Directory not accessible on client, permission denied.
8/10/2018 9:10:19 PM, My Music, Documents,Directory not accessible on client, permission denied.

[nextcloud-bot]

GitMate.io thinks possibly related issues are #6350 (does not allow me to create users), #7588 (Folder permissions), #1357 (Allow create but not view when sharing), #5312 (Skeleton should not create files in shared folder), and #708 (Some sub-Folders on SMB/CIFS External Storage are read only. (You don't have permissions to upload or create files here.)).

[jcklpe]

I have mostly managed to fix this issue by changing the umask for www-data user and adding them to the david user group. NextCloud can now save new folders. New folders however created in Nautilus can't be edited however. I have tried to change the default umask for Nautilus through many different guides and have not been able to.

[tflidd]

I looks for me like a configuration problem. Check your permissions, especially the group rights (chmod 660 for files and chmod 770 for folders). Such configuration stuff is better handled on the forum: help.nextcloud.com

[jcklpe]

@tflidd I ended up solving this issue using bindfs. The issue arises in part because I am running my server on my desktop and also manipulating files directly on my desktop. These files are mounted as local external folders to the desktop but reside in my Home folder.

Just to check what you mean, when you say "configuration issue" do you mean like an nginx configuration issue or a NextCloud configuration issue?

[jcklpe]

Also my understanding is that NextCloud group rights only refer to the rights of NextCloud users within the nextcloud interface and doesn't reflect the permissions that the www-data user actually writes those changes to the HDD with. Is that incorrect? I'm having trouble finding that documentation.

[jcklpe]

Also I wanted to include the forum thread by which I fixed this issue in case someone else comes along and has a similar problem: https://help.nextcloud.com/t/permissions-issues-on-local-external-folders/34958/39

It should also be noted that merely changing the nginx chmod pattern for folders and files etc would not fix this issue entirely due to the way that my particular set up worked. It was ultimately still necessary to change the default umask stuff for systemd so that Nautilus etc would be able to create new folders that were writable by www-data, and even then this solution apparently creates a problem with copying files form one folder into another.

The simplest solution, and the one which covers all necessary uses-cases has been the bindfs solution, which apparently has some slight performance issues but not that much. I actually think this solution should be added to the NextCloud official documentation in some way, unless there's a planned internal solution. At least for me it was very hard to find out this sort of information.