This issue has been fixed in Kolab. It sends the color now with a # prefix. However, DAVdroid behaviour could be improved by not expecting the #.
CalDAV and CardDAV on separate ports (Synology), DNS discovery not working
-
Not sure if that’s DAVx5 problem, but anyway. DAVx5 2.5.3-ose.
I’m using Synology Calendar app and CardDAV server. They are accessible on domain.com:443/caldav/users/username/ and domain.com:8443/addressbooks/users/username/, resp. I’d like to have them under one account.
Problem 1: I can’t edit .well-known addresses. It might be possible through editing system nginx config templates, but I have no idea how.
Problem 2: I tried to use DNS records. So I set up:- _carddavs._tcp SRV 10 20 8443 domain.com.
- _caldavs._tcp SRV 10 20 443 domain.com.
- _carddavs._tcp TXT /addressbooks/
- _caldavs._tcp TXT /caldav/
Records have propagated, yet it does not work with DAVx5 — if I add account with domain.com, it finds only carddav server. What else can I try?
Edit: looked through logcat. DAVx5 checks .well-known and finds carddav through domain.com:8433, but I don’t see any attempt to look at DNS records.
-
Hello,
Please post the logs of the (unsuccessful) discovery.
-
Sent logs to support@davx5.com.
-
@Alex-Fullmoon Thanks for the logs! As you can see in the logs, DNS discovery is done as expected (:8443 for CardDAV, :443 for CalDAV; search for
._tcp
or SRV records in the logs), but the server redirects to https://localhost:8443, which can’t work.Do you know why your server redirects to localhost?
-
Ok, found cause of problem. It was because of malformed TXT record, it should be “path=/caldav/” and “path=/addressbooks/”.
Sorry for bothering you. -
Thanks for the update! Good to know that SRV records are working with Synology, too (as they should).