Podłączanie kalendarza CalDAV
CalDAV is an open standard protocol for accessing calendar data over the internet. Many calendar services support it, for example Fastmail, Nextcloud, SOGo, Radicale, Baikal and Synology Calendar.
Steps
-
Gather your CalDAV details
Before connecting, you need to find your CalDAV server information. This is typically found in:
- your provider’s help documentation,
- your account settings page,
- the email from your provider when you signed up.
You’ll need:
- Server address – often the bare server address is enough, e.g.
cloud.example.com, and we look up the exact calendar path ourselves. Otherwise enter the full CalDAV URL, e.g.https://example.com/dav. - Username – usually your email address or account username
- Password – your account password or an app-specific password
Settings for Fastmail, Nextcloud, SOGo and Synology Calendar are listed below under Popular CalDAV providers.
-
Go to the Calendars page
In SyncMyDay, click Calendars in the menu, or go straight to the Calendars page.
-
Click “Other CalDAV”
Find the Other CalDAV tile and click it.
-
Enter your CalDAV credentials
Fill in the form with the details you gathered:
- Server address – the server address or the CalDAV URL itself, for example:
https://caldav.fastmail.comhttps://nextcloud.example.com/remote.php/davcaldav.example.com(we’ll addhttps://automatically)
- Username – usually your email address (e.g.
you@example.com) or username - Password – your account password or app-specific password (if your provider requires it)
- E-mail (optional) – shown with the calendar if it differs from the username
If you type an e-mail address of a provider that has its own form, we offer to switch to it. For an address on a custom domain, we try to look up its CalDAV server and fill in the address if you haven’t entered one yet.
- Server address – the server address or the CalDAV URL itself, for example:
-
Let SyncMyDay find your calendars
Click Find calendars. SyncMyDay will:
- verify the server is reachable over HTTPS,
- authenticate with your credentials,
- discover available calendars.
This usually takes a few seconds.
-
Select a calendar
You’ll see a list of the calendars available on your CalDAV server. Pick the one you want to sync, adjust its name if you like and click Complete Setup. You can switch to another calendar later in the calendar’s detail via Edit.
Typical calendars you might see:
- Personal – your main calendar
- Work – work-related events
- Family – shared family calendar
- any custom calendars you’ve created
A calendar marked Read-only can only be the source of a one-way rule. Blockers can’t be written into it, and it can’t be used for two-way sync.
-
Connection complete
Your CalDAV calendar is now connected and ready to use.
Popular CalDAV providers
Fastmail
Popular email and calendar service.
- Server URL:
https://caldav.fastmail.com - Username: your Fastmail email address
- Password: your Fastmail password (or app password if 2FA is enabled)
Nextcloud
Self-hosted or managed Nextcloud.
- Server URL:
https://your-nextcloud.com/remote.php/dav - Username: your Nextcloud username
- Password: your Nextcloud password or app password
SOGo
Open-source groupware server.
- Server URL:
https://your-sogo-server.com/SOGo/dav - Username: your SOGo username (often
email@domain.com) - Password: your SOGo password
Synology Calendar
Synology NAS Calendar package.
- Server URL:
https://your-nas-address.com:5001/calendar - Username: your Synology DSM username
- Password: your Synology DSM password
Make sure the Calendar package is installed and CalDAV is enabled in Calendar settings.
Troubleshooting
“We can’t reach the server …” or “The server … has no valid certificate”
Check these common issues:
- Server address: we add
https://automatically. If the bare server address isn’t enough, enter the full CalDAV URL from your provider’s documentation. - Trailing slashes: try with and without a trailing slash (
/) at the end. - Port number: some servers need an explicit port (e.g.
:8443). - Certificate: we only connect over HTTPS, and for your security we never connect to servers with an invalid certificate (self-signed included). If you’re self-hosting, give the server a valid certificate.
- Internet access: a server you can only reach from an internal network or over VPN can’t be connected.
“CalDAV rejected the sign-in details.”
Common causes:
- incorrect username or password,
- you need to use an app-specific password (if 2FA is enabled),
- wrong username format (try with and without
@domain.com), - account locked or disabled.
Solution: double-check your credentials, generate an app-specific password if needed, or contact your provider.
“We didn’t find any calendar. Please check the server address.”
If no calendars are found:
- Enter the full CalDAV URL from your provider’s documentation instead of the bare server address.
- Make sure you have at least one calendar in your account.
- Check that the calendars aren’t hidden or archived.
- Try creating a test calendar in your provider’s web interface.
Sync stopped and I got an e-mail
When the stored password stops working, SyncMyDay pauses the connection and e-mails you. Open the calendar on the Calendars page, click Edit, fill in New password (optional) and click Save changes.
Sync is slow
CalDAV calendars sync every 5 minutes, which is slower than Google Calendar and Microsoft 365:
- This is normal due to CalDAV protocol limitations.
- No real-time push notifications are available.
- The polling frequency balances responsiveness with server load.
Need faster sync? Consider using Google Calendar or Microsoft 365, which support real-time webhooks.
Kolejne kroki
Szczegóły techniczne
Dla programistów i działu IT
CalDAV protocol (RFC 4791)
SyncMyDay implements the CalDAV standard using:
PROPFIND— discovering calendars, their privileges and change tagsREPORT— querying calendar data (calendar-query)PUT— creating and updating blockersDELETE— removing blockers
Service discovery
We use WebDAV service discovery to find calendar collections:
- Try the URL you entered; if CalDAV doesn’t answer there, try
/.well-known/caldav(RFC 6764). - Follow
current-user-principalto thecalendar-home-setproperty. - Query the home set for calendar collections.
- Use
current-user-privilege-setto detect and mark read-only calendars.
Authentication and security
- Basic Auth: standard HTTP Basic Authentication over HTTPS
- Digest Auth: supported if the server requires it
- HTTPS with a valid certificate only; addresses in internal networks are refused.
- Credentials are encrypted at rest (libsodium).
Polling strategy
Since CalDAV doesn’t support push notifications:
- We poll for changes every 5 minutes.
- We compare the calendar’s
getctag/sync-token; if it hasn’t changed, events aren’t downloaded again. - If it has changed, we fetch the events of the whole sync window with a
REPORT(calendar-query). - At least once an hour the whole calendar is re-checked even without a change.
iCalendar format
Events are exchanged in RFC 5545 iCalendar format:
- We parse
VEVENTcomponents. - We extract
DTSTART,DTENDandSTATUS. - We handle recurrence rules (
RRULE). - We support timezone conversion (
VTIMEZONE).
Known limitations
- No real-time sync: 5-minute polling interval
- Server dependencies: requires a proper CalDAV implementation
- Firewall restrictions: the server must be internet-accessible
Nie udało się? Napisz do nas, a pomożemy.