On Tue 12-May-2020 at 12:59:22 +02, "Loris Bennett" <loris.benn...@fu-berlin.de> wrote: > Eric S Fraga <e.fr...@ucl.ac.uk> writes: > >> On Tuesday, 12 May 2020 at 09:29, Loris Bennett wrote: >>> The Nextcloud instance at work is version 15 and is accessible via the >>> browser, but there was some outage recently and some server-side >>> tweakage may also have occurred while things were being fixed. >> >> I don't know if this is related but a recent point release to nextcloud >> caused problems with an OPTIONS directive that org-caldav-sync uses. A >> subsequent bug fix has corrected this but may not have been incorporated >> in your server yet. >> >> See https://github.com/nextcloud/server/issues/20624 >> >> The provider I use for calendar services had to manually patch their >> instance of nextcloud to get it working again for org-caldav-sync. > > Thanks for the pointer, but the link seems to refer to a regression > introduced between versions 18.0.3 and 18.0.4, whereas the server I am > talking to is some version of version 15. > > My android phone is able to sync in both directions via DavX5, so the > server is obviously not totally borked in terms of syncing. So some > aspect of the org-caldav-sync seems to be hitting the problem.
Hi, FYI, I found this issue when looking for a solution for the same problem: https://github.com/dengste/org-caldav/issues/195 In my case, if I am patient enough, the sync completes after 30-50 minutes. --
