Mail invitation - There was an error updating your attendance status. #15814
Comments
|
Is it in a calendar shared with you? => there already is a Server Ticket about this in the Server. Do all Nextcloud users have unique email addresses? => If no, that’s not supported |
|
No, the calendar used is my default calendar and i can confirm, that there are no duplicates in the mail-addresses. |
@georgehrke Does this problem only affect the accounts which have non-unique e-mail addresses or does it affect all accounts as soon as there is one non-unique e-mail address? |
|
Any update on this? I still have the same error with Nextcloud version 16.0.1 and calendar version 1.7.0. I can confirm that the user list does not show users with the same mail address and i see no duplicat mail addresses in the db, too. |
skjnldsv
added
the
0. Needs triage
|
I Have exact the same issue with one user in my nextcloud installation. |
|
Hi there, any Updates on this? I'm having the same issue but with every user. I am on NC 16.0.3 and Calendar 1.7.0, i have no users with the same Mail address. I create an appointment on my own personal cal, add an attendee (one of my other private Mail addresses, not connected to the system), i get the invitation mail, click on "accept" and i get the error: There was an error updating your attendance status. I have zero clue where to look from here. |
|
Hello. The same problem, on two nextclouds. Each with NC 16.0.0 and calendar 1.7.0 |
|
Hello, also same problem here with NC 16.0.3 also without any e-mail duplicates. |
|
same problem on my server when clicking on the mails sent to the invited person via email. NC: 17.0.3 |
|
I can confirm this. NC: 18.0.3 |
|
What are you using for background jobs? I had the same problem and switching from ajax to cron seems to have fixed it. |
|
I am using cron |
|
I have the same behaviour on one NC instance. If i chose the accept button inside the invitation, it will result in an error on the NC page: NextCloud versions{ "id": "removedbyme", "items": [ [ "server", "version", "19.0.4.2" ], [ "server", "code", "other" ], [ "server", "enable_avatars", "yes" ], [ "server", "enable_previews", "yes" ], [ "server", "memcache.local", "\\OC\\Memcache\\APCu" ], [ "server", "memcache.distributed", "none" ], [ "server", "asset-pipeline.enabled", "no" ], [ "server", "filelocking.enabled", "yes" ], [ "server", "memcache.locking", "none" ], [ "server", "debug", "no" ], [ "server", "cron", "cron" ], [ "php", "version", "7.3.6" ], [ "php", "memory_limit", 536870912 ], [ "php", "max_execution_time", 3600 ], [ "php", "upload_max_filesize", 535822336 ], [ "database", "type", "mysql" ], [ "database", "version", "5.6.19" ], [ "database", "size", 14229504 ], [ "apps", "accessibility", "1.5.0" ], [ "apps", "activity", "2.12.1" ], [ "apps", "admin_audit", "1.9.0" ], [ "apps", "announcementcenter", "3.8.1" ], [ "apps", "bruteforcesettings", "disabled" ], [ "apps", "calendar", "2.0.4" ], [ "apps", "caniupdate", "disabled" ], [ "apps", "cloud_federation_api", "1.2.0" ], [ "apps", "comments", "1.9.0" ], [ "apps", "contacts", "3.4.0" ], [ "apps", "contactsinteraction", "1.0.0" ], [ "apps", "dav", "1.15.0" ], [ "apps", "federatedfilesharing", "1.9.0" ], [ "apps", "federation", "1.9.0" ], [ "apps", "files", "1.14.0" ], [ "apps", "files_lock", "0.8.3" ], [ "apps", "files_pdfviewer", "1.8.0" ], [ "apps", "files_rightclick", "0.16.0" ], [ "apps", "files_sharing", "1.11.0" ], [ "apps", "files_texteditor", "disabled" ], [ "apps", "files_trashbin", "1.9.0" ], [ "apps", "files_versions", "1.12.0" ], [ "apps", "files_videoplayer", "1.8.0" ], [ "apps", "firstrunwizard", "2.8.0" ], [ "apps", "gallery", "disabled" ], [ "apps", "groupfolders", "7.1.0" ], [ "apps", "impersonate", "1.6.1" ], [ "apps", "logreader", "2.4.0" ], [ "apps", "lookup_server_connector", "1.7.0" ], [ "apps", "nextcloud_announcements", "1.8.0" ], [ "apps", "notifications", "2.7.0" ], [ "apps", "oauth2", "1.7.0" ], [ "apps", "password_policy", "1.9.1" ], [ "apps", "passwords", "2020.10.0" ], [ "apps", "photos", "1.1.0" ], [ "apps", "polls", "1.5.4" ], [ "apps", "privacy", "1.3.0" ], [ "apps", "provisioning_api", "1.9.0" ], [ "apps", "recommendations", "disabled" ], [ "apps", "serverinfo", "1.9.0" ], [ "apps", "settings", "1.1.0" ], [ "apps", "sharebymail", "1.9.0" ], [ "apps", "spreed", "9.0.4" ], [ "apps", "support", "1.2.1" ], [ "apps", "survey_client", "1.7.0" ], [ "apps", "systemtags", "1.9.0" ], [ "apps", "tasks", "0.13.3" ], [ "apps", "templateeditor", "disabled" ], [ "apps", "text", "3.0.1" ], [ "apps", "theming", "1.10.0" ], [ "apps", "twofactor_backupcodes", "1.8.0" ], [ "apps", "updatenotification", "1.9.0" ], [ "apps", "user_external", "disabled" ], [ "apps", "viewer", "1.3.0" ], [ "apps", "workflowengine", "2.1.0" ], [ "stats", "num_files", 20647 ], [ "stats", "num_users", 17 ], [ "stats", "num_storages", 22 ], [ "stats", "num_storages_local", 1 ], [ "stats", "num_storages_home", 17 ], [ "stats", "num_storages_other", 4 ], [ "stats", "num_comments", 140 ], [ "stats", "num_comment_markers", 7 ], [ "stats", "num_systemtags", 6 ], [ "stats", "num_systemtags_mappings", 1 ], [ "files_sharing", "num_shares", 34 ], [ "files_sharing", "num_shares_user", 2 ], [ "files_sharing", "num_shares_groups", 21 ], [ "files_sharing", "num_shares_link", 2 ], [ "files_sharing", "num_shares_link_no_password", 2 ], [ "files_sharing", "num_fed_shares_sent", 0 ], [ "files_sharing", "num_fed_shares_received", 0 ], [ "files_sharing", "permissions_1_1", "6" ], [ "files_sharing", "permissions_2_1", "8" ], [ "files_sharing", "permissions_3_1", "2" ], [ "files_sharing", "permissions_1_3", "1" ], [ "files_sharing", "permissions_4_15", "1" ], [ "files_sharing", "permissions_1_17", "7" ], [ "files_sharing", "permissions_1_19", "7" ], [ "files_sharing", "permissions_0_31", "2" ], [ "encryption", "enabled", "no" ], [ "encryption", "default_module", "no" ] ] }If I chose "Weitere Optionen..." (more options ?) from the invitation mail, I'll get the correct configuration page on NC. But the Save-Button results to the same error as above. May be interesting: There is an other NC instance, hosted by the same provider, but on an other server. This instance will work as expected. The NC versions are exactly the same. Difference are the OS-Versions on the servers and the history of the instances. The first is older (more updates installed). |
|
I do see the same problem, but i was able to find a disabled test user which caused the problem. As the mail attribute is not unique in our company it would be great to have working e-mail invitations without unique e-mail addresses based on the hash in the accept- or decline links from the invitation e-mail. |
|
Same issue on NC 20.0.1 with calendar app 2.1.2. No users have duplicate email addresses. I'm using system cron. I fixed the issue by adjusting "Restrict users to only share with users in their groups" in the admin sharing settings to false. |
|
I read somewhere that the problem might be with usernames which contain spaces. Did somebody try that? |
It was not the case as I had the problem in Nov 2020 |
|
@cnmicha Did you get it solved? |
|
@JMoVS A workaround was to set "Restrict users to only share with users in their groups" in the admin sharing settings to false. |
|
@cnmicha Wow that is a weird work around. Does this prevent them from creating public links? |
|
@JMoVS Maybe.. I haven't traced down the problem any further |
|
@cnmicha Hmm in my case it was already not enabled :-/ |
|
I can confirm that it does not work, also not with a workaround in place ;) because for me this was always the case. |
|
Go in "Settings->Administration->Sharing", then disable the checkbox “Restrict users to only share with users in their groups” does not fix this issue here with: Nextcloud: 20.0.9 User inviting: [email protected] |
|
The workaround (disable the checkbox “Restrict users to only share with users in their groups”) is able to remove the error message "There was an error updating your attendance status." However doing that creates a Privacy setting issue for admins, as users from a specified group can access contacts of other groups within my NC instance: for this reason, I agree that the workaround is not fixing the issue, just a temporary solution hoping for a definitive fix in the next NC release. My setting where the issue is still not fixed: Nextcloud 21.0.1 and Calendar App 2.2.1. |
|
In my case the error only appears if users are not logged in. Logging in to my account and then clicking on the link (with the browser used for the login) solves this issue. Lifting the share restriction for users as suggested previously is not an option in my case. |
|
Unfortunately logging in is not an option if an organization wants to invite external users that do not have a NC account associated with their email address. |
|
@SebastianBerlin unchecking the option onlyShareWithGroupMembers is not an option: this creates a Privacy issue with private groups that should not see the users from other groups. |
I know. In my case neglectable, because there is only one group. It was just a hint for the involved devs, that this could solve the issue. |
Weird, since NC 26 (stable) it's not possible anymore with this dirty solution. Guests receive this awful message after they clicked 'accept' in the mail they got.
That is really really bad, especially for professionals. |
After reading the ticket details and responses like #15814 (comment) it sounds like documentation could be a goof first step, and so is adding more logging. I'm not acquainted with the internals of Sabre and can't tell if writing our own principal backend is a good idea. |
|
If I'm not mistaken we are talking about two problems in this tickets
|
|
Ran into this while testing an unrelated bug on my dev env: Edit: same email address assigned to three test users. |
|
I still have the initially described problem on NC 25. |
I get that it's frustrating, but here's the issue. We can't really deny user accounts from using email addresses that have already been used by someone else. But that leads to errors in Sabre since the calendaring system assumes the email is a unique identifier. So it finds multiple calendars for the same email address for different user accounts, but since there is nothing telling the code which one is the right one, the code, instead of leaking info, stops processing the data and errors out. There is currently no good way forward to solve this issue. Either we change stuff in Sabre in a way that doesn't adhere to the calendaring RFCs, leading to unforseen bugs and possibly even compatibility issues with other calendaring clients. Or we adjust Nextcloud to disallow duplicate emails, which will have wide reaching effects on all parts of NC. Both of those are not something we can simply fix. Any change for this needs to have as few side effects as possible, ensure we still adhere to the calendaring RFCs and also not change the core of how NC works. |
This bug main problem is not with duplicated emails: main problem is that any user not having a Nextcloud account can't accept or deny any meeting invitation sent through Nextcloud Calendar App. This repressents a very basic feature that is not working today on Nextcloud: should be fix as soon as possible, duplicated emails problem can be fixed later on. |
Would a be possible to add a warning in the admin interface or via occ command that shows which accounts are affected? Part of the problem is that most affected users aren't aware of the issue and don't have a clue how to work around it. The result is that Nextcloud generates errors and seems unreliable to our own users and others. |
|
The easiest way to fix this right now is to just not allow invitations to
anyone outside of Nextcloud. Check if the email is registered, if it's not
then throw an error saying so. Another thing is to just not allow duplicate
emails for different users, this seems like a security problem anyways
allowing multiple users to have the same email.
…On Tue, Jun 27, 2023 at 12:23 PM Lars Becker ***@***.***> wrote:
@miaulalala <https://github.com/miaulalala>:
There is currently no good way forward to solve this issue. Either we
change stuff in Sabre in a way that doesn't adhere to the calendaring RFCs,
leading to unforseen bugs and possibly even compatibility issues with other
calendaring clients. Or we adjust Nextcloud to disallow duplicate emails,
which will have wide reaching effects on all parts of NC. Both of those are
not something we can simply fix. Any change for this needs to have as few
side effects as possible, ensure we still adhere to the calendaring RFCs
and also not change the core of how NC works.
Would a be possible to add a warning in the admin interface or via occ
command that shows which accounts are affected? Part of the problem is that
most affected users aren't aware of the issue and don't have a clue how to
work around it. The result is that Nextcloud generates errors and seems
unreliable to our own users and others.
—
Reply to this email directly, view it on GitHub
<#15814 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNNBZ6DF6Q3B37G2GJO4YDXNMJJFANCNFSM4HRDVYWQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
*Devin Arendt*
*Cell: 815-751-7723*
|
Oh, then I know how to fix all bugs and solve all problems in any software: just avoid using it! Now seriously: no, this is not a fix, this is crippling. Ability to send email invitations to non-registered users and processing feedback from them is essential part of functionality and it has to be fixed properly. |
|
I said easiest, I didn't say most logical. Nextcloud was never meant to be
a public cloud software anyways so it makes sense to keep mostly everything
local to nextcloud.
The more logical approach is to just use a token based system for
meeting/calendar confirmations and store the email into an "unregistered
users" table of sorts so they can register as a user later if given
permission.
Feel free to submit ideas of how to fix it instead of complaining and not
giving a solution to the problem.
…On Tue, Jun 27, 2023 at 1:21 PM Nik ***@***.***> wrote:
The easiest way to fix this right now is to just not allow invitations to
anyone outside of Nextcloud.
Oh, then I know how solve all bug and problems in any software: just avoid
using it!
Problems?
—
Reply to this email directly, view it on GitHub
<#15814 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNNBZYMRT7PXMG6FT3ZGITXNMQCRANCNFSM4HRDVYWQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
*Devin Arendt*
*Cell: 815-751-7723*
|
|
however -> i use the calender only to invite nextcloud users. and i am nextcloud user myself. as far as i understand you the problem should not happen in this case but it is? It would be new to me that we have duplicate email adresses as it is also unique in the company. so i dont get the problem here. my case is pretty the simplest: nextcloud calender user is inviting another nexcloud calender user to an event. not working when accepting over email. should it? |
|
If it's another nextcloud user and there's no duplicate emails then that
would be a different bug outside of the scope of the current issue being
discussed. Honestly the two issues being discussed here (duplicate emails,
non-nextcloud user) should be separated into different bug reports since
they're two entirely different scenarios.
…On Wed, Jul 5, 2023, 8:36 AM Mat ***@***.***> wrote:
however -> i use the calender only to invite nextcloud users. and i am
nextcloud user myself. as far as i understand you the problem should not
happen in this case but it is? It would be new to me that we have duplicate
email adresses as it is also unique in the company. so i dont get the
problem here. my case is pretty the simplest: nextcloud calender user is
inviting another nexcloud calender user to an event. not working when
accepting over email. should it?
—
Reply to this email directly, view it on GitHub
<#15814 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNNBZ5G7SINCPDYIM5BXA3XOVUU7ANCNFSM4HRDVYWQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
At least for the duplicate email problem I found a thread: #17146 however, both cases do not apply to my case (i am nextcloud user with unique email) , and yet i cannot accept calendar invites from calendars, that have not previously been shared with me. I am rather confused and somewhat surprised that the docs do not properly hint to what is possible under which circumstances and what is not. |
|
Dears, Someone asked for more constructive solutions how to solve it, like a token-table for non-user-invitations. Can someone of the developers role out the status quo of the invitations-mechanics in NC? Would be a good start to have this years-long issue solve. Thank you, Thomas |
|
Maybe this will help future diagnostic efforts. I read through a number of comments and didn't see this mentioned: I was able to solve the problem by going directly to the database and cleaning out old users that weren't showing up in the UI from the oc_accounts table. I'm using LDAP for user authentication and groups and so it seems like it would hide users that were removed from LDAP, but wouldn't remove them from the NC database, which is great. I see the benefits of that. But if a user was deleted in LDAP and then recreated with the same email, there would then be two users with the same email recorded in the DB but only one would show up in the UI making it look like there wasn't any duplicate emails. Maybe it's possible there are other circumstances where user accounts are hidden from the UI, but still stored in the DB and thus cause this problem... It seems cleaning up the DB of duplicate emails also solved the non-nextcloud invites since everything seems to be working flawlessly now, but I can't confirm this as I wasn't specifically thinking of this scenario. All I know is I couldn't seem to get accepting/declining invites to work at all before and now it all works fine. Just some ideas: Maybe it would be helpful to have an oc_accounts cleanup option to automate this process or add it as a warning in the "Security & setup warnings" in the admin settings when there are duplicate emails in oc_accounts so it makes admins aware that this will cause problems. |
|
Hello, Sorry for the bump, but it's a 5 years old ticket and nothing for the last 8 months for an important feature (we have lots of complains, people saying they are missing rdv etc..) I understand it's not an easy problem to solve, but any idea when we can hope to see this problem resolved? Thanks |
|
Hi @quenenni. I'm not familiar with the code that managed invitation validations, but it's bound to this checkbox. |
|
@nderambure Thanks for the tip, but we can't uncheck that box, to respect privacy. That's really something we can't do. |
|
@quenenni : yep, I'm affraid this is only usefull on NXC instance where you only have one group...kind of workaround. |
|
Dear @quenenni, yes it might be a log running issue. But it‘s really important as you stated yourself. I follow it for some years, since this issue is the show stopper for desicion making for NXC for a plattform for calendar, contacts and issues-tracker. |
|
Since I'm also bothered by the problem I invested some spare time today and here's what I found: Nextcloud version: 30.0.0 So I created an invitation and received this link: Clicking on the link to accept of course resulted in the dreaded "There was an error updating your attendance status." message. Looking at the code I found that the message is generated in line 75 here (because the organizer is shown to me): server/apps/dav/lib/Controller/InvitationResponseController.php Lines 62 to 77 in 31ad1c5 As it seems at least in my case the returned value for This particular result code is generated here (in line 509): So why did it end up there? As it turns out, this happens when in Line 505 Since server/apps/dav/lib/CalDAV/CalDavBackend.php Lines 2346 to 2362 in 31ad1c5 This creates an SQL query which obviously returns an empty result set where it shouldn't. Translating the statement to real SQL and running it directly on the MariaDB server attached of course also gave me an empty result set. SELECT c.uri AS calendaruri, co.uri AS objecturi FROM oc_calendarobjects AS co LEFT JOIN (oc_calendars AS c) ON (co.calendarid = c.id) WHERE c.principalUri = 'principals/users/user1' AND co.uid = '3085bd4f-15f8-434d-aab2-9ab197056123' AND co.deleted_at IS NULL;
Empty set (0.000 sec)Verifying that the objects actually exist gave a positive answer: SELECT co.uri AS objecturi, c.id AS calendarid FROM oc_calendarobjects AS co WHERE co.uid = '3085bd4f-15f8-434d-aab2-9ab197056123';
+------------------------------------------+------------+
| objecturi | calendarid |
+------------------------------------------+------------+
| 3085bd4f-15f8-434d-aab2-9ab197056123.ics | 6 |
+------------------------------------------+------------+Ok, now that I got the calendar id, check out what records it may have: SELECT * FROM oc_calendars WHERE id = '6';
+----+--------------------------+------------------+------------------+-----------+-------------+---------------+---------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------+-------------+------------+
| id | principaluri | displayname | uri | synctoken | description | calendarorder | calendarcolor | timezone | components | transparent | deleted_at |
+----+--------------------------+------------------+------------------+-----------+-------------+---------------+---------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------+-------------+------------+
| 6 | principals/users/mypersonaluser | Family | familycalendar | 2651 | NULL | 4 | #C37285 | BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Apple Inc.//Mac OS X 10.15.6//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
DTSTART:19810329T020000
TZNAME:MESZ
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
DTSTART:19961027T030000
TZNAME:MEZ
TZOFFSETTO:+0100
END:STANDARD
END:VTIMEZONE
END:VCALENDAR
| VEVENT,VTODO | 0 | NULL |
+----+--------------------------+------------------+------------------+-----------+-------------+---------------+---------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------+-------------+------------+Some things immediately hit the eye:
Not caring about the timezone field for now I just removed the line creating the WHERE clause for the This time in line 497 of Thus, the construction of To fix this, I had to modify $objectPath = $homePath.'/'.$result;now doing $objectPath = 'calendars/'.$result;in line 496. And lo and behold, I'm now able to accept invitations in shared calendars. Wasn't able to test whether this also fixes similar problems with personal calendars but if you want to try, the patch is attached. Chances are it'll make things worse Be aware that I did this just for me, scratching my own itch and that I didn't check for any potential side effects That's also why it isn't submitted as a PR ;) You have been warned. |
|
Thank you, @RustyDust for your solution! In my case I checked e-mails in database (Nextcloud 29). |
and others
Steps to reproduce
Expected behaviour
Status of attendee should be updated in the calendar view.
Actual behaviour
The following error is shown:
There was an error updating your attendance status.
Please contact the organizer directly.
Already tried
I already found this post with the same problem and tried to use another mail address for my Nextcloud account without success. There is currently no user sharing the exact same mail address.
https://help.nextcloud.com/t/solved-cannot-accept-calendar-invitation/50154
Server configuration
Operating system:
Ubuntu 16.04
Web server:
Apache
Database:
MySQL
PHP version:
7.2.12
Server version: (see your admin page)
15.0.7
Calendar version: (see the apps page)
1.6.5
Updated from an older installed version or fresh install:
Yes, updated since ownCloud 8
Signing status (ownCloud/Nextcloud 9.0 and above):
List of activated apps:
Nextcloud configuration:
Are you using external storage, if yes which one: local/smb/sftp/...
no
Are you using encryption: yes/no
no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
no
Client configuration
Browser:
Firefox , Chrome
Operating system:
Windows 10, macOSX, iOS
CalDAV-clients:
iOS
Logs
Web server error log
Log file (data/nextcloud.log)
Browser log
The text was updated successfully, but these errors were encountered: