@enr00ted Maybe other apps use other CalDAV methods (for instance, only PROPFIND instead of the better-suited REPORT calendar-query). If these clients are open-source, you can have a look at the source code – would be interesting.
Synology DSM 7: CalDAV not syncing anymore with "modern compatibility" mode
NeverEatYellowSwissSnow last edited by rfc2822
Since Synology DSM 7 RC has been released recently I mentioned that DAVX5’s CalDAV is not syncing anymore when TLS/SSL Profile level is set to “Modern compatibility”. To make it sync again it is necessary to set the level to “Intermediate compatibility”.
In DSM 6.x, DAVX5 synced without any issues with “Modern compatibility” mode. So it seems Synology has changed something within security mode settings between DSM 6 and DSM 7.
CardDAV does not have this issue, it’s working fine as before with “Modern compatibility” mode.
It would be nice if this could be fixed so we can use “Modern compatibility” mode again.
NeverEatYellowSwissSnow last edited by NeverEatYellowSwissSnow
@rfc2822 I already am on DAVx5 version 3.3.11. I’m using CAlDAV by using a https connections from my android 10 phone to my Synology which runs DSM 7 RC and the Synology Calendar application.
@nevereatyellowswisssnow Is the Synology accessible publicly so that I can have a try? And/or do you have a list which protocols/ciphers are “modern compatibility”?
NeverEatYellowSwissSnow last edited by
@rfc2822 I could give you a temporarly account. Can I pm you?
Maybe this hint is helpful to you, only TLS 1.3 for “modern”:
@nevereatyellowswisssnow TLS v1.3 shouldn’t be a problem. So yes please provide a test account. I’d also need the DAVx⁵ debug info, which contains information like the Android version.
@rfc2822 Thanks for the chat. We have found out that this problem seems to be on the server side (and should affect all other clients, too). As a workaround, you can set to “Intermediate compatibility”. This has been reported to Synology in ticket #2818867.
We’re received this reply from the Synology dev team:
Thank you for the listed points at the point.
The behavior is known to our development and a solution regarding this is being worked on.
Unfortunately, I cannot tell you from our side when exactly there will be a solution, as we have no insight into the development processes.