Hello, 2019-11-30 09:49:10 10217 [HttpClient] <-- HTTP FAILED: java.net.ConnectException: Failed to connect to /192.168.0.100:8443 2019-11-30 09:49:10 10217 [ui.setup.DavResourceFinder] PROPFIND/OPTIONS on user-given URL failed There is no connection to 192.168.0.100:8443 from your Android device, so it’s probably a connectivity problem (firewall, …). Does it work when you access the URL from your Android browser?

In DAVx⁵ 2.6, there will be a warning when there’s no validated Internet connection. So when you see this, you will know there’s something wrong with the connection:

Thanks for the explanation. I guess it was a problem with Baïkal after all. I have “fixed” it by switching to DAViCal. Very intimidating documentation & UI, but almost nothing needed to be configured and it Just Worked. So, DAViCal is the server DAVx5 syncs everything on Android on the desktop I use vdirsyncer & khal for the calendar only (vdirsyncer still refuses to sync my contacts), and SoGo connector for contacts on thunderbird. It’s been a long day.

@pescepalla Thank’s a lot! Your solution workes on my Xiaomi 5s plus with nextcloud on an own server in my LAN and using DAVx⁵ for synchronisation after I’ve searched two days where the problem comes from. By accident I installed nextcloud 15 and deleted and reconfigured DAVx⁵’s account. So I was not clear if it’s a nextcloud or a DAVx⁵ problem. Finally I found out in the nextcloud logs an entry webdav Sabre\DAV\Exception\NotAuthenticated: No public access to this resource., No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured Still misleading, I checked everything related with passwords and accounts. Android doesn’t sync if it can’t connect to a working captive_portal_https_url, even if you choosed in the internet access settings for your network not to ask the question anymore and the internet works as far, as possible in China. And that with LineageOs. As many people not only using their own local nextcloud installation inside a LAN that is kind of a strange setting with Android in China at least. Thanks again, @pescepalla !

There are no errors.

Confirm the regression too. got I9300 with replicant 6.0 0003 Long time ago, add account to davdroid installed from f-droid. Following upgrade from f-droid repository and work well with latest version of Davx5. But have to reinstall os, reinstall Davx5, and cant register new account with the same stack of error when trying this url: https://domain.tld/baikal/html/dav.php And when trying https://domain.tld/baikal/html/dav.php/calendars/user/work/, Davx5 print crash popup. Install an old davdroid apk and work well. Work well with Thunderbird too for calendar and Inverse SOGo Connector for address book. Not a server side problem. Thanks a lot for this software ! Happy to use it daily.

@devvv4ever Sorry for the delay in responding. I used the IP instead of the name, but I get the same result. Here is the log davx5-info.txt Any thought will be greatly appreciated.

@mazeiva I don’t know. We’d have to know the actual reason why it’s not working to say why it’s working on other devices. Maybe you can find something in your server (for instance, do the DAVx⁵/browser requests make it through to the server) and/or firewall logs?

Is it possible that you have multifactor turned on for Nextcloud? If so, you can create a one-time password in your NC settings.

@moonlies Did you use an app password for the first account? In this case, the app password would stay valid even when the main password changes.

@rfc2822, may application was moved back to the old server. now all cipherspecs are available again, nothing was changed on the old server ! Only my Nextcloud was first migrated to a newer server, there Nextcloud was updated from 13.0.7 to 14.0.4, the problems occurred. now the Nextcloud has been moved back to the old server. But now it is still Nextcloud 14.0.4 ! Could it be that it’s not the cipherspecs but the old DavDroid has a problem with Nextcloud 14.0.4?

Hello I’m running owncloud 10.0.0.4 on a slow system and requesting a contact sync >450 entries (with pictures). As far as i’m able to judge the client is requesting the whole addressbook and after timeout exception it want to retry a request of 10 entries. At this time the server is still running at 100% cpu duty collecting the previous request. That leads to a bunch of apache instances on server-side which freezes the system for a couple of minutes and the client isn’t getting it’s requests within it’s (too short and unconfigurable) timeout. For reference: setting the timeout to 180sec would very likely fix this problem

I had the same problem where I was able to enter my account in davdroid and Davdroid itself successfully found all my calendars, however none of them would sync with the phone’s calendar programs (both the native calendar and e-tar). Seems like a bug / change in android 7 broke calendar syncing. I was unable to get davdroid to work for months, however now that there’s a new DAVx5 client I decided to try it. They fixed it! The link is broken in the fdroid repo’s BTW, however I managed to install davx5 manually and everything’s working. So if anyone else has the same issue, give the new davx5 a shot!

@rfc2822 No, I can’t browse to the server from any device connected via Internet. On my local LAN the web pages serve up fine , and my Thunderbird calendar on a machine on the LAN will sync to the calendar on the Pi. However, I can ping the server successfully from the internet - both via direct IP address and the sub-domain name. I do have a local DNS server running on another RPi on my LAN - Pi-Hole - to block ads. The Pi-hole logs don’t indicate that traffic to the sub-domain are blocked. But the DNS blocking would be happening from DNS resolution requests from devices that are connected on the LAN, not traffic coming into the LAN.

Hi, Thanks, it’s also the issue I was having. Instead of giving internet access to uid 1000, I just did “settings put global captive_portal_mode 0” (recent android) Agreed it would be useful to add this in the FAQ

I had the same problem with DAVdroid and Posteo and found the cause, so I wanted to share this: I am using LineageOS 14.1 on a GT-i9300 (Samsung Galaxy S3) in Austria, my mobile telecommunications operator is A1. As far as I remember I never edited the APN settings after setting up my phone, so I suspect that the default APN for this operator is wrong (sure it’s possible I edited the settings and can’t remember it…). The active APN was named “live!” and used a Proxy – and I ran into the problem described here. After changing the APN to “A1” (settings with the name of my mobile telecommunications operator and without a Proxy) I can’t reproduce this issue. You can find all APN settings included in LineageOS on GitHub. BTW, thanks for DAVdroid!!

emmmm. I meet this problem again.

@cedricoola Unfortunately not. I am quite certain that the synchronization of the CardDav server only works if you have a proper port forwarding and direct access via a fixed IP address and that this is why I can not access it via app or browser.

2017-11-05 19:35:13 16235 [HttpClient] --> PROPFIND http://192.168.1.100:8008/addressbooks/users/LW/addressbook/ … 2017-11-05 19:35:43 16235 [ui.setup.DavResourceFinder] PROPFIND/OPTIONS on user-given URL failed EXCEPTION java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) The connection to 192.168.1.100:8008 has timed out. This is probably a networking/server problem. You may try to reach the server with your mobile device’s Web browser first.

2017-08-10 16:10:35 4684 [HttpClient] --> END PROPFIND (290-byte body) 2017-08-10 16:11:05 4684 [HttpClient] <-- HTTP FAILED: java.net.SocketTimeoutException: connect timed out 2017-08-10 16:11:05 4684 [ui.setup.DavResourceFinder] PROPFIND/OPTIONS on user-given URL failed EXCEPTION java.net.SocketTimeoutException: connect timed out There was a timeout. This is a connectivity problem. Did you try another network? Can you access the URLs with your browser on the mobile device? Did you try another connection type? Are there any firewalls which could block the access?