This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Denne tråden ble arkivert. Still et nytt spørsmål dersom du trenger hjelp.

Sync for caldav not working after update to Thunderbird 60

  • 3 svar
  • 7 har dette problemet
  • 1 view
  • Siste svar av 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

Valgt løsning

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/ )

Les dette svaret i sammenhengen 👍 4

All Replies (3)

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

Valgt løsning

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 Eieren av spørsmålet
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?