Why do you think the permissions are broken in the first place? Does the cloud work? Are there any problems? There should not be any differences in NC 13. Give us a listing of the output of
ls -la
in the nc root directory. Is this a Debian / Ubuntu system? My directory looks like this:
And used Method 2 to symlink out my data directory. When I do you suggested number 9, do I need to do this also on the linked directories? Or does linux do it automaticly? I looked now in the directory and the symlink itself is 777.
To be on the secure site:
I went to /var/www/ and followed your suggestion. Was this right or do I need to go in the nextcloud directory?
I looked at the linked directory:
drwxrwxâ 19 www-data www-data 4096 Feb 28 07:25 data
This is still correct, but in this it seems to look not correct, e.g.:
-rwxrwxrwx 1 www-data www-data 1126022 Mar 17 11:37 updater.log
drwxr-xr-x 4 www-data www-data 4096 Mar 17 11:42 updater-oc6t6ey2ygrc
drwxrwxrwx 4 www-data www-data 4096 Aug 19 2017 updater-oc6wqgwqj867
Now I see that I have a bigger problem with my permissions and I will open for this next time a new topic, sorry for spamming for support in the news category
You have also lines that are executeable to others So I´m still asking what the savest solution
When you will follow Bernie_O´s suggestion your permissions will look different than your previous ones.
So it´s a little bit confusing for me and that the reason why I´m asking
The x that you see in the âotherâ row are directories, so these are not executable flags. You might still be right, @Bernie_O has good suggestions.
yes, if you mean the first flag. But you have also an x =executable for ownership others. It´s like 751 atm but as in documention you need for my understanding a 750 for your directories For example your settings directory
No, I mean the third flag for others. The x flag on directories does not include executable (you cannot execute a directory) but only accessible. For the content of the directory the normal access rules apply. So you still need the x flag to execute files, this is not given by the x flag of the containing directory.Still, to enhance security it is still useful to remove the x flag from directories also.
The symlink itself by default is 777, which is no problem if the permissions of the actual data directory is stricter, which counts.
As theoretically only the webserver needs to acress to the actual data directory, it should be possible to set itâs permissions to 700 for folders and 600 for files. If you want to be on the secure side, just set data/.htaccess permissions to 400 or owned by root:www-data and 640. But webserver configuration should prevent direct access to this anyway.
As said, the permissions of the symlink /path/to/nextcloud/data doesnât matter. Just the permissions of the actual data folder, where the link is pointing to, is relevant and changing this will not be reflected by the symlink.
Update seemed to go smoothly. Only thing I noticed is now I get trusted domain error in my logs? Guess I spoke to soon. I tried to update my theme and the change did not work and got the following error messages.
Doctrine\DBAL\Exception\UniqueConstraintViolationException: An exception occurred while executing âINSERT INTO oc_filecache (mimepart,mimetype,mtime,size,etag,storage_mtime,permissions,parent,checksum,path_hash,path,name,storage) SELECT ?,?,?,?,?,?,?,?,?,?,?,?,? FROM oc_filecache WHERE storage = ? AND path_hash = ? HAVING COUNT(*) = 0â with params
@e-raser I find it strange that you say your current version is 12.0.6 and the updater reports v12.0.4RC1. What versions are in config/config.php and in version.php?