Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Sync for caldav not working after update to Thunderbird 60

  • 3 replies
  • 7 have this problem
  • 1 view
  • Last reply by Xagec

folkz
folkz
more options

After I updated from Thunderbird 52.9 to 60 enlightenment stopped working with all caldav calendars on my nextcloud-instance. It doesn't synchronize anymore and doesn't even show that it doesn't. As soon as I downgrade to Thunderbird 52.9 and Enlightenment 5.4 all is good. I don't believe the problem being the nextclouds fault because the syncing is working with all android apps, Evolution and CLI tools too. I tested with a now profile on Thunderbird 60. But that doesn't help. I only get empty calenders because of the sync-problems

After I updated from Thunderbird 52.9 to 60 enlightenment stopped working with all caldav calendars on my nextcloud-instance. It doesn't synchronize anymore and doesn't even show that it doesn't. As soon as I downgrade to Thunderbird 52.9 and Enlightenment 5.4 all is good. I don't believe the problem being the nextclouds fault because the syncing is working with all android apps, Evolution and CLI tools too. I tested with a now profile on Thunderbird 60. But that doesn't help. I only get empty calenders because of the sync-problems

Chosen solution

I believe this is the CalDAV known-issue, it's a NextCloud problem. It's been reported in this issue, there is a workaround:

  1. Go to the config editor (Settings -> Advanced -> General -> Config Editor)
  2. Search for network.cookie.same-site.enabled
  3. Set it to false

For your own security you should set it back to true once this issue is resolved.

This was also mentioned in the release notes (very bottom of https://www.thunderbird.net/en-US/thunderbird/60.0/releasenotes/ )

Read this answer in context 👍 4

All Replies (3)

Fabián Rodríguez
Fabián Rodríguez
more options

Chosen Solution

I believe this is the CalDAV known-issue, it's a NextCloud problem. It's been reported in this issue, there is a workaround:

  1. Go to the config editor (Settings -> Advanced -> General -> Config Editor)
  2. Search for network.cookie.same-site.enabled
  3. Set it to false

For your own security you should set it back to true once this issue is resolved.

This was also mentioned in the release notes (very bottom of https://www.thunderbird.net/en-US/thunderbird/60.0/releasenotes/ )

folkz
folkz Question owner
more options

Thank you and sorry that I didn't read all through the release note.

Xagec
Xagec
more options

Fabián Rodríguez said

I believe this is the CalDAV known-issue, it's a NextCloud problem. It's been reported in this issue, there is a workaround:
  1. Go to the config editor (Settings -> Advanced -> General -> Config Editor)
  2. Search for network.cookie.same-site.enabled
  3. Set it to false
For your own security you should set it back to true once this issue is resolved. This was also mentioned in the release notes (very bottom of https://www.thunderbird.net/en-US/thunderbird/60.0/releasenotes/ )

Same problem here, tried the workaround to no avail. Is there anything else that can be done aside of downgrading?