3. Can't configure DAVDroid account with Synology

Can't configure DAVDroid account with Synology

  • A

    Hi,

    So, first of all, thanks for the app. Though, for now, I do not have the pleasure of using it, I appreciate the work.

    So, my problem is the next : I can’t seem to be able to correctly connect to my CALDav server with DAVDroid.

    My CalDav server is a Synology, and WebDav/CalDav is correctly activated, according to DSM.
    I recently bought a domain name and a proper certificate (gandi) for my synology.

    So, I had to create a calendar with my syno, located on the web repertory.

    When I use the direct adress of my NAS (meaning, just the domain and the port, not the repertory), i get this : “missing capabilities invalide dav response : couldnt determine principal path (rfc 5397)”.
    Otherwise (with the path to the calendar) , I get this : missing capabilities invalide dav response neither caldav nor carddav available…

    So, I tried to look for some explanations, but I didnt find any, which is why I come to you for help.

    Best regards,
    TheDoctor

    0
  • R
    developer

    We couldn’t test DAVdroid with Synology successfully yet. Can you please provide a test account that is working with other clients and send it to play@bitfire.at?

    0
  • A

    Hi,
    I’ve got the same error:

    Missing capabilities: Invalid DAV response: Couldn't determine principle path (RFC 5397)

    It’s not with Synology but with Baikal on my webhoster.
    It works with http, but fails when using https.
    If you want to try, I made a test account. Due to issues with apache PHP via CGI, only basic authentication works:
    Settings:

    http url: dav.bamax.nl/card.php
For correct certificate use for https:
https url: cp.mijnreus.nl/ssl/81//www.s1007571-15164.mijnreus.nl/dav.bamax.nl/card.php
username: test
password: test
Enable preemptive authentication
    0
  • A

    I don’t have a lot of time, but I will first have to run some test on other clients. It’s an account with access to WebDav/CalDav on my Syno you need, right ? If so, no problem. I’ll do my test, and then, I’ll send it to you.

    0
  • A

    Hi,
    Any help is welcome, but don’t feel rushed by me. I’m using your issue to add information about mine.

    I was checking whether my issue was already posted before writing a new one. Yours seemed similar due to the error message.
    Since rfc2822 was asking for more information and a test account, I thought it might be helpfull to make one for my issue as well.
    Maybe our issues are related and my test account can help solving them.

    0
  • A

    Hi,

    Little update 🙂
    Sorry, it’s a bit late, but I didn’t had time to do it before.

    I ran some test, and it’s working fine on Thunderbird (with Lightning), but I still got the same error with DavDroid.

    0
  • R
    developer

    After testing a Synology device, I found out that for some reason, the current-user-principal is not returned, so that auto-detection of resources is not possible (and DAVdroid only supports resources which are automatically detectable).

    > PROPFIND /CalDav/Testuser/ HTTP/1.1
> Authorization: Basic XXXXXX
> User-Agent: curl/7.32.0
> Host: xxxxxxx:5006
> Accept: */*
> Depth: 0
> Content-Length: 73
> Content-Type: application/x-www-form-urlencoded
> 
* upload completely sent off: 73 out of 73 bytes
< HTTP/1.1 207 Multi-Status
< Date: Sat, 29 Mar 2014 21:17:51 GMT
* Server Apache is not blacklisted
< Server: Apache
< Content-Length: 344
< Content-Type: application/xml; charset="utf-8"
< 
<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:" xmlns:ns0="DAV:">
<D:response xmlns:lp1="DAV:">
<D:href>/CalDav/Testuser/</D:href>
<D:propstat>
<D:prop>
<lp1:current-user-principal><D:unauthenticated/></lp1:current-user-principal>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:multistatus>

    I have looked for a way to report/discuss that with Synology, but I couldn’t find any way to contact them electronically except the contact form, which I can’t use because I actually don’t have an own Synology device and can’t register without serial number etc.

    Follow up: https://twitter.com/davdroidapp/status/450018678957158400 & waiting for a response…

    0
  • R
    developer

    I have also read that it is possible to install OwnCloud (maybe even other CalDAV/CardDAV servers?) to Synology devices, which would work around this problem.

    0
  • R
    developer

    Also see https://twitter.com/davdroidapp/status/471652913082023936

    Closing this for now, please report further problems directly to Synology.

    0
  • A

    Any news following this issue ? Did you received any feedback from Synology?
    I’m actually in a similar situation: bought the davdroid app but can’t get it working due to this Synology issue.

    Regards,

    0
  • R
    developer

    DAVdroid 0.6.12 now supports Synology, we have changed the detection code so that it doesn’t require current-user-principal support.

    Configuration details: https://davdroid.bitfire.at/configuration

    0
  • A

    Thanks a lot, it will be useful 🙂

    I wish Synology had corrected the bug on their side, though.

    0

  • @TheDoctorII yes, would have been a lot easier if they did…
    @henry-nicolas Can you maybe test the new version 0.6.12 (see https://davdroid.bitfire.at/configuration for configuration details) and tell us if it works for you?

    0
3rd-party issue 281 enhancement 189
Log in to reply