Suddenly it worked.
Can't log to ownCloud
Basically I can’t log to ownCloud with davdroid. It stays this way for minutes ( http://i.imgur.com/W7urx2h.png ) until I see this message: “I/O Error Socket is closed”.
It works if i try with other similar apps (like CalDAV-Sync). It also works on PC (GNOME/Evolution).
OwnCloud 8.1.1 on Arvixe
DAVdroid 0.8.3 from F-Droid
Android 5.1.1 (Cyanogenmod)
I also provided a test account
Did you have a connection and correct sync in the past?
Yes. It stopped working roughly less than a month ago.
The strange thing is that downgrading davdroid doesn’t solve the problem. Still other (closed source) apps similar to davdroid do work flawlessly.
Its a weird thing… Normal OC works pretty good, only the hosted ones seem to make problems.
Other apps might have some workarounds for specific providers. We avoid it where we can, because they are a pain to maintain - also we’ve never had time to test owncube and arvixe (which seem to have the same backend, because at both providers the “Socket closed” error appeared at the same time). Currently I don’t think this has something to do with DAVdroid, but we will test it ourselves soon to get more details on it!
@h3r0n What happens if you put a proxy such as mitmproxy inbetween?
I wonder whether this could be caused by an incorrect
I am a bit confused.
Your domain is http://owncloud.h3ron.com.
But there is a DNS SRV record for _carddavs._tcp.owncloud.h3ron.com (also for _caldav) pointing to https://caique.arvixe.com:2080/
To me it seems, that on caique.arvixe.com (126.96.36.199) no process is listening on port 2080.
But your owncloud server is running on owncloud.h3ron.com:80 (188.8.131.52:80), right?
@h3r0n That’s exactly the problem. The SRV records points to a service that doesn’t run, this the timeout:
$ host -t SRV _carddavs._tcp.owncloud.h3ron.com _carddavs._tcp.owncloud.h3ron.com has SRV record 0 0 2080 caique.arvixe.com. $ nc caique.arvixe.com 2080 Ncat: Connection timed out.
Please contact your hoster and include this issue’s URL.
I’ll close the issue for now because it’s not a DAVdroid problem. If there’s anything new, please feel free to post again nevertheless.