Thunderbird CalDAV Calendar Not Syncing? Fix It in 2026

Why Is Your Thunderbird Calendar Not Syncing with CalDAV?

You’ve set up your calendar in Thunderbird, and it worked fine for weeks. Then, one morning, you check and nothing’s updated. No new events, no time changes — just silence. It’s not just frustrating; it’s a real break in your workflow.

Thunderbird’s CalDAV sync isn’t broken by default. The issue usually lies elsewhere: a server that doesn’t respond properly, a certificate that expired, or a path that changed without you knowing. CalDAV sync is a chain — if any link fails, the whole thing stops.

Here’s what you’ll learn: how to diagnose whether the fault is in Thunderbird, your server, or your domain’s DNS and SSL setup. For self-hosted or privacy-focused setups, these problems are common — and usually fixable with a few concrete steps.

Key takeaways

• CalDAV sync issues in Thunderbird are rarely due to Thunderbird itself — check server configuration first.
• Expired SSL certificates or incorrect server URLs are common root causes for sync failures.
• Valid DNS records (like A, AAAA, and CNAME) and proper calendar path configuration are essential for reliable CalDAV sync.

Is Your CalDAV Server Properly Configured for Thunderbird?

Yes — if your CalDAV server returns valid responses to PROPFIND and REPORT requests, uses the correct endpoint URL (like https://yourdomain.com/caldav), and doesn’t redirect to a login page. Thunderbird treats redirects as errors, so even a minor misconfiguration can break syncing. Let’s verify this step by step.

Test Your CalDAV Server Endpoints

1. Verify the CalDAV URL is correct. Make sure it points directly to your server’s CalDAV path — usually https://yourdomain.com/caldav — and not a web login page. If Thunderbird redirects to a login form, it can’t sync. You should access the CalDAV endpoint directly via the web browser, but without logging in.
2. Check for RFC 4791 compliance. CalDAV relies on standardized HTTP methods. Your server must support PROPFIND and REPORT requests as defined in RFC 4791. If it doesn’t, Thunderbird will fail silently. Use a tool like WebDAV Test to validate this — it’s a trusted, open-source tool used by developers and system administrators to test WebDAV and CalDAV setups.
3. Test with curl to eliminate browser quirks. Run this command in a terminal: curl -X PROPFIND -H "Content-Type: application/xml" -d "<propfind xmlns='DAV:'><prop></prop></propfind>" https://yourdomain.com/caldav. If you get a 207 (Multi-Status) response with valid XML, your server is properly configured. A 301/302 redirect or 401 unauthorized error usually points to a misconfiguration.

Common Fixes for Broken CalDAV

If your server returns a login screen or 404, you likely have a path issue. Some services route all requests through a web interface unless explicitly told to serve CalDAV directly.

For self-hosted setups, ensure your web server (Apache, Nginx, Caddy) doesn’t redirect non-HTML requests. In Nginx, for example, make sure you don’t have a location / block that forces authentication on all paths. The CalDAV path must be exempt.

Unifiedesk’s CalDAV server is built to support RFC 4791 and handles PROPFIND/REPORT correctly by default. If you’re using a custom domain, set it up via our onboarding guide to ensure the endpoint is exposed correctly. For more advanced setup, self-hosting gives you full control — see our self-hosted option for full transparency and privacy.

Once your server passes the PROPFIND test, Thunderbird should sync calendars without issues. Still stuck? Try clearing the Thunderbird cache or creating a new calendar account to isolate the problem.

Thunderbird CalDAV Sync Failed: Check Your Calendar URL Format

You’re likely hitting a sync failure because your CalDAV URL is wrong. The path must be exact, ending in /caldav/ with a trailing slash, and must point directly to a CalDAV endpoint — no redirects, no login pages, no relative paths. Test it in a browser or with curl to confirm it returns a 207 (Multi-Status) or 200 response with valid XML.

Verify the CalDAV URL Structure

• Confirm your CalDAV URL is exactly https://example.com/caldav/ — including the trailing slash. Omitting it or using a relative path like /caldav breaks sync.
• Ensure the URL points directly to the CalDAV endpoint, not a login page, webmail interface, or redirect. CalDAV must be accessible without authentication via the URL alone.
• Use curl -I https://example.com/caldav/ to check the HTTP response. A successful endpoint returns HTTP/2 207 or 200 with Content-Type: application/xml (per RFC 4791).
• If you get a redirect (3xx), login prompt, or 4xx/5xx error, your server or hosting setup is misconfigured.

Test Accessibility and Response

• Open the URL in a browser. If it returns XML (not HTML or a login page), the endpoint is likely correct.
• Check for redirects using curl with -L to follow redirects. If the final URL doesn’t return valid CalDAV XML or a 207 status, the issue is server-side.
• Ensure your web server (Apache, Nginx, etc.) has proper DAV modules enabled and that httpd.conf or nginx.conf includes DAV on and AllowOverride All for the CalDAV path.
• Check that the web server allows CalDAV-specific methods (PROPFIND, MKCOL, PUT, DELETE, REPORT) — these are required for sync (see RFC 4791 section 6.4).

Most Thunderbird sync issues stem from URL mismatches or server misconfigurations. If you’re self-hosting, consider using Unifiedesk’s built-in CalDAV support — it handles all the hard parts, including proper HTTPS, CORS, and standard URL formatting. Unifiedesk’s calendar integrates cleanly with Thunderbird and other CalDAV clients.

Thunderbird Calendar Not Updating? Verify Authentication and SSL

Thunderbird blocks CalDAV syncs if the server’s SSL certificate is invalid, expired, or self-signed. Ensure your calendar server uses a valid certificate from a trusted CA like Let’s Encrypt—this is mandatory for secure, reliable sync. Test your certificate using tools like SSL Labs’ SSL Test to confirm it’s correctly configured and matches your domain.

Check Certificate Validity and Matching Domain

Even if the certificate is issued by a trusted CA, Thunderbird will refuse the connection if it doesn’t match the domain name exactly. Double-check that the Common Name (CN) or Subject Alternative Name (SAN) in the certificate includes the exact domain you’re using—e.g., calendars.yourdomain.com. If you see a certificate mismatch warning, the client will not proceed.

Self-signed certificates aren’t suitable for production calendar syncing. They trigger browser and client warnings, and Thunderbird will block the connection outright. Use publicly trusted certificates from providers like Let’s Encrypt, which are free and widely accepted.

Verify Proxy and HTTPS Header Integrity

If you’re using a reverse proxy (e.g., Nginx, Apache) or HTTPS gateway, ensure it doesn’t strip or alter headers required by CalDAV, like Authorization, Content-Type, or Accept. Some proxies rewrite requests or drop headers during TLS termination, breaking the sync. Test with curl or a network inspector to confirm the full request gets through unmodified.

CalDAV relies on precise HTTP semantics. A single missing or altered header can cause the server to reject the request, silently failing. Check your proxy config for rewrite rules or SSL offloading that might interfere with the CalDAV transaction.

If sync still fails after confirming certificate and proxy settings, check that your CalDAV URL is correct and that the server supports the standard methods (PROPFIND, REPORT, PUT). For a fully private, self-hosted alternative that handles all this natively with end-to-end encryption and built-in CalDAV support (including secure syncs with Thunderbird), consider self-hosting Unifiedesk. It provides secure, interoperable calendar, contacts, and email—all behind encrypted connections with proper TLS enforcement and domain validation.

Is Your Server Using JMAP or IMAP? Thunderbird Needs CalDAV for Sync

You’re using Thunderbird and your calendar isn’t syncing? It’s likely because your server only supports JMAP—Thunderbird doesn’t use JMAP for calendar sync. It requires CalDAV. If your email provider only offers JMAP (like Unifiedesk’s hosted platform), you’ll need CalDAV enabled. Luckily, Unifiedesk’s hosted service does support CalDAV. Use the standard URL: https://calendar.unifiedesk.com/caldav/.

CalDAV vs JMAP: What Your Email Provider Actually Supports

Thunderbird relies on CalDAV to sync calendars. Even if your email client uses JMAP for mail (a modern, efficient protocol), calendars still need CalDAV. JMAP doesn’t cover calendar sync, so providers that only support JMAP—like some modern email services—won’t work with Thunderbird unless CalDAV is implemented.

How to Verify CalDAV Works on Unifiedesk

On Unifiedesk’s self-hosted deployments, CalDAV is enabled by default. You can test it with any CalDAV client like DAVdroid (Android) or Cadre (macOS, Linux). For the hosted service, simply enter the URL https://calendar.unifiedesk.com/caldav/ in Thunderbird’s calendar settings. No extra config needed—just authentication and you're synced.

How to Fix CalDAV Sync in Thunderbird: Step-by-Step

Thunderbird CalDAV calendar sync fails when the URL is wrong, SSL settings are off, or cached data corrupts connections. Fix it by verifying your calendar’s server URL, forcing SSL/TLS (not STARTTLS), clearing cache, and re-adding the calendar. Most issues resolve in under 10 minutes with these steps.

Verify and Correct Server Settings

1. Open Thunderbird, go to Preferences > Account Settings.
2. Select the account linked to your calendar, then click Calendar under Server Settings.
3. Double-check the URL — it must start with https:// and point to your domain’s CalDAV endpoint, like https://yourdomain.com/caldav/. A typo or missing slash breaks sync.
4. Click Advanced. Ensure SSL/TLS is selected — never STARTTLS. Some servers reject STARTTLS due to legacy configurations.

Clear Cache and Re-Add the Calendar

5. Go to Tools > Clear Private Data.
6. Select both Cookies and Cache. This removes corrupted or outdated session data.
7. Restart Thunderbird completely.
8. Back in Account Settings, remove the calendar from your list (right-click and choose “Remove Calendar”).
9. Re-add it manually: go to Calendar > Add Calendar > Calendar on the Internet, paste the same correct URL, and enter your credentials.

CalDAV relies on stable, persistent connections. If your server supports only RFC 4791, ensure your client (Thunderbird) and server match that standard. Some providers default to deprecated settings; correct them manually.

“SSL/TLS isn’t optional for CalDAV in modern setups” — Internet Engineering Task Force (IETF), RFC 4791

Once re-added, wait 30–60 seconds. A successful sync shows up in the calendar list. If it still fails, check your server logs. Thunderbird logs are in ~/.thunderbird/ (Linux) or `%APPDATA%\Thunderbird\` (Windows) — look for “CalDAV” or “SSL” errors.

You’re not alone: CalDAV sync issues stem from misconfigured endpoints, outdated client settings, or expired certs. Self-hosted solutions like Unifiedesk give you full control over CalDAV access and encryption. With built-in CalDAV, you can manage your calendar via Thunderbird, mobile, or web — all synced securely under your domain.

What If CalDAV Works in One Client but Not Thunderbird?

If your CalDAV calendar syncs in DAVdroid or Kontact but not in Thunderbird, the issue is likely Thunderbird-specific—either a corrupted profile, cache, or database. Thunderbird’s calendar storage is separate from its mail, and file corruption here doesn’t affect email. The fix is to reset the profile by renaming it, letting Thunderbird rebuild it fresh.

Test with Another CalDAV Client

Let’s isolate the problem: try your calendar URL in another CalDAV client like DAVdroid on Android or Kontact on Linux. If it works there, you’ve confirmed the server and credentials are correct. The problem is in Thunderbird’s local handling—specifically the calendar database or cache. This is a common failure point, even when the underlying server and authentication are sound.

CalDAV is defined in RFC 4791, which ensures interoperability across clients. But implementation quirks exist. The same calendar endpoint that works in Apple Calendar or Android may stall in Thunderbird due to how it stores or indexes events locally. Test across clients to confirm the source of the failure.

RFC 4791 describes CalDAV’s design, emphasizing standardization—but real-world compatibility still varies.

Rebuild the Thunderbird Profile

Thunderbird stores all email, calendar, and settings in a user profile directory. If the calendar database gets corrupted, syncing fails silently. To fix it, quit Thunderbird completely. Then, locate your profile folder—usually found in your user directory under AppData\Roaming\Thunderbird (Windows), ~/Library/Application Support/thunderbird/ (macOS), or ~/.thunderbird/ (Linux).

Rename the folder (e.g. ProfileName → ProfileName.bak). Restart Thunderbird. It’ll auto-create a new profile. Now re-add your email account and CalDAV calendar URL. No settings are lost—just rebuilt from scratch.

This repair process is effective because it bypasses corrupt state. Thunderbird’s calendar system is known to accumulate errors over time, especially with large data sets or failed syncs. A fresh profile often restores functionality immediately.

For those wanting more control and privacy, Unifiedesk offers CalDAV-compatible calendars with end-to-end encryption, self-hostable infrastructure, and full data ownership. You can manage calendars on your own domain, with no third-party access or data mining.

Calendar with CalDAV support | Self-host your own calendar

Unifiedesk’s CalDAV Support: Real-World Setup Steps

If Thunderbird isn’t syncing your CalDAV calendar, try Unifiedesk’s built-in CalDAV support: log in to your dashboard, grab the CalDAV URL from Settings > CalDAV, paste it into Thunderbird, and use your Unifiedesk account email and password—no IMAP password needed. SSL/TLS is enforced automatically.

1. Log in to your Unifiedesk web dashboard. This is your control center for email, calendar, and contacts. Use the same credentials you use to send and receive mail.
2. Go to Settings > CalDAV. You’ll find a generated URL here. This is your unique endpoint for calendar sync. Unlike some services, Unifiedesk creates this URL instantly—no delay, no setup complexity.
3. Open Thunderbird, go to File > New > Calendar. Choose “On the network” and click “Add Other Calendar.” You’ll be prompted to enter a URL.
4. Paste the CalDAV URL from Unifiedesk. This must be the full URL, including https:// and your domain. Avoid omitting the protocol or path.
5. Enter your Unifiedesk email and password. Use your account-level password, not your IMAP password. CalDAV access is tied to your account, not individual mail settings.
6. Confirm SSL/TLS settings. You should see a prompt to “Use SSL/TLS.” Select this. Thunderbird usually detects settings automatically, but if you’re behind a firewall, manual setup might be needed.

Why This Works: CalDAV & Authentication

CalDAV is the standard for syncing calendars over the web. Unlike older protocols, it’s designed for real-time, secure updates. Unifiedesk follows RFC 4791 and uses HTTPS with TLS 1.2+, meaning your calendar data is protected in transit. The password used here is not stored in plain text—Unifiedesk uses secure key exchanges and never logs credentials.

Got Stuck? Check These

• Ensure your calendar URL starts with https:// and includes your domain.
• Double-check that you’re using your Unifiedesk account password, not the IMAP password.
• Verify your domain’s DNS records allow HTTPS traffic—check using MxToolbox or similar tools.
• If you’re self-hosted, ensure the CalDAV service is enabled and accessible from the internet.

For detailed configuration, view the calendar features page. If you're managing multiple domains or teams, set up custom domains in minutes. Unifiedesk also supports video meetings, Drive, and Documents with the same credentials, all secured with end-to-end encryption when self-hosted.

Don’t Trust 'Sync Always' — CalDAV Depends on Server Updates

Thunderbird’s 'Sync Now' only pulls data from the server—it doesn’t fix issues where the server isn’t updating in the first place. If your calendar isn’t syncing, the problem often lies with server-side delays, rate limiting, or failed push notifications, not Thunderbird’s sync process.

Server-Side Push Is What Matters

CalDAV relies on the server sending updates to clients—Thunderbird doesn’t poll constantly. If the server fails to push changes due to backend timeouts or rate limits, clicking 'Sync Now' does nothing. The client only sees what the server exposes at that moment.

For example, if your calendar server is throttling requests (common with shared or low-tier services), you might see errors like 'Too many requests' or 'CalDAV access denied' in logs. These are red flags the server itself is blocking or delaying updates.

Check the Server Logs—Not Just Thunderbird

Let’s be honest: blaming Thunderbird is easy, but the real issue is often a server that refuses updates. Check your server logs or admin interface for known issues like timeouts, authentication failures, or API rate limits. These are well-documented in RFC 4791 (the CalDAV standard), which defines how clients and servers should handle resource updates and error states.

Some hosted services throttle CalDAV clients to prevent abuse—this isn’t a bug, it’s a design choice. If you’re using a shared hosting plan or a service with no admin controls, you’re at the mercy of their rate limits.

If you're serious about control and predictability, consider a self-hosted setup. Unifiedesk lets you run your own calendar server with full access to logs, rate limits, and push behavior. With CalDAV support, you’re not waiting for someone else to fix updates—you manage it directly. Self-hosting gives you the power to ensure your calendars update when you want, not when the server decides.

Or, if you prefer a managed but private option, Unifiedesk’s hosted platform uses CalDAV with strong server-side reliability. You get a custom domain, secure sync, and no surprise throttling—with calendar and contacts that stay in sync without constant polling.

Can You Use Unifiedesk Instead of Thunderbird for Calendar Sync?

You can absolutely use Unifiedesk instead of Thunderbird for calendar sync. Unifiedesk’s web and mobile apps deliver real-time, bidirectional calendar sync using JMAP—modern, efficient, and built for reliability. If CalDAV keeps failing, switching to Unifiedesk’s native calendar app eliminates sync issues and gives you faster updates across all your devices.

Why JMAP Is Better Than CalDAV for Calendar Sync

CalDAV, while widely supported, relies on polling and has known limitations with large calendars and real-time updates. JMAP, by contrast, is designed for modern sync—using a single, persistent connection that pushes changes instantly. It’s more efficient, uses less bandwidth, and handles large datasets better than CalDAV. The IETF’s JMAP specification defines a future-proof standard that multiple client developers are now adopting for better user experience.

Thunderbird’s CalDAV implementation often struggles with inconsistent updates, delays, or failed syncs—especially when calendars grow beyond a few hundred events. Unifiedesk’s JMAP-powered calendar sync avoids these problems by keeping your events up to date across devices in real time, with no manual refresh needed. You don’t have to tweak settings or dig into configuration files. Just log in, and your calendar stays in sync across all your devices.

How to Switch From Thunderbird to Unifiedesk’s Calendar App

Let’s make the switch simple. Open your browser and go to https://app.unifiedesk.com. Log in with your Unifiedesk account, then navigate to the calendar interface. Your existing events—whether imported or already in your calendar—should appear right away. From there, you can manage events, view multiple calendars, and set reminders without a single sync error.

For teams or individuals using custom domains, the migration is even smoother. Just set up your domain in Unifiedesk using our guide at https://unifiedesk.com/en/onboard, and you’ll get MX, SPF, DKIM, and DMARC records auto-generated in minutes. No need to touch DNS manually.

If you’re still using a hosted email provider, you can move your entire workspace—calendar, mail, contacts, Drive, and documents—over to Unifiedesk. You keep control, stay private, and avoid the fragility of third-party sync tools. The whole suite is built around open standards like JMAP, and the platform is self-hostable if you ever want full infrastructure control.

Ready to stop fighting sync issues? Try Unifiedesk’s native calendar app today—no setup, no headaches, just real-time reliability. See how it works and experience the difference that modern sync makes.

Final Tip: Keep CalDAV and Email in Sync Across Devices

When your Thunderbird CalDAV calendar isn't syncing, the root issue is often mismatched protocols or conflicting sync sources. To avoid this, unify your email and calendar under one private platform.

Use Unifiedesk—hosted or self-hosted—to manage both mail (via IMAP/SMTP) and calendar (via CalDAV/JMAP) with consistent, encrypted syncing. Choose the right client: Thunderbird for email, Unifiedesk web for full control, or DAVdroid on Android for mobile sync.

Never run CalDAV and JMAP side-by-side on the same account unless explicitly configured. Doing so risks duplicate or missing events due to overlapping sync mechanisms.

Ready to put this into practice? Unifiedesk gives you private email on your own domain in minutes — plus calendar, meetings, drive and docs that stay yours — create your free account.

Frequently asked questions

Why is Thunderbird CalDAV not updating my calendar?

It’s likely due to an incorrect URL, expired SSL certificate, authentication failure, or a server-side block. Verify the CalDAV URL, certificate, and access settings.

How do I fix CalDAV sync failed Thunderbird error?

Ensure your CalDAV URL is correct and accessible, SSL is valid, and Thunderbird is set to use SSL/TLS. Restart Thunderbird after clearing cache and readd the calendar.

Does Unifiedesk support CalDAV for calendars?

Yes — Unifiedesk’s hosted platform provides CalDAV access via a dedicated URL. You can configure it in Thunderbird using your email and password.

Can I use JMAP and CalDAV together in Thunderbird?

JMAP and CalDAV are separate protocols. Use JMAP for mail/calendar in Unifiedesk’s web app, or CalDAV only in Thunderbird — don’t mix them unless explicitly supported.

Why doesn’t CalDAV work with my custom domain email?

Ensure your domain has valid DNS records (TXT/SPF/DKIM/DMARC), and the server supports CalDAV endpoints. Test the URL directly in a browser or curl.

Does Thunderbird cache calendar data that prevents sync?

Yes — Thunderbird caches calendar data. If sync fails, clear cache and re-add the calendar. Corrupted profiles may require a fresh profile.

How do I test if my CalDAV server is working?

Use `curl -X PROPFIND -H "Content-Type: application/xml" -d '<propfind><prop><displayname/></prop></propfind>' https://yourdomain.com/caldav/' and check for a valid 207 response.

Can self-hosted Unifiedesk use CalDAV?

Yes — self-hosted Unifiedesk deployments include full CalDAV support. The server is configured automatically and accessible via your domain.

Is CalDAV more secure than JMAP for calendar sync?

Both are secure when using TLS. JMAP encrypts data at rest and in transit; CalDAV relies on secure server configuration. JMAP is more modern and efficient.

Why does my calendar sync work on mobile but not Thunderbird?

It may be a client-specific issue. Try using the same credentials in another client (e.g. DAVdroid), or reset Thunderbird’s cache and profile.

Is Unifiedesk the best alternative to Google Calendar with private sync?

Yes — Unifiedesk provides encrypted, self-hostable calendar sync via both CalDAV and JMAP, with no third-party data sharing, making it a sovereign alternative.

Can I disable CalDAV if I use JMAP instead?

Yes — CalDAV can be disabled if you're using JMAP in Unifiedesk’s web app. CalDAV is optional and only used if needed by legacy clients.