Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Avatar for Username

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Тази тема беше архивирана. Моля, задайте нов въпрос ако имате нужда от помощ.

Sync for caldav not working after update to Thunderbird 60

  • 3 отговора
  • 7 имат този проблем
  • 1 изглед
  • Последен отговор от 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

Избрано решение

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

Прочетете този отговор в контекста 👍 4

Всички отговори (3)

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

Избрано решение

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 Задаващият въпроса
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?