-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when creating share #21120
Comments
I get this in v19.0.0 and v19.0.1 (upgraded from v18 to v19, worked fine in v18). Created new file using web interface, clicked share. File manager shows (for a short while) that the file is shared, The log:
|
To be sure, the summary is: sharing with expiration date does not work. What further triage is needed? Happy to help. |
I have added the linked issue above with more details from the browsers JavaScript log. |
Pretty sure the server error is the indication of what the root cause is. |
I also get the error in Nextcloud 19.4. I share it with users and groups, not as a link. |
do you have a default expiration date set? |
I tried any combination, but no change. I tried setting the share on a folder. It works when sharing a file. |
so do you get ther error when both settings are disabled? What do you see in the server log? |
I get the error no matter what this setting is for either: All disabled, one of them enabled and all of them disabled, can't share the folder. |
Everyone here, please give us your browser logs Hello! How to access your browser console (Click to expand)Chrome
Safari
IE9
Firefox
Opera
|
No errors in nextcloud.log. Console gives this error: |
@Skalli what path are you trying to share? cc @rullzer @nickvergessen we cannot share a folder that contains a share? server/lib/private/Share20/Manager.php Line 678 in de7026f
|
Yeah, it was a folder, one subfolder had a share. I wasn't aware of that limit and the very generic error message was not helpful. I moved the shared subfolder to a different location and then adding the share worked. |
Yes @skjnldsv otherwise you could create loops:
It would break your sync client, the file scan and everything else. So having a received share inside a shared item is not possible. |
Let's just improve the wording then and block sharing ? |
Just wanted to chime in.
This is quite odd since the response, as can be seen below contains much more than one would expect. Almost as if debugging was enabled in Circles maybe? Request:
Request payload:
Response:
|
Yes, the share was indeed created. But the front-end application of
course can't handle a response body like that.
|
You mean a response body like {
"ocs": {
"meta": {
"status": "ok",
"statuscode": 200,
"message": "OK"
},
"data": {
"id": "211",
"share_type": 7,
"uid_owner": "08ece906-d7b8-1035-9c8d-97c38bc36d8d",
"displayname_owner": "David Raison",
"permissions": 31,
"can_edit": true,
"can_delete": true,
"stime": 1604851797,
"parent": null,
"expiration": null,
"token": null,
"uid_file_owner": "08ece906-d7b8-1035-9c8d-97c38bc36d8d",
"note": "",
"label": "",
"displayname_file_owner": "David Raison",
"path": "/Fun",
"item_type": "folder",
"mimetype": "httpd/unix-directory",
"storage_id": "home::08ece906-d7b8-1035-9c8d-97c38bc36d8d",
"storage": 3,
"item_source": 77346,
"file_source": 77346,
"file_parent": 312,
"file_target": "/Fun",
"share_with_displayname": "BuCo (Closed circle, David Raison)",
"share_with_avatar": "https://cloud.tentwentyfour.lu/apps/circles/img/closed.svg",
"share_with": "8e5e0a8787fd9",
"mail_send": 0,
"hide_download": 0
}
}
} Looks good to me 🤔 |
details of what I see (saw) in the server log: The issue is still the same, even though currently I don't see that error anymore in the server log, and the client does not show an error message.
In the server log I see this one dozens of times in last week or so (not directly linked to the sharing issue)
The devtools show an (I think) normal PUT for the file, including the expiration as string:
when reloading I see a couple of requests: Including a 404 error inside the XML of the PROPFIND call (statuscode 207):
Immediately followed by a 404 for:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I get the following error. Same problem as original poster, I can not share a newly created folder in the root directory with a group, although there are lots of previously shared folders there. Please let me know if I should share more information with you. This is Nextcloud 19.0.4 on Ubuntu 18.04.5 LTS |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hi! I've noticed, that this error appears, when your Nextcloud name consists of 2+ words (f.e. |
Is there already a solution for the "error creating a share" issue, because I can´t get rid of this error. What to do? Reinstalling nextcloud in the expectation it'll work after that? In such a case, will I loose all configuration? Should I back up the configuration, or is there a way to do it to restore back the configuration? Thanks |
This seems to happen when trying to share a folder which contains a file shared with me. In that case there is no loop possible, it feels like the restriction shouldn't apply. |
This comment was marked as outdated.
This comment was marked as outdated.
Does this also happen on 25.0.2? |
Small update: this error occurs only when trying to create links on externals storage files. Local files can be shared successfully. Sharing is of course enabled for external storage. I found #37414 which fits this problem much better. |
Same error "Error while creating the share" here when clicking on "share link", either with external S3 storage or with local files or folders. Should I create another issue ? It is similar to #37414 but also affects local files and folders. (fresh nextcloud 26 / php8.1 / MariaDB manual install) EDIT : When mounting the S3 external storage from the admin set-up page and not from the user set-up page, the problem is gone for both local and external files/folders. |
Fixed in #38115 |
I am using nextcloud snap but the the people on the snap-respository told me that such issues affect the server-repository.
I have been getting this error for a few days now:
When I want to share a folder with another person on my nextcloud there is this error:

Translation: "Error when creating share"
How to reproduce this error:
Click on the sharing-icon on the folder and select another cloud-user.
Then the error message appears.
Despite the error the user gets access and the user is shown in the sharing-list after refreshing the page.
Tested on version 18.0.4
This has only started occuring recently (snap updates itself)
The text was updated successfully, but these errors were encountered: