Thanks for your response. I’m on a local network. Whenever I need to sync, I turn on WiFi and disable mobile data. This is the way I’ve been syncing successfully for some years, until this issue started to occur. I’m able to access my Nextcloud server’s web interface, I can also refresh the calendar, as I said in my post. And certainly I can reach the CalDAV URL from my browser (I get an error about the GET method not being supported, as expected).

@rfc2822 said in Couldn't find CaldDAV or CardDAV service. But works on Thunderbird.: https://nextcloud.****.ovh/remote.php/dav/principals/users/arthur/ Firewall has being deactivated, on server logs I do have this entry : [Fri Apr 19 07:22:07 2019] [error] [client --.–.--.–] [host nextcloud.____.ovh] AH01630: client denied by server configuration: /homez.270/ljv/Nextcloud/config But I’m not sure wether this is related to my connexion attempt with DAVx, timestamp doesn’t seem to fit, and anyway other services are working fine, my nextcloud application works great, the only issues I have is with the browser client ( icons missing with https ) and DAVx. The URL https://nextcloud.****.ovh/remote.php/dav/principals/users/arthur/ is accessible in a browser, and here is the answer : “This is the WebDAV interface. It can only be accessed by WebDAV clients such as the Nextcloud desktop sync client.” I’ve got some issues with Nextcloud on this server anyway going through https, and it seems some other people have had the same issues with OVH shared hosting. I don’t expect this problem to be solved anytime soon. But what tickles me is that things are working perfectly fine with Thunderbird with Cardbook plugin installed. With the address : https://nextcloud..ovh/remote.php/dav/addressbooks/users/arthur/contacts/ for the addressbook and https://nextcloud..ovh/remote.php/dav/calendars/arthur/personal/ for the calendar. So I was thinking that if I could access DAVx settings and setup directly those addresses that should work, isn’t it ?

@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?

@Yuniru i’ve you solved your problem ? I’ve the same and don’t find an issue… I don’t know if it’s server error or davx5 problem !

@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

@rfc2822 said in Sync stopped working, nothing to go by in terms of debugging: @MadGoose Thanks for sharing your solution! So, your problem was basically firewall settings which were incompatible with the way how Android detects Internet connection, so that synchronization was never started (not only of DAVdroid, but all account types). Well, not quite: DAVDroid synced after a reboot for a certain time - just until i got killed (by the system?). It just was not restarted to continue synchronization. All other apps continued their “synchronization” - but I guess all other apps I use do not rely on the synchronization framework by Android but use other methods to restart after having been killed by the system. But for sure it was no DAVdroid-related problem but the - in my opinion - not too clear documented (well, where could that be found?) behavior of synchronization framework and “internet connectivity detection”. Cheers MG

@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?

@marco said in Cannot add new account: How can I resolve with the mobile data? I mostly use it instead of wifi. It’s not a DAVdroid problem. You can see the proxy in Android settings / Mobile data / Access points (APNs) / your access point / Proxy. If this proxy doesn’t work properly, please contact your provider or just delete the proxy setting (and restart DAVdroid / the system afterwards), if you’re allowed to do so (may be restricted). Same problem as here, for instance: https://forums.bitfire.at/topic/422/certpathvalidatorexception-but-my-domain-is-a-on-ssllabs

@devvv4ever Thanks for the answer ! I’ve adjusted the ciphers the server supports and now it’s working flawlessly Patrick

Thank you, that was the solution. This works best for me, better than auto. ssl_ecdh_curve secp384r1:prime256v1;

Already open again in okhttp: https://github.com/square/okhttp/issues/3308