Owncloud 9.1.1-1.2 and Davdroid (1.3.1-ose) CalDAV-CardDAV

Hi friends,
I've just installed on my VPS Debian jessie Owncloud deb packaged from https://download.owncloud.org/download/repositories/stable/owncloud/
I've added on absolute domain path this .htaccess entries:

Redirect 301 /.well-known/carddav /owncloud/remote.php/carddav
Redirect 301 /.well-known/caldav /owncloud/remote.php/caldav

I've uploaded calendar and address book correctly, but if I try to connect with Davdroid obtain:

Couldn't find CalDAV or CardDAV service.

With the 8.x Owncloud all works fine, It is still feasible with the new Owncloud release?

many thanks!


there is a documentation about the .well-known URLs available here explaining most stuff about these:


Hi @RealRancor and thanks for your help!
I made these changes:

Redirect 301 /.well-known/carddav /owncloud/remote.php/dav
Redirect 301 /.well-known/caldav /owncloud/remote.php/dav

And now if I point my browser to https://example.com/.well-known/carddav or https://example.com/.well-known/caldav
it ask me owncloud username and password but if I set Davdroid to https://example.com/ it tell me again "Couldn't find CalDAV or CardDAV service."

I've try also: https://example.com/owncloud/remote.php/dav/principals/username with the same result.

I've read your tutorial, where I'm wrong? :slight_smile:

many thanks again!

Works for me here with davdroid and a current oC install so you're most likely have configured the redirects wrong or pointing them to the wrong URL.

The important part you can test is to open:




in your browser. After you get asked for your username and password there you need to be redirected to a page stating something like:

This is the WebDAV interface. It can only be accessed by WebDAV clients such as the ownCloud desktop sync client.

If that is working it might be possible that your *DAV interface / setup is not working completely / fully. For that we have a FAQ thread available (especially the litmus part there can help you to check your environment):

I'm very afraid!
All this mess was generates by The wrong password!
Infact, Davdroid does not communicate if the credentials are incorrect but only the above generic message.

Everything is resolved now, sorry If I bothered you!

And thanks for your help!

1 Like

Really? Thats quite bad from DAVdroid side. Maybe report that issue to the app developer so he can improve the message?


The detection process is quite complicated, and it's not possible to tell whether the single steps return 401 for a good reason (for instance, because well-known URLs are not configured or because the user-given URL returns 401, but the automatically detected ones work) or because of the wrong password. We have thought over the detection process and how to show errors many times, and I hope that it's quite a good solution now. When you click on "View logs", you see every request + what the server returns, so all the 401 messages from the server should be a good hint that the password is wrong. If you have specific ideas on how to improve that, please let us know.

Btw, I'm not a "he" :wink:

1 Like