I have the nextcloud docker running in pi4 and storing itâs data in an external ntfs drive.
I have already given all permission to write and read for all the folders inside of this folder.
However, it seems like nextcloud still have some issues when running it. What am I missing?
Error PHP chmod(): Operation not permitted at /var/www/html/lib/private/Log/File.php#86
Warning no app in context Invalid cliBasedCronUser data provided to provideInitialState by settings
Error PHP Trying to access array offset on value of type bool at /var/www/html/apps/settings/lib/Settings/Admin/Server.php#76
Which docker image are you using? AIO, LinuxServer, Nextcloud, something else?
Could you confirm those with ls -la or similar. Did you map them as docker volumes?
Try searching these errors against the forum and wider internet. Should turn up a bunch of info that could answer the issue for you. Tried searching part of this and found: cliBasedCronUser & Server.php error - #3 by werto165
Yea it seems like a common issue. I have been searching for few days, but unfortunately I canât find an answer that I understand what to do. Iâm using nextcloudâs docker image directly, and I did map my nextcloud/html folder to the docker.
Here is an image from portainer, where I setup my nextcloud as a stack:
Both of them has some sort of hint saying I need to set the ownership correctly; however, the ownership of both of my problematic files are already set to 777. I even set the check_data_directory_permissions to false in config.php. My understanding is that anyone should be able to access it, but why canât nextcloud?
Ok, so I gave up putting the data in my ntfs external drive, now the error is gone.
Originally I have everything on my external drive, including the html folder from nextcloud, and mariadbâs data folder with its backup folder. Now I only have mariadbâs back up folder in my external drive, and everything else in the ext4 main drive.
I guess Nextcloud is not very friendly with mounting things on ntfs drive. If I want to fix this issue in the future, I would probably research more on how they deal with ntfs drive in windows.
Leaving this thread for future users. GL
What would be the proper configuration nextcloud expect for mariadb? I mean I thought all read write permission (777) would take care of everything.
For experiment purpose, I moved mariadb to ntfs, and the error âcould not create new folderâ appears again, which could make sense if I had the wrong permission in fstab.
This is my current line in fstab that mount the ntfs drive:
I stopped using ntfs almost ten years ago, so I have little memory of how it works. It was one of the first things I stopped using when selfhosting. The problem in this case is simply misconfiguration.
If fstab is looking good, then confirm ownership matches www-data with a tool like chown.
You will not need smb if youâve properly mounted the disk. Mounting disks is at the filesystem level as opposed to Nextcloud.
ok, so after using the command to change the ownership of the database folder (both db and db_backup), I donât see the error anymore.
I think I misunderstood âownershipâ. I thought if nextcloud can access it nextcloud will be happy, but in fact www-data has to âownâ the folder to make nextcloud happyâŚ
Thanks
now I just need to figure out how to make my fstab file so that I can smb share my drive and change that folderâs permission at the same timeâŚ
I installed nextcloud docker to ext4 only, and here was the permission I got when everything was working fine (no permission error):
Then I cleared nextcloud to do a re-installation. I installed the db folder into my ntfs HDD, which is mounted using the ntfs3 driver (allowing me to store the permissions), I have this:
where html is also owned by www-data:www-data (same as what you see in the first figure).
I did get some errors when testing right after installation, but after rebooting m pi, I have not seen any error for two days. I think we are good now! Thanks
