Nextcloud version (eg, 29.0.5) : 30.0.1
Operating system and version (eg, Ubuntu 24.04) : Freebsd 13
Apache or nginx version (eg, Apache 2.4.25) : Apache 2.4.62
PHP version (eg, 8.3) : 8.3.12
The issue you are facing:
unable to sync calendar with external calendar app (OneCalendar)
Is this the first time you’ve seen this error? (Y/N) : Y
Steps to replicate it:
When I link to my Nextcloud account to access the calendar, it appears to link correctly (the correct calendar information appears) but the app fails to sync the data.
This is the output from the log:
webdav] Error: Exception thrown: OCA\DAV\Exception\UnsupportedLimitOnInitialSyncException
REPORT /remote.php/dav/calendars/dougw/momdad/
from 192.168.50.1 by dougw at Oct 25, 2024, 11:10:59 AM
UnsupportedLimitOnInitialSyncException Exception thrown: OCA\DAV\Exception\UnsupportedLimitOnInitialSyncException
/usr/local/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Sync/Plugin.phpLine 121
OCA\DAV\CalDAV\Calendar->getChanges()
/usr/local/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Sync/Plugin.phpLine 62
Sabre\DAV\Sync\Plugin->syncCollection(
"*** sensitive parameters replaced ***"
)
/usr/local/www/nextcloud/3rdparty/sabre/event/lib/WildcardEmitterTrait.phpLine 89
Sabre\DAV\Sync\Plugin->Sabre\DAV\Sync\{closure}(
"*** sensitive parameters replaced ***"
)
/usr/local/www/nextcloud/3rdparty/sabre/dav/lib/DAV/CorePlugin.phpLine 690
Sabre\DAV\Server->emit()
/usr/local/www/nextcloud/3rdparty/sabre/event/lib/WildcardEmitterTrait.phpLine 89
Sabre\DAV\CorePlugin->httpReport()
/usr/local/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.phpLine 472
Sabre\DAV\Server->emit()
/usr/local/www/nextcloud/apps/dav/lib/Connector/Sabre/Server.phpLine 43
Sabre\DAV\Server->invokeMethod()
/usr/local/www/nextcloud/apps/dav/lib/Server.phpLine 370
OCA\DAV\Connector\Sabre\Server->start()
/usr/local/www/nextcloud/apps/dav/appinfo/v2/remote.phpLine 19
OCA\DAV\Server->exec()
/usr/local/www/nextcloud/remote.phpLine 146
undefinedundefinedrequire_once(
"/usr/local/www/nextcloud/apps/dav/appinfo/v2/remote.php"
)
tflidd
October 31, 2024, 3:43pm
2
So just the external application?
I found this bug report with this error:
opened 03:25PM - 13 Oct 24 UTC
bug
0. Needs triage
regression
feature: caldav
28-feedback
29-feedback
30-feedback
### ⚠️ This issue respects the following points: ⚠️
- [x] This is a **bug**, no… t a question or a configuration/webserver/proxy issue.
- [x] This issue is **not** already reported on [Github](https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3Abug) OR [Nextcloud Community Forum](https://help.nextcloud.com/) _(I've searched it)_.
- [x] Nextcloud Server **is** up to date. See [Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/).
### Bug description
OneCalendar users are experiencing errors when syncing caldav calendars with Nextcloud. This used to be working.
As OneCalendar developer I tried to reproduce the problem and for the latest versions of 28,29 and 30 the Caldav response is no longer working correctly when
doing a initial sync.
Hereby an overview of which versions are working correct/incorrect:
- 28.0.9 Correct
- 28.0.10 Incorrect
- 28.0.11 Incorrect
- 29.0.6 Correct
- 29.0.7 Incorrect
- 29.0.8 Incorrect
- 30.0.0 Incorrect
### Steps to reproduce
Sync caldav calendar data:
Request data
```
<sync-collection xmlns="DAV:">
<sync-token />
<sync-level>1</sync-level>
<limit>
<nresults>100</nresults>
</limit>
<prop>
<getetag />
</prop>
</sync-collection>
```
Actual response data (507):
```
<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:exception>Interne serverfout</s:exception>
<s:message>
De server was niet in staat je aanvraag te verwerken. Stuur de hieronder afgebeelde technische details naar de serverbeheerder wanneer dit opnieuw gebeurt. Meer details in de serverlogging, </s:message>
<s:technical-details>
<s:remote-address>172.17.0.1</s:remote-address>
<s:request-id>du8YMujFjQr6HIRmBFm1</s:request-id>
</s:technical-details>
</d:error>
```
### Expected behavior
According to https://tools.ietf.org/html/rfc6578#section-3.11 the caldav server does not need to support limit tag but in that case the following 507 response data is expected:
```
<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:exception>OCA\DAV\Exception\UnsupportedLimitOnInitialSyncException</s:exception>
<s:message/>
<d:number-of-matches-within-limits/>
</d:error>
```
### Nextcloud Server version
28
### Operating system
None
### PHP engine version
None
### Web server
None
### Database engine version
None
### Is this bug present after an update or on a fresh install?
None
### Are you using the Nextcloud Server Encryption module?
None
### What user-backends are you using?
- [ ] Default user-backend _(database)_
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
### Configuration report
_No response_
### List of activated Apps
_No response_
### Nextcloud Signing status
_No response_
### Nextcloud Logs
_No response_
### Additional info
Perhaps there has been a minor update/fix of SabreDav that caused this problem in the newer 28/29/30 versions ?
That sounds like the problem. It’s good to know I’m not alone.
Thanks for digging that up.
I did some further research and testing, and what I’ve found is that there is a bug in later versions of Nextcloud that prevents INITIAL syncing of caldav calendars. Those versions are 28.0.10 or higher, 29.0.7 or higher, and all versions of 30. Calendars where the initial sync was done in prior versions continue to sync correctly in the latest versions.
I was able to confirm this by going back and installing version 29.0.6, migrating all my data and settings, syncing the calendars, then upgrading to 30.0.2 and everything worked correctly. Obviously doing a new install of 29.0.6 each time I want to add a new user with all that entails is a task I don’t want to do every week, but at least I have an option.
Hopefully this will be fixed in the near future.
tflidd
November 25, 2024, 8:00am
5
It would be great to share these details directly with the developers on github. Either in the topic that is already linked (if it is similar enough), or even a new one if you see a regression and you can already name a version.
Seems the error is still there with latest 30.0.5…
Seems to be solved. I have upgraded to Calender 5.0.10 and Nextcloud 30.0.6 and my OneCalender can sync with Nextcloud.
I think it’s solved for OneCalendar because that developper made a change to their code. It’s still an issue for all other CalDav apps.
system
Closed
February 22, 2025, 2:04pm
10
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.