Thanks for the extremly fast answer ! I’ve played a little bit with the contacts app. The option is hidden in the filter settings in the contacts app. There I could switch on the DAVdroid account visibility.
For me the issue is solved. Thanks a lot.
CalDAV + WEB.DE/GMX not working at the moment
-
After many hours of trial and error i finally found a solution to set up CalDAV with WEB.DE using DAVdroid.
All mentioned methods described on the WEB.DE support website did not work out.So how to setup CalDAV with WEB.DE ?
-
Go to https://caldav.web.de/your_adresse@web.de using your webbrowser
-
Enter your email adress and your password in the upcoming dialogbox
-
Copy the link “Home Collection” at the bottom of the site
It should look like this:
https://kalender.web.de/begenda/dav/many_numbers_and_letters -
Add new account in DAVdroid and use “Login with url and username”
For the Basis-URL use:
https://kalender.web.de/begenda/dav/many_numbers_and_letters/calendar
(!! Note !! that “/calendar” was added to the end of the link)Enter username and password next.
-
After choosing and accepting an account name you should see “Mein Kalender” in the account.
Thats it.
@administrators
It would be nice if you could add this information to the service specific information -
-
Thanks for the info.
Same for GMX.
Their server settings (SRV records, redirects etc.) are now totally broken (no
.well-known, SRV/TXT records point to broken/begenda/dav/userspath which always returns 403). So I don’t know whether we should update this in the documentation, because it looks like a (temporary) error on their side.Unfortunately, we have never received any response from GMX upon our contact requests, so I guess chances are not too high this time.
-
-
@Kaputta said in CalDAV + WEB.DE/GMX not working at the moment:
@rfc2822
Did you change the title?Yes, mainly because the same problem occurs for GMX. GMX and web.de seem to share the same CalDAV/CardDAV system.
I mean no problem but now it sounds like that also WEB.DE is not working.
Exactly, that’s the problem. It has wrongly configured SRV/TXT records, so that clients like DAVdroid which implement the corresponding standards correctly can’t find the resources anymore.
$ host -t SRV _caldavs._tcp.gmx.at _caldavs._tcp.gmx.at has SRV record 0 1 443 kalender.gmx.net. $ host -t TXT _caldavs._tcp.gmx.at _caldavs._tcp.gmx.at descriptive text "path=/begenda/dav/users/" $ curl -nvX PROFIND https://kalender.gmx.net/begenda/dav/users/ … < HTTP/1.1 403 Forbidden -
Ok, so it is wrongly configured by GMX/WEB.DE.
But does that mean that i should be worried now because of data loss or something? -
@Kaputta said in CalDAV + WEB.DE/GMX not working at the moment:
Ok, so it is wrongly configured by GMX/WEB.DE.
But does that mean that i should be worried now because of data loss or something?No, the data will always remain on the server until you (or someone else) explicitly delete it from there.
-
Seems like it really was a temporary server problem. In our tests, everything is working again.
-
I tested it, too. It’s working as we wrote it on our configuration page for GMX and web.de.
-
I just tested it too. Now it really works as it is written on your configuration page. More than easy now…
Maybe they read about the problem here, too.Anyway, thanks for help.
-
For me, it seems the “temporary server problem” has reappeared about 1 or 2 weeks ago.
Since then server replies “Service” upon calling
https://kalender.gmx.net/begenda/dav/mail@address.de/calendarAnybody to confirm these issues?