No option to select CalDAV/Apple #6

Activity

1. PrinzKenny1

   added

   bugSomething isn't workingSomething isn't working

   on Aug 12, 2026
2. pullfrog commented on Aug 12, 2026

   

   pullfrogbot

   on Aug 12, 2026 – with Pullfrog

   Contributor

   More actions

     ^{｜ Build this ➔ ｜ Make a plan ➔}
3. shockalotti commented on Aug 18, 2026

   

   shockalotti

   on Aug 18, 2026

   Contributor

   More actions

   Thanks for the report! We've tried to reproduce this on a few fresh instances and CalDAV always shows up as an option, so this looks like it's specific to what's happening on your instance rather than a general bug in the CalDAV feature — we also just did an end-to-end test (connect → discovery → free/busy → booking write-back against a real CalDAV server) and it all worked correctly.

   A couple of things that would help us pin it down, if you're up for it:

   1. What does your Calendar settings page show right now? Does CalDAV appear anywhere — either as an existing connection (with a "Disconnect" button) near the top, or as a "Connect" option further down? A screenshot of the full page would help.
   2. Container startup logs, if you still have access to the instance:

      docker logs <your-container-name> 2>&1 | grep -i "calendar\|caldav"
      

      Looking for CalDAV calendar configured (fine) vs caldav: init failed (tells us exactly what broke).
   3. Which image tag is actually running:

      docker inspect <your-container-name> --format '{{.Config.Image}}'
      

   That said — if you'd rather not dig through logs, the fastest path back to a working state is probably to tear down the container/volume and redeploy fresh from the latest image. Given we can't reproduce this on new instances, whatever state your instance is in looks like a one-off rather than something everyone hitting the latest release would see. Happy to keep digging into root cause from the diagnostics above if you're able to grab them first, though — that'd help us catch a real bug if there is one under here.
4. PrinzKenny1 commented on Aug 21, 2026

   

   PrinzKenny1

   on Aug 21, 2026

   Author

   More actions

   Hm, surprisingly it works now, even though we didn't change anything. Maybe a restart of the application fixed it, i'm not sure. But when i first started it and signed up as the initial user I also didn't get the owner role so maybe something hiccuped. Can be closed now.
5. shockalotti commented on Aug 23, 2026

   

   shockalotti

   on Aug 23, 2026

   Contributor

   More actions

   AWESOME! Less work :) Ha ha. Closing now.
6. shockalotti

   closed this as completedon Aug 23, 2026