I tried several alternatives of CalDAV in Evolution, a standard Linux email/calendar client.
Neither the standard calDAV, nor the Thunderbird link works. The ICS one works, but it offers only one-way sync.
Similarly, in Office-365, the browser version: Neither the app-based link, nor the ICS works.
Hi Michael,
Sorry to hear the Team Calendars CalDAV linking isn't working as expected!
The first thing I'd check is if your site has a context path at the end of the base URL (e.g. www.yoursite.com/confluence). If it does, there are some modifications that need to be made to the proxy to make the CalDAV connection (See the Confluence context path section of Subscribe to and from Team Calendars).
Also, you can check the rest of the notes in the Troubleshooting section at the end of Subscribe to and from Team Calendars, which addresses common connectivity issues.
If neither of these solve the issue, could you provide more detail on what happens when you try to use the calendar in Office 365 and Evolution? (e.g. At what step does the failure happen? What does it look like? Is there an error message?)
Thanks!
-Zak
The calendar backend servicing “Unnamed” encountered an error. The reported error was “Bad file format.”.
Failed to get properties: HTTP error code 200 (OK): The server responded with an HTML page, which can mean there’s an error on the server or with the client request. The used URI was: https://mgrivas@confluence.bbpd.io/
Failed to connect calendar “CalDAV : Unnamed”Given URL “https://mgrivas@confluence.bbpd.io/” doesn’t reference CalDAV calendar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.