Ipad | Calendar does not sync, contacts do

Issues
1

Issue Description

Using v0.16.11 stalwart, the ipad calendar does not sync with Stalwart. Contacts do. I have not tested email syncing (because I dont intend to use email syncing on my ipad).

I can confirm the calendar syncs on android with davx5

I am not tech savvy and do not know how I can provide more information to debug this.

Expected Behavior

Works as expected

Actual Behavior

Doesn’t work

Reproduction Steps

Configure the ipad to use stalwart server.

Use the email as the login and the login password (not an app password).

Relevant Log Output

N/A

Stalwart Version

v0.16.x

Installation Method

Binary (Linux)

Database Backend

PostgreSQL

Blob Storage

PostgreSQL

Search Engine

PostgreSQL

Directory Backend

Internal

I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.

on

I have searched this support forum (open and closed topics) and confirm this is not a duplicate.

on

I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.

on

2

Here are some troubleshooting steps to help narrow down why your iPad’s calendar isn’t syncing while contacts are.

The most common cause is a misconfigured CalDAV account on iOS. iOS uses separate account types for CardDAV (contacts) and CalDAV (calendar), so it’s entirely possible that contacts were set up correctly while the calendar account was not added, or was added with the wrong server URL.

Here’s what to check on your iPad:

  1. Verify you have a CalDAV account, not just a CardDAV one. Go to Settings > Calendar > Accounts (not Settings > Contacts > Accounts). Make sure there is an account there pointing to your Stalwart server. If it’s missing, you need to add it separately as a CalDAV account.

  2. Use the correct server URL. When adding the CalDAV account manually, use either:

    • The autodiscovery endpoint: https://your-server/.well-known/caldav
    • Or the direct path: https://your-server/dav/cal/<your_username>

  3. Use your full email address as the username and your regular login password (as you already do).

  4. Check for SSL/TLS issues. If your server uses a self-signed or improperly configured certificate, iOS will silently refuse to connect. Since CalDAV and CardDAV may negotiate certificate trust differently, contacts could work while calendar does not.

To generate server-side log output for debugging, you can temporarily raise your Stalwart log level (in the WebUI under Settings > Server > Logging) and then attempt a calendar sync from the iPad to see what requests are arriving and whether any errors are returned.

Documentation reference: Stalwart CalDAV / Calendar docs

This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong.

3

We would need logs to diagnose the issue. Try setting the log level to TRACE and provide the raw HTTP requests when Apple Calendar is interacting with Stalwart.

4

I actually reported this issue like nine months or so ago on github, back when one could make issues there. Have you never been able to replicate this on your end?

I will try to get these logs to you, but I have a feeling they aren’t going to reveal much.

5

I managed to solve this issue.

As it turns out (stupidly). Apple allows you to put in https://sub.domain.tld, when it really should just be sub.domain.tld without the https://

Don’t ask me why they allow this. It works without https://

Since I don’t have port 80 open.. yeah enough said.