HTTP 204 No Content must not have a body and thus Content-Length (which is the definition of 204). It seems like your server has returned HTTP 204 with a body, which does not make sense and can’t be interpreted. Please fix your Web server/application server.

Hello, The server return’s an internal server error, probably because it couldn’t process one of its events. Please contact the server support.

Hello, Although there is no debug info, it seems that Nextcloud returns an error when DAVx5 requests the events/contacts. Is there any indication that this could be a DAVx5 problem?

It works! Thanks!

Thanks for the test account. When DAVx⁵ queries the resources, the server sends: <?xml version="1.0" encoding="utf-8"?> <D:multistatus xmlns:a="urn:ietf:params:xml:ns:carddav" xmlns:D="DAV:"><D:response><D:href>/SOGo/dav/c%26m@example</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><a:addressbook-home-set><D:href xmlns:D="DAV:">/SOGo/dav/c&m@example/Contacts/</D:href></a:addressbook-home-set><D:group-membership/></D:prop></D:propstat></D:response></D:multistatus> which causes this DAVx⁵ error: Couldn't parse urn:ietf:params:xml:ns:carddavaddressbook-home-set EXCEPTION org.xmlpull.v1.XmlPullParserException: unterminated entity ref (position:TEXT @2:247 in okhttp3.ResponseBody$BomAwareReader@abfda3c) As you can see, the & is not escaped in the href element, which is invalid XML and can’t be parsed. So, this seems to be a server problem and it seems to be related to the bug report you have posted. If there are any specific indications that this could be a DAVx⁵ problem, please let us know.

@Saroumane Thanks for the update!

Good to know. I was already wandering. I was using aCalendar, not aCalendar+. In the free version it is not provided. Thanks for the quick feedback … Max

@hidde Thanks!

@nate2014jatc Maybe you could ask in the Nextcloud forum. As far as I know, issues are better for reporting bugs than asking questions, and it will take longer to get an answer.

@heX16 That would certainly be possible, if there is no other solution (like fixing the problem where it comes from). I’d really appriciate if you could contact the MyPhoneExplorers and tell me what they say? Android account names can easily contain Unicode characters, for instance if you use local language. What if you name an account “Mein schöner Account”? Or “мой аккаунт”? Such names should work with any app, and they’re not related to DAVx⁵.

@wanderlei-huttel I see, sorry… didn’t notice the logs. It doesn’t look suspicious from DAVx⁵ point of view.

@mtausig Ok. Please contact the service which generated the .ics file to fix that.

@xuziq2000 I see… Seems like it also works without OAuth2, because DAVx⁵ doesn’t support OAuth. However your problem seems to be a server problem. Is there is anything specific we can do for you, just let us know.

Hi @Larnal, please try again with the new Baikal version 0.5.2. The old 0.5.0 did not support php 7.2 yet and I guess you used it with php 7.2. I got the same error message before upgrading.

It still happens a lot with standard Google calendars. Sometimes it syncs sometimes not, sometimes only one but most times all 5 of them. Is there any way to get a log file?

@rfc2822 I’m sorry, I can’t. But my fantatstic admin was able to! All is back to normal now, thanks for assistance.

@sergio Workaround still works (using DAVx⁵ 2.2.1-ose and OpenTasks 1.1.15), however, once I check a task as done in OpenTasks the issue returns with the next sync. Now I’m using aCalendar+ as calendar app and OpenTasks to sync tasks. When I get a notification for a due task, I just check it as done in the aCalendar+ notification. Notifications from OpenTasks are deactivated. A sync thereafter does not trigger Vibration. So the Vibration only happens after checking within the OpenTasks notification.

I’ve been able to figure out why the import in Thunderbird failed for the 51 entries: If the UID of a VEVENT contains “@domainname.tld” or “@machine-name”, the Posteo.de CalDAV server returns HTTP statuscode 404 for the REPORT HTTP method. I have now removed all occurences of “@followedbyastring” and successfully imported my .ics-file with Thunderbird. I have not tested the import on my phone using DAVdroid and Calendar Import Export. Should Posteo.de support occurences of “@followedbyastring” in a UID? If I have time to do so, I will report this issue to Posteo.de But please: Feel free to test and report the issue to Posteo.de Sorry for the noise, I initially thought this was a DAVdroid problem.

Thanks for the logs. I was finally able to reproduce a similar situation: Upload an event with UID:a%40b (note the %, for instance coming from some erroneously double-encoded old UID; nevertheless valid) to Google /events/a%40b.ics (or anything else) Google usually rewrites the path (= moves the event) to <UID>.ics, which would be a%40b.ics. However, Google CalDAV REPORT calendar-query reports /events/a%2540b.ics as the URL of the resource. If you want to download /events/a%2540b.ics from Google, it returns 404, although it had just listed this path. So, in my opinion and what I currently know about it, this seems to be a server problem. It should go away if you delete all events on the server and then only create/sync “clean” events with “good UIDs”. Maybe you can also create a new calendar for testing and see whether this one works?

Ok, then you very much for your fast help! I’ll look into the server logs again. Is there a way to close this Thread?