Server: path needs to be relative to the system wide data folder and point to a user specific file

[fs1605]

We have been using the file upload in the groupfolder for some time now. Today's update to version 15.0.6. did not solve the problem.

if we want to upload a file to a group folder the error message appears:

"path needs to be relative to the system wide data folder and point to a user specific file"

after the second try, it usually works.

someone a solution?

yes, encryption is on.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity and it seems to be missing some essential informations. It will be closed if no further activity occurs. Thank you for your contributions.

[Tobstr02]

I also have the error with the CLI command encryption:encrypt-all.
I'm using the default encryption module.

[ukrainer8]

I have the same problem (path needs to be relative to the system wide data folder and point to a user specific file) + problems:

• (SabreDAVExceptionForbiden)
• Invalid argument

Do anybody have an idea how to solve them?
Server version 16.0.4, client version 2.5.3, encryption is on (Server-side encryption - Enabled, Encrypt home storage - Enabled, Default encryption module 2.4.0), Group folders 4.0.5. The most files are synced properly, but about 10% of them have these problems...

[phonon112358]

I have the same issue with NC 18.0.1, group folders 6.0.1 and encryption enabled (default encryption module 2.6.0)...
I can't synced any files in the group folders nor copy files from the data root into a group folder...

Any solution???

[LukasSchulz]

Is there a way to disable encryption for the group folders?
Because as it is now it just isn't useable for the end user.
To actually see an uploaded or created file, the user needs to create or upload it twice....
Thank you for any help.

[Micromegass]

Same problem for me. Uploading twice works, which is not a solution though

[SB97]

Same problem NC 18.0.3
with Group folders 6.0.6 and Default encryption module 2.6.0

After a update also on NC 18.0.4

[insanity54]

I had this issue on NC 18.0.4 with Group folders 6.0.5.
I worked around the issue by completely disabling encryption in Nextcloud.

Step 1-- Disable server side encryption

The following picture shows how it should look on the .../settings/admin/security page.

occ maintenance:mode --on
occ encryption:disable
occ:maintenance:mode --off

I had to do this process twice. The first time I did this, the command completed successfully, but the checkbox in .../settings/admin/security still showed checked until I ran the three occ commands again.

Step 2-- Disable encryption app

I read about this from another issue in this issue tracker. I would link it if I could find it, but I can't find the issue again. It wasn't enough to disable server side encryption, I actually had to completely disable the Default encryption module before I stopped getting the error.

[SB97]

I read about this from another issue in this issue tracker.

@insanity54
Maybe https://github.com/nextcloud/groupfolders/issues/71 ?

[insanity54]

Maybe nextcloud/groupfolders#71 ?

No that's not the one I was thinking of. That comment mentions disabling encryption in the home folder, but the comment I'm thinking of mentions disabling the encryption app. I'm still looking for it, I'll post again when I find it.

EDIT: Here is the comment. https://github.com/nextcloud/groupfolders/issues/429#issuecomment-605461318

[Micromegass]

Idk if that helps anyone, but in my case disabling encryption is not an option. I ditched the group folder app completely. Then I create a user group with the admin account and add all users of my choice to the specific group. The I simply share the folder with the particular group. I know there is some behavioural difference to what could be achieved with the group folders, but for me it was sufficient. And I can keep encryption.

In https://github.com/nextcloud/groupfolders/issues/71 they say that a new release will properly disable encryption for group folders, which I don't think is a solution, since the encryption becomes obsolete in the first place.

[void-arch]

Same here on NC 18.0.4 in a docker setup with enabled encryption and groupfolders.
Groupfolders 6.0.6
File sharing 1.10.1
Default encryption module 2.6.0

I tried to

• Share access to a folder with public link to a new user, from there copy/move this public folder to a new private one - failed.
• Copy this public folder somewhere else - failed
• Copy/move this public folder to a groupfolder. Thats where I got the most telling logs:

[Michaelis90]

i don't know if the problem is still current, but i had the same problem.
but I solved (or bypassed) it.
i integrated the nextcloud in windows explorer as a network drive (webdav) and then moved my folders and files to the shared folder.
But I don't know why it works like that.
I hope I could help.

Nextcloud 18.0.7.1
Group folders 6.0.6
Default encryption module 2.6.0
encryption is on

[oszilloskop]

Same problem here. File uploading twice works, which is not a solution though.

Nextcloud 19.0.3
Group folders 7.0.0
Default encryption module 2.7.0
encryption is on

[gchaincl]

Same problem here on nextcloud: 19.0.4.2, group folders: 7.1.0 and Default Encryption module: 2.7.0

[govbetrieb]

Same here. Double upload/delete is working.

[strongboy54]

Idk if that helps anyone, but in my case disabling encryption is not an option. I ditched the group folder app completely. Then I create a user group with the admin account and add all users of my choice to the specific group. The I simply share the folder with the particular group. I know there is some behavioural difference to what could be achieved with the group folders, but for me it was sufficient. And I can keep encryption.

In nextcloud/groupfolders#71 they say that a new release will properly disable encryption for group folders, which I don't think is a solution, since the encryption becomes obsolete in the first place.

This is the solution I believe works best. It's not a perfect collab solution, but it's certainly a preference seeing as you can keep encryption. For me at least there is no functional difference between the two. Thanks!