![]() ![]() ![]() I'd think that Synology would automatically set up the folders properly since it is a feature DSM handles (the creation of homes for all users). ![]() I'm probably missing something obvious, but I can't think what it could be. I will also mention that the user with the issue does have a space in their username (in case that proves to be relevant). The user has permissions to read/write that folder, also. I can see the folder just fine in File Station, too. The Drive folder exists and the user has permissions for the folder and MyDrive is enabled as a location in the Team Folders section. However, it is my understanding that the default MyDrive folder is typically located in the /homes/USERNAME/Drive/ I've added the new users as 'standard' accounts, and my own account is an administrator account. I added a few members of my family and see it's created home folders for each of the new users. I'm now starting to add members of my family and have some questions on how best to set it up. When the user logs into Drive, they are told the MyDrive folder doesn't exist. 1 In the past I've only had my own user account on my DSM. I recently installed the Synology Drive suite of apps on the NAS and I enabled Drive for one of the users. I have a single large volume set up on the NAS where everything resides. I have the latest DSM 7.1 non-beta installed on my NAS. maybe I should also note that I tried migrating it (which I think did succeed, but I thought it had failed because of the described error), and then once or twice I deleted my installation and did it over again.I tried searching for this issue here, but was unable to find anything like it. I chose to post this in “Support” because technically my installation is up and running. (nothing useful, just information about the TypeError which does not affect me. Output errors in nextcloud.log in /var/www/ or as admin user in top right menu, filtering for errors. The output of your Apache/nginx/system log in /var/log/_: The check_data_directory_permissions is there, because I got the error “ Your data directory is readable by other users” 'check_data_directory_permissions' => false, 'datadirectory' => '/volume1/web/nextcloud/data', TypeError: OCA\DAV\Connector\Sabre\FilesPlugin::OCA\DAV\Connector\Sabre\(): Return value must be of type ?int, float returned The output of your Nextcloud log in Admin > Logging: Error: chmod(): Operation not permitted at /volume1/web/nextcloud/lib/private/Log/File.php#86Įrror: exif_read_data(): File not supported at /volume1/web/nextcloud/lib/private/Metadata/Provider/ExifProvider.php#20 Is this the first time you’ve seen this error?: yes Setting the owner of all folders and subfolders to http:http is not helpful either. Nextcloud then displays the message “ This directory is unavailable, please check the logs or contact the administrator”. If no modifications were made previously, the default permission entries will appear on the page. On the Permission tab, you will find the current permission entries for the 'homes' folder. Setting the owner as my own user account, everything works, but as soon as I upload data, the owner of the data folder becomes http:http. Launch File Station, right-click on the 'homes' shared folder, and select Properties. Operating system and version: Synology DSM 7.1.1-42962Īpache or nginx version: Apache Http Server 2.4 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |