Ok. If there’s anything new about it, please just post here.
No connection possible - E/A-Fehler: Connection to https:// ... refused
CM’s privacy guard doesn’t have any option to disable network access for apps, so this part should’ve worked. @sh3wjie did you try the browser on the same device, through the same ISP?
@rfc2822 : what I found out is that this privacy guard I was referring to seems to be a default in CM which basically is a shell to some underlying functionality.
@untitaker : good point! Yes the CM privacy guard only deals with other data privacy matters and not with any network access issues on the level of actually accessing a network as far as I can see.
Trying to connect to the server using one browser on the same device leads to a “Fehler: Verbindung fehlgeschlagen” message. Using another browser leads to"Webseite nicht verfügbar Die Webseite unter https://posteo.de:8443 konnte nicht geladen werden als: net::ERR_CONNECTION_REFUSED", which basically reads for me quite similar as to what DAVDroid tells me. In both cases the ISP was the same.
Question now is what keeps the browser(s)/DAVdroid App from connecting to the net? So far searching the I-NetI did not give an answer.
Do you have any proxy set up? (check the WiFi settings in Android)
Are you able to access https://posteo.de:443?
Well, checking the proxy settup under Einstellungen -> Drahtlos & Netzwerk -> WLAN -> Netzwerk ändern -> Erweitert reveals that there is no proxy set up (Keiner).
Checking the above mentioned address without the “8” leads to a redirection to https://posteo.de/de.
How do you access the Internet? WiFi only? Can you try mobile network, does it make a difference?
Up to now I only did use WiFi. Changing to mobile network leads to the follwoing situation: both browsers now ask me to punch in my crendtials and after doing so I get a XML file presented that basically contains the error message of my 2nd post.
DAVdroid instead is now desperately trying to load data from the server. At least that is what it is telling me. “Daten werden vom Server abgefragt”.
Update 1: after changing to mobile networks, closing all Apps and browsers and starting anew to set up an DAVdroid account I was able to get past the screen where you type in your access data in DAVdroid an now I have a DAvdroid account! There are 2 things I have to figure out now:
- How to use DAVdroid in detail
- Why doesn’t it work when I am trying to access the I-Net with WiFi?
Just read a few line on the DAVdroid website and did as was described there. I opened the regular calendar and there I saw all my events and appointments that I did enter in the posteo calendar.
PERFECT!!! A dream!
So now I have the proof that it basically works with mobile access. This leaves me with question 2. of Update 1. So somehow something is bend with my WiFi settings. I will look deeper into that.
Ok, so I’ll close this now as it’s not a DAVdroid problem. If you find a solution for your problem, you can post it here anyway of course.
It’s ok with me. Thank you again for your patience and support. I’ll let
you know the outcome of my further investigation.
Mit freundlichem Gruß,
Am 07.06.2015 um 15:16 schrieb rfc2822:
Ok, so I’ll close this now as it’s not a DAVdroid problem. If you find
a solution for your problem, you can post it here anyway of course.
Reply to this email directly or view it on GitHub
It works!!! After another hint from the posteo support I checked my router settings. There I have set up two accesses, a main access and one guest access. So far I was using the guest access to access the net. Checking the settings there showed a possibility to restrict I-Net access only to surfing and mailing. After unchecking the respective check box I tried to use the previously set up DAVdroid account to synch my data and … IT WORKS!!!
So now I am a happy DAVdroid user and posteo customer. What else can I ask for?
Thank you so much for your time and patience in helping me analysing this problem although it was on my side and not on yours. Sorry for any inconvenience.
Just wanted to let you know.
Thanks again. Topic can stay closed.