Server: Thunderbird 60.x unable to use caldav/carddav

Created on 6 Jul 2018 · 100Comments · Source: nextcloud/server

When trying to access calendar (Lightning) and addressbooks (CardBook) on a Nextcloud 13.0.4 server, Thunderbird 60.0b9 receives status 503 from the server and therefor cannot access any data.

Using Thunderbird 52.x everything works as expected.

Cross reference see https://bugzilla.mozilla.org/show_bug.cgi?id=1468912

The admin of our webserver tried the same with owncloud 7.0.4, but he did not test newer versions.
Using this really old version of owncloud, Thunderbird 60.0b9 manages to access the caldav and carddav urls without any error.
Since Nextcloud is a fork of owncloud, it might be, that the described issue is not Thunderbird related.
Perhaps the bug has to be searched for in Nextclouds code.

bug dav

Source

egal88

👍8

Most helpful comment

By disabling the newly introduced parameter network.cookie.same-site.enabled the problem can be solved. So it seems to be a kind of cookie handling problem?!

Yes, there is an issue with the cookie handling. I'm talking to the person at Mozilla who implemented it to see what causes this issue and how we can resolve it.

As a workaround:

(as described in Thunderbird's release notes):

go to the config editor (Settings -> Advanced -> General -> Config Editor)
search for network.cookie.same-site.enabled
set it to false

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

georgehrke on 8 Aug 2018

👍36 ❤3 🎉3 😄2

All 100 comments

GitMate.io thinks possibly related issues are https://github.com/nextcloud/server/issues/8766 (Caldav ), https://github.com/nextcloud/server/issues/6291 (Thunderbird/Lightning Events pop up after each caldav update), https://github.com/nextcloud/server/issues/3031 (Carddav/Caldav api confusion), https://github.com/nextcloud/server/issues/8469 (Allow remote caldav/carddav servers), and https://github.com/nextcloud/server/issues/8500 (Unable to access CalDAV as LDAP authenticated user).

nextcloud-bot on 6 Jul 2018

I can confirm a working Thunderbird 60.x with ownCloud 10.0.2.
I can confirm a not working Thunderbird 60.x with Nextcloud 11.0.3 and nextcloud 12.0.9.

painxcess on 7 Jul 2018

cc @georgehrke

MorrisJobke on 9 Jul 2018

Thunderbird 60.0b10 still has the same issue

egal88 on 9 Jul 2018

We might be investigating the same issue here: https://gitlab.com/CardBook/CardBook/issues/306 and https://bugzilla.mozilla.org/show_bug.cgi?id=1468755

Could you confirm that TB60 beta 4 did not have the issue, while beta 5 and following have it? (you can find these versions here: https://filehippo.com/fr/download_thunderbird/history/

biva on 9 Jul 2018

And for reference, I closed my initial issue because I thought it was cardbook related: https://github.com/nextcloud/server/issues/9869

@egal88 could you correct your bugzilla link (it's broken)?

biva on 9 Jul 2018

I can confirm:

TB60 Beta 4 syncs caldav (works)
TB60 Beta 5 does not sync (-> actual issue)

painxcess on 9 Jul 2018

@biva Bugzilla link corrected. Thanks for your info.

egal88 on 9 Jul 2018

@georgehrke @MorrisJobke Thunderbird developers ask for Nextcloud developers' support in https://bugzilla.mozilla.org/show_bug.cgi?id=1468912#c33 as it might be specific to Nextcloud. Could you have a look?

biva on 13 Jul 2018

@georgehrke Could you answer their questions, as you know a bit more about it.

MorrisJobke on 16 Jul 2018

Or maybe @rullzer regarding the auth stuff.

MorrisJobke on 16 Jul 2018

@rullzer and @georgehrke It looks like if this issue happens with Nextcloud server only. Could you have a look at this Thunderbird issue? https://bugzilla.mozilla.org/show_bug.cgi?id=1468912#c54

biva on 31 Jul 2018

👍2

@adi-dev @georgehrke @rullzer Thunderbird 60 has been released and this issue is the single "Known Issues" in the release notes https://www.thunderbird.net/en-US/thunderbird/60.0/releasenotes/

And apparently, only Nextcloud is having this issue. Thunderbird developers are begging for a support from Nextcloud to investigate this (https://bugzilla.mozilla.org/show_bug.cgi?id=1468912#c61). Could you have a look?

biva on 7 Aug 2018

❤1

When I took a look a couple of days ago it seemed to be related to Nextcloud in a subdirectory. Can anyone confirm this?

Looking into a proper fix now ..

georgehrke on 7 Aug 2018

it seemed to be related to Nextcloud in a subdirectory. Can anyone confirm this?

I'm not sure to understand your question. I'm having the issue and my Nextcloud is installed in /var/www/html/nextcloud and the url is https://nexcloud.mywebsite.com

biva on 7 Aug 2018

Just out of curiosity, my httpd logs are full of:

503 Service Unavailable
    /remote.php/dav/calendars/username/contact_birthdays/: 8 Time(s)
    /remote.php/dav/calendars/username/pers ... 18671aca94f.ics: 8 Time(s)
    /remote.php/dav/calendars/username/pers ... 2B019A7E39A.ics: 8 Time(s)
    /remote.php/dav/calendars/username/pers ... 746adb10b4e.ics: 8 Time(s)
    /remote.php/dav/calendars/username/personal/: 8 Time(s)
    /remote.php/dav/calendars/username/work ... 3205226d8d2.ics: 8 Time(s)
    /remote.php/dav/calendars/username/work ... 424356a20b3.ics: 8 Time(s)
    /remote.php/dav/calendars/username/work ... 8f14bfddd52.ics: 8 Time(s)
    /remote.php/dav/calendars/username/work ... 98e7d1e3e30.ics: 8 Time(s)
    /remote.php/dav/calendars/username/work ... ac01859d6df.ics: 8 Time(s)
    /remote.php/dav/calendars/username/work ... afbc4852481.ics: 8 Time(s)
    /remote.php/dav/calendars/username/work ... d04937ec4a4.ics: 8 Time(s)
    /remote.php/dav/calendars/username/work/: 8 Time(s)

I set up my Thunderbird as CalDAV, is it normal it requests .ics files?
Any clues?

adi-dev on 8 Aug 2018

@georgehrke I just read the description of the Thunderbird bug report and it seems that the interesting part starts at comment 43. By disabling the newly introduced parameter network.cookie.same-site.enabled the problem can be solved. So it seems to be a kind of cookie handling problem?!

j-ed on 8 Aug 2018

👍1

By disabling the newly introduced parameter network.cookie.same-site.enabled the problem can be solved. So it seems to be a kind of cookie handling problem?!

Yes, there is an issue with the cookie handling. I'm talking to the person at Mozilla who implemented it to see what causes this issue and how we can resolve it.

As a workaround:

(as described in Thunderbird's release notes):

go to the config editor (Settings -> Advanced -> General -> Config Editor)
search for network.cookie.same-site.enabled
set it to false

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

georgehrke on 8 Aug 2018

👍36 ❤3 🎉3 😄2

I can confirm, the workaround works for me, cheers

adi-dev on 8 Aug 2018

No problems with old installations upgraded to Thunderbird 60.

After creating a new profile in TB 60. had the problem with caldav and carddav under cardbook.
The network.cookie.same-site.enabled works, but I think, Thunderbird should work out of the box...

JSoko on 9 Aug 2018

When I took a look a couple of days ago it seemed to be related to Nextcloud in a subdirectory. Can anyone confirm this?

I can tentitavely confirm this (even though I assume debugging has moved beyond this point). I was actually going mad trying to figure out why one of my up-to-date nextcloud instances (in root folder) would sync as usual after the TB60 update and the other one wouldn't (in sub-folder, TB actually receives a 503). Especially as both kept synching with DAVDroid and react to curl.

The work around seems to work for me as well. Keep up the good work, thanks everyone!

goddib on 9 Aug 2018

Yes, there is an issue with the cookie handling. I'm talking to the person at Mozilla who implemented it to see what causes this issue and how we can resolve it.

Hello @georgehrke,
Did you find the causes?

biva on 13 Aug 2018

Did you find the causes?

No, we are still looking for what causes this. If we know more, I will comment here.

georgehrke on 13 Aug 2018

👍7 ❤1

👍 Great both sides are working on this, this issue drove me crazy for the last two days 🤣.

MichaIng on 14 Aug 2018

Still no idea about the cause? Thanks for your investigation.

biva on 29 Aug 2018

I´m syncing two thunderbirds (both 60.0) on two computers with the same Nextcloud-Installation. Both same system (win7), but one is 32bit, the other is 64bit. The 32bit system seems to work fine (thunderbird syncs like expected), the 64bit doesnt want to sync (execpt using the workaround described above). May that helps...

criwe on 29 Aug 2018

I can't confirm a working Windows 7 Pro in 32 Bit with Nextcloud 13.0.6.
(Tested a fresh Win7-Install 32 Bit with all updates and Thunderbird 60)

painxcess on 5 Sep 2018

I'm also hit by this bug.
What's interesting for me though, that I only have this problem with a fresh TB profile.
With an existing TB profile where I've setup lightning a long time ago, the calendar sync works.

mbiebl on 17 Sep 2018

👍1

@mbiebl cannot confirm the "only fresh profile" observation. Just tested two thunderbirds with year old profiles and had to activate the work-around for both.

mnlipp on 17 Sep 2018

👍2

@mnlipp: can confirm that old profiles got the problem too.

I´ve updated Nextcloud from 13.x to 14.01, but still the same issue...

criwe on 25 Sep 2018

👍1

I'm not sure but https://github.com/nextcloud/server/pull/11433 might fix this.

rullzer on 2 Oct 2018

@rullzer looks good. I´ve tested with two installations, in both syncing works fine now.
But would be cool, if some other thunderbird user(s) can test too.

criwe on 14 Oct 2018

I just installed NC 14.0.3: is this patch included?

biva on 14 Oct 2018

@biva
I don't think so, can't find the new CookieHelper class inside stable14 branch

MichaIng on 14 Oct 2018

@biva @MichaIng I´m not sure, but I think so, because it #11433 is marked as merged and I´ve only made the update to 14.0.3 and no other manual patching.

criwe on 14 Oct 2018

@criwe
Jep merged into "master", but not merged into "stable14", which is 14.0.3 branch. But I will test myself now by switching Thunderbird back to network.cookie.same-site.enabled=true

€: Ah lol, it was already... Yeah, I reinstalled Thunderbird in between for some other reason I remember 😆. So somehow the issue seems to be resolved on Thunderbird side already?
Also fixing this issue was not the (main) purpose of the PR.

So jep, solved by either another commit until v14.0.2 or on Thunderbird side.
@georgehrke
To cleanup you can close this issue, as long as nobody complains it is still an issue.

MichaIng on 14 Oct 2018

👍1

Just tried, changed settings network.cookie.same-site.enabled=true and restart the TB and BOOM! my TB version just upgraded to 63 beta 1, none of the add-ons are working lol. Rolled back TB to 60.2.1 (release) and checked, all working with network.cookie.same-site.enabled=true 😃 🍻 cheers guys!

Edit It doesn't work, just realized the TB does not sync events with Nextcloud :cry:

adi-dev on 15 Oct 2018

Neither Lightning nor CardBook works with Nextcloud 14.0.3 stable without network.cookie.same-site.enabled=false hack. TB 60.2.1 (32-Bit) fresh installed.
Additional info: and the Nextcloud is installed in a subdomain in my case.

fuzsin on 15 Oct 2018

here works with Thunderbird 60.2.1 (32-Bit)
with the beta of sogo-connector-60.0.0-e2547a3565.xpi
= https://packages.inverse.ca/SOGo/thunderbird/nightly/
calendar works
also CardBook works too
and my NextCloud is 14.0.3
by the way, the Custom Address Bar in english works also with the v2.5 on github,
i have make a version 2.5.1 for German users too and put it on my blackysgate.de/files :)
shimamu have the pull request not done for german lang files..
edit: ah ja.. Win7 Modded' hihi

best regards
Blacky

screen 00002

blackcrack on 15 Oct 2018

The workaround does not work for me.. NextCloud 13.0.7 with Thunderbird 60 x64 on Arch. As soon as i set the setting to FALSE, the calendar gets "disabled" in Lightning and i can reenable it again untill i change the config back to true..

jadesoturi on 15 Oct 2018

For the sake of completeness: The problem still exists with Nextcloud 14.0.3 and TB 60.2.1 (64-Bit) (@fuzsin already reported it for 32-bit). The workaround still works (and is still required).

mnlipp on 16 Oct 2018

@mnlipp - I've tried the workaround fix with both the the 32bit and 64bit on my 13.0.7 installation, but it does not work for me. Results in the calendar being turned off in Lightning, until I set the setting to TRUE again. Is there something I'm missing that can be the reason for this?

jadesoturi on 16 Oct 2018

I just installed NC 14.0.3: is this patch included?

Nope this is only in master. So will be NC15

rullzer on 16 Oct 2018

👍3

I use TB60.2.1 (64bits) under Ubuntu 16.04.4 with a Nextcloud 14.0.3 freshly migraded.
The change of network.cookie.same-site.enabled=true to network.cookie.same-site.enabled=false allows the calendar synchronisation.

abject on 8 Nov 2018

👍2

NC 14.0.3 on Openmandriva 3.03 Server .
Client TB 60.3.0 (32-Bit)
https://packages.inverse.ca/SOGo/thunderbird/nightly/
https://packages.inverse.ca/SOGo/thunderbird/nightly/sogo-integrator-60.0.0-3f871d5df1-sogo-demo.xpi
this works on TB WinNT
and also works the Carddav own solution of Thunderbird..
Open AdressBook => Extra => New => Remote-AdressBook

best regards
Blacky

blackcrack on 8 Nov 2018

I use TB60.2.1 (64bits) under Ubuntu 16.04.4 with a Nextcloud 14.0.3 freshly migraded.
The change of network.cookie.same-site.enabled=true to network.cookie.same-site.enabled=false allows the calendar synchronisation.

Thank you! This fixed the issue with Thunderbird 60.3.0. Calendar and Contacts are working now.

aventu90 on 9 Nov 2018

@jadesoturi the workaround worked for me (mostly fresh Arch installation, Nextcloud 14, don't know which minor version though)

qw3ry on 9 Nov 2018

Unfortunately I ran into a lot of trouble as Thunderbird automatically updates to v60.3.0 (32bits) yesterday. Thunderbird wasn't able to show all my subscribed calendars nor was the response behavior acceptable with network.cookie.same-site.enabled=true, as it tries to synchronize with Nextcloud 14.0.3.
I managed to set network.cookie.same-site.enabled=false but the response behavior was still bad although some calendar items were shown. At the end I decided to reinstall Thunderbird 52.9.1 and got everything working again. Therefore it seems that I need to wait for a full fix in Nextcloud to get it working as before.

j-ed on 11 Nov 2018

On a fresh Windows install, after network.cookie.same-site.enabled=true was somehow working for me, now it is not anymore, matching reported results here.

Perhaps when Thunderbird and Nextcloud already communicated successfully, cookies are saved and such, the setting can be set to true again? Will test by times.

MichaIng on 11 Nov 2018

Can confirm this bug for Nextcloud v14.0.3 and Mozilla v60.3.0. The network.cookie.same-site.enabled=false-workaround works. Disabling the setting and re-enabling it after a succesfull sync doesn't help.
When prompted for username and password I get the following warning:
my-hostname is requesting your username and password. WARNING: Your password will not be sent to the website you are currently visiting! What does this mean really? Could this have something to do with the issue?

I understand that a fix in NC 15 is underway (thx!). @rullzer, as you stated

I'm not sure but #11433 might fix this.

Could you elaborate a tiny bit on what you suspect went wrong?
If I could help out testing or so I'd be glad to.

MikiDi on 12 Nov 2018

When prompted for username and password I get the following warning:
my-hostname is requesting your username and password. WARNING: Your password will not be sent to the website you are currently visiting! What does this mean really? Could this have something to do with the issue?

No, this means that you retrieves your e-mails from another site than your calendar data.

brunt82 on 12 Nov 2018

Hm, even with the workaround it does not work for me (14.0.4 and TB 60.2.1):

"Exception":"OCA\\DAV\\Connector\\Sabre\\Exception\\PasswordLoginForbidden"

Edit: Nargh, 2FA was enabled ;) Okay, works now!

morph027 on 23 Nov 2018

I'm also affected.
Workaround ok with network.cookie.same-site.enabled=false

Nextcloud server version: 13.0.1
Thunderbird: 60.3.0
Lightning: 6.2b6

ftoral on 25 Nov 2018

same issue, workaround works (network.cookie.same-site.enabled=false)

Nextcloud server version: 14.0.3
Thunderbird: 60.2.1
Lightning: 6.2b6

ftorto on 25 Nov 2018

same issue, workaround works (network.cookie.same-site.enabled=false)

Nextcloud server version: 14.0.4
Thunderbird: 60.2.1 (64bit on KDE neon)
Lightning: 6.2.2.1

I had the problem only with newly added calenders. Older calenders from another NC13/14 instance worked all the time.

FreeMinded on 2 Dec 2018

No further comments that it doesn’t work on Nc 13/14 with Thunderbird 60 please. We are aware and more and more comments won’t fix it ;):)

If you want to help us fix this, please grab the RC of Nextcloud 15 and verify that it fixes it.

georgehrke on 2 Dec 2018

👍6

I'm on 15 since Alpha, got Beta 1 and 2 now.
The Problem is there too. Also with the workaround it doesn't work in Thunderbird 60.3.0 (64-Bit).
Client is on Debian 4.9.130-2
Server is Raspian 4.14.79-v7+ #1159 armv7l GNU/Linux

EDIT:
Changed to RC1, RC2 and RC3. Problem still exits.
Removed all CalDAV Calendars and imported new on RC3.
Working now without the workaround.
Seems to be a DNS-Problem.

Luegengladiator on 2 Dec 2018

NextCloud 15 beta RC3, Thunderbird 60.3.2 (32-Bit), Lightning 6.2.3.2, Windows 10 (64-Bit) - same issue, workaround works.

fuzsin on 7 Dec 2018

@Luegengladiator if you fixed the issue by removing the calendars and reimporting them. how do you end up with the conclusion that this is a DNS problem? I don't see any relation there.

@georgehrke as there are already two users reporting the issue still exists, is there anything we can do to help so this issue will get fixed?

Schroedingers-Cat on 14 Dec 2018

@Schroedingers-Cat
I removed the calendar referencing http://my.local.domain/path/to/calendar (nonworking)
With http://127.0.0.1/path/to/calendar (working)
So the only thing I changed was replace a Name with the corresponding IP.
I think this is a local DNS Problem ;)

Luegengladiator on 14 Dec 2018

Tested with version 15.0.0 and Thunderbird 60.2.1 and 60.3.1 and was hoping this would be fixed.
Problem is unfortunately not fixed so #11433 did not help unfortunately.

Would really be great to have some focus on this issue. This affects a lot of users and is very simple to reproduce.

mbiebl on 16 Dec 2018

Would really be great to have some focus on this issue. This affects a lot of users and is very simple to reproduce.

There is focus on this issue. You, being a developer yourself, should know best that simple to reproduce is not the same as simple to debug / simple to fix 😉

Having the same logic for same-site cookies work with all major browsers and other Calendar applications just fine, I tend to say this is a bug in Thunderbird / Lightning, but we are still figuring that out together with the people at Mozilla who wrote the Same Site Cookie code.

georgehrke on 16 Dec 2018

Solved the problem via option --> General --> config editor --> network.cookie.same-site.enabled=false
Nextcloud server version: 15.0.0
Thunderbird: 60.4.0
Lightning: 6.24
You need to add the correct calendar path. For example, the calendar named "nextcloud"
http://xxx,com:8080/remote.php/dav/calendars/USER_NAME/nextcloud/

lyu0001 on 28 Dec 2018

👍1

I have found a safer workaround: If you have changed it already set network.cookie.same-site.enabled to true again. Then set all third party cookies to be denied and add an exception for the domain your Nextcloud installation is running on.

svenmauch on 1 Jan 2019

👍5 👎1

I have found a safer workaround: If you have changed it already set network.cookie.same-site.enabled to true again. Then set all third party cookies to be denied and add an exception for the domain your Nextcloud installation is running on.

@svenmauch Could you walk me through the steps to add an exception for nextcloud?

rvanlaar on 7 Jan 2019

@rvanlaar
Settings > Privacy > Web content > Exceptions > Enter https://your.domain.org[/nextcloud]

MichaIng on 9 Jan 2019

👍2

I have found a safer workaround: If you have changed it already set network.cookie.same-site.enabled to true again. Then set all third party cookies to be denied and add an exception for the domain your Nextcloud installation is running on.

Does not work for me (60.3.1).

mnlipp on 9 Jan 2019

I have found a safer workaround: If you have changed it already set network.cookie.same-site.enabled to true again. Then set all third party cookies to be denied and add an exception for the domain your Nextcloud installation is running on.

Does not work for me (60.3.1).

Same. Doesn't work for me (60.4.0). Nextcloud 13

megies on 10 Jan 2019

The workaround by @svenmauch and @mjmunger does not work for me (TB 60.4, Nextcloud 13.0.8).

Schroedingers-Cat on 10 Jan 2019

I created a topic for workarounds in our forum: https://help.nextcloud.com/t/workarounds-for-same-site-cookie-bug-with-thunderbird/44873

As the developer, I recommend to stick to the workaround described in https://github.com/nextcloud/server/issues/10134#issuecomment-411322692

Please take all further discussion about workarounds to that forum topic.

georgehrke on 10 Jan 2019

Is there a way to disable this functionality on the server side? I'm asking because this particular issue is what's currently preventing me from upgrading one of my nextclound instance to v15.
This installation has quite a few users and a lot of them do use TB. Asking all those users to update/change their TB configuration is not really an option.
If I could change the cookie handling on the server side and switch it back once fixed, that would be workable solution for me.

mbiebl on 11 Jan 2019

I can confirm that this is happening on the v14 too.
It may be something related to the Thunderbird configuration, accounting for the second workaround not working as expected for everyone (?).

@mbiebl It is definitely not recommended to tweak cookie settings on the server-side, as it would endanger ALL your clients, including regular WEB usage, and not only Thunderbird synchronization.

EDIT : Still happening with Thunderbird v60.3.1 and Nextcloud v14.0.5

HorlogeSkynet on 11 Jan 2019

Is there a way to disable this functionality on the server side? I'm asking because this particular issue is what's currently preventing me from upgrading one of my nextclound instance to v15.

Not upgrading NextCloud won't help you - at least V13 and V14 are affected as well.

You will have to keep your users from updating Thunderbird to V60, which in turn probably would be a bad idea from the security perspective. (Not even speaking of the difficulty of preventing users to update their software which possibly also auto-updates.)

So giving your users instructions of how to configure Thunderbird to work around the issue probably is the best approach.

gohrner on 11 Jan 2019

I had trouble with this function too in the past with Thunderbird v60.3.1, but after I exactly followed the tip of @svenmauch, I was successfully able to configure Thunderbird 60.4 with Lightning 6.2.4/Cardbook 33.5 and NC 14.0.4/.5.
I would recommend to always give it a personal try before relying on others feedback. There are so many system in the wild, which are all configured differently, that you couldn't rely on it.

j-ed on 11 Jan 2019

the safer workaround didn't work for my setup (Thunderbird 60.4.0 arch, and Nextcloud 15.0.2), but the official one did.

tleydxdy on 17 Jan 2019

👍1

Just wanted to try some Thunderbird events with Nextcloud to notice TB doesn't work with NC anymore… cookies.same-site workaround helped. Which is the currently recommended workaround? Has this been fixed already (either in Thunderbird or in NC or in both)?

rfc2822 on 22 Jan 2019

Thundebird found the issue:

https://bugzilla.mozilla.org/show_bug.cgi?id=1468912

See latest comments.

JtheBAB on 22 Jan 2019

🎉3

Ok thanks… I got it now working but I have to delete the credentials/cookies every time I want to see the other calendar. Confusing but it somehow works now.

rfc2822 on 22 Jan 2019

@rfc2822 Hey, the recommended workaround is the one i mentioned further above.

Has this been fixed already (either in Thunderbird or in NC or in both)?

Looking at the latest comments in https://bugzilla.mozilla.org/show_bug.cgi?id=1468912, the issue was fixed on the Thunderbird side and I expect a fix to be released soon.

georgehrke on 22 Jan 2019

I'm closing this ticket, because it's an issue in Thunderbird.

Looking at https://bugzilla.mozilla.org/show_bug.cgi?id=1468912#c83, they already have a fix and consider releasing a new beta version of Lightning 6.7, so i expect this fix to be available soon.

georgehrke on 22 Jan 2019

👍7

Has anyone actually confirmed that things got fixed? It still doesn't work for me today, using thunderbird 60.7.0, CalDav 0.15.0.2, TbSync 1.7 against NextCloud 16.0.3. The TbSync folks seems to have closed it, just telling people to use the security hack workaround... https://github.com/jobisoft/DAV-4-TbSync/issues/41 but its really hard to track which bugs are actually tracking this, as so many were opened across different projects, then closed again, claiming fixed... yet it still doesn't work.

darmbrust on 28 Jul 2019

@darmbrust
Why not just test it?
I just did, switched network.cookie.same-site.enabled back to true (default), closed Thunderbird, removed all cookies via CCleaner (shame on me...), reopened Thunderbird, toggled and re-synced my Lightning calendars and CardBook and it works 😃.
I also created a new calendar and successfully synced with Lightning.
So as long as there is no cache influence or something I forgot, the issue indeed seems to be resolved (Lightning 6.2.8).

MichaIng on 28 Jul 2019

👍4 😄1

Well, I _did_ test it, thats how I got here. I recently set up nextcloud... installed the calendar app today, and tried to sync it with thunderbird, and could not successfully link to my calendar. Not until I changed the cookie setting. And this was with a clean install that has never attempted this before. Happy to change it back and get debug logs... if there is something you want to see....

darmbrust on 29 Jul 2019

@darmbrust I can confirm that plain Thunderbird Lightning without TbSync works.

As pointed out in the mozilla bug report, it was a bug in the mozilla implementation. So if it's still not working in DAV-4-TbSync, perhaps open a new bug report there?

georgehrke on 29 Jul 2019

well, as recently as 15 days ago, people are commenting on that bug that it isn't fixed either.

Though, perhaps they are using the DAV plugin too.

darmbrust on 30 Jul 2019

So, I upgraded Thunderbird to 60.8.0. Tried adding my nextcloud calendar via the Network -> CalDev option directly in Lightening. It adds the calendar... but shows nothing. Sync does nothing.

No errors are shown to the user.

Error log contains stuff like:
503 Service Unavailable.
[calCachedCalendar] replay action failed: null,
uncaught exception.

Toggled network.cookie.same-site.enabled to false, and suddenly the calendar syncs.

So, yea.... probably on the thunderbird side, but still not fixed... and doesn't work at all without finding this obscure toggle.

Of course, Lightening also doesn't let you view or edit the events properly either... they all come up with garbage times if you try to view them... but guessing that is on the lightening side too, since they show up on the calendar GUI with the correct dates and times.

darmbrust on 30 Jul 2019

I cannot confirm any of your described behavior: Neither with Lightning nor with TBSync.
I tested it with:

TB 60.8, TBSync 1.7, CalDavProvider 0.15.0.2, Nextcloud 15.0.10
TB 60.8, Lightning 6.2.5.1, Nextcloud 15.0.10
"network.cookie.same-site.enabled" is set to true in both cases.

Maybe it is any other issue?

brunt82 on 30 Jul 2019

Works for me:

TB 60.8, CardBook 37.5, Nextcloud 15.0.10
TB 60.8, Lightning 6.2.8, Nextcloud 15.0.10

network.cookie.same-site.enabled = true

Benedikt81 on 30 Jul 2019

Maybe this is related to the issue, but I don't understand how people keep reporting they are testing with Lightning 6.2.8 when 6.2.5 is the newest version I see:
https://addons.thunderbird.net/en-US/thunderbird/addon/lightning/versions/

The other difference in versions with my setup, compared to the recent works for me posts is that I'm on NextCloud 16.0.3.

Happy to grab logs / debug from whatever parts people would like to see.

darmbrust on 30 Jul 2019

Ok, guessing this is where the fix landed:
https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&product=Calendar&target_milestone=6.2.5.1&list_id=14828679

6.2.5.1, while my calendar is still at 6.2.5. According to this list:
https://developer.mozilla.org/en-US/docs/Mozilla/Calendar/Calendar_Versions
I'm like 5 versions behind on Lightning.... I know its not your issue, but what the heck is wrong with the Lightning distribution that they aren't pushing their updates to the central update site?

Sigh... reading more, it appears that they want you to uninstall the extension, cause its no longer necessary... as its supposed to be bundled. That is the stupidest update path I've ever heard of.... something tells me they will bite a lot of people with this, when they didn't manage the extension properly for users that already had it installed.... and they aren't properly updating the update site, so if you installed it from there, the older version overrides the integrated version.

I'll retest after sorting this out so I actually get the current version of lightning. If anyone else encounters this bug, it appears that the solution is to uninstall the lightning extension, so that thunderbird will go back to using the embedded one released with it, and not the out-of-date broken version mozilla has published on the update site.

darmbrust on 30 Jul 2019

@darmbrust
~What is wrong about the TB internal addons management? I installed Lightning from there and are automatically updated to the latest version since long time.~

Lol this addons web page gets even worse when you download from the main Lightning page: https://addons.thunderbird.net/en-US/thunderbird/addon/lightning/
You will get 6.2(.0) there 😄. ~However as said I see no reason to use this website for downloading+installing addons manually anyway, at least in case of a single home PC.~

EDIT

Okay now I am confused, TB internal addons management directs you to the same website. Somehow if offers slightly different versions there compared to opening in browser, found 6.2.5 offered indeed now instead of older 6.2(.0). So I am not sure now how I got updated to 6.2.8, if somehow the internal updater finds later versions or the new versions were revoked for some reason at a later time?
Indeed very confusing...

MichaIng on 30 Jul 2019

Ok, there is just a whole lot of stupid with the Mozilla / Lightning / Ubuntu package maintenance folks. I installed Thunderbird using the package manager, but they stripped Lightning, which is supposed to be included. Lightning as published by mozilla is 5 versions out of date. If you uninstall the extension again, its just gone, because Ubuntu stripped it.

To get the proper, up-to-date version, you have to install it using the Ubuntu package manager, (assuming you let ubuntu install thunderbird in the first place) which restores the extension they stripped, and you get the proper 6.2.8 version.

After sorting that out, I can confirm that it is indeed fixed, when using the native remote caldav option. Though I am still seeing issues when trying to use the TBSync addon. But guessing that problem is over there... https://github.com/jobisoft/DAV-4-TbSync/issues/100

darmbrust on 30 Jul 2019

👍3

Okay, then finally things seem to match. Perhaps for @brunt82 the same works, as you're on v6.2.5 as well.

MichaIng on 30 Jul 2019

Anyone here got it to work with thunderbird 68.x? I can't even add an account on TbSync :(

r3pek on 16 Sep 2019

@r3pek
I suggest you open a new issue for this to not mix things with the different 60.x bug that was discussed+solved here.

MichaIng on 16 Sep 2019

@r3pek I would recommend to ask for help in the official Nextcloud help forum first, because this is repository is primarily used to track bugs 😉

j-ed on 16 Sep 2019

I just realized that TB 68 is now released and not beta anymore. However it is common that not all plugins support new versions immediately.

Not sure about the Nextcloud plugin (Lightning/CardBook), will try as well later, but this should then discussed in a separate issue or indeed Nextcloud forum first to verify and collect some info.

EDIT: Just tested and everything I use works very well, Lightning and CardBook including CalDAV/CardDAV sync with my Nextcloud server. I recognised that there is no network.cookie.same-site.enabled setting anymore, but so far no problems without it, as expected due to fix.

MichaIng on 17 Sep 2019

I still cannot get syncing to work in our lab (5+ users). We are on Nextcloud 14/15 using TB 60.x or TB 68.x. Can anyone confirm that upgrading to NC 16 definitively solved their issues?

In my experience the recommended fix using network.cookie.same-site.enabled ceased to work some months ago. It used to work in earlier versions of TB, I have tested various combinations of NC, TB and Lightning - to no avail...

Any experiences / suggestions would be much appreciated - using the web interface for now but usability is less then ideal.

xpressio on 27 Nov 2019

Any experiences / suggestions would be much appreciated - using the web interface for now but usability is less then ideal.

Unfortunately this is the bug tracker for the development and NOT the Nextcloud help forum. You should use the search function of the help forum to find an answer on your question first, before you raise a new request.
I can personally confirm that the original problem described here has already been solved and Thunderbird 68.2.2/Cardbook 43.0 work like a charm with Nextcloud 17.0.1.

j-ed on 27 Nov 2019

I was still facing sync issues with Nextcloud 19 and Thunderbird 68.10 (linux).

SOLVED: I was able to make it work using the TbSync and Provider for CalDAV & CardDAV plugins as suggested in this thread in nextcloud forum.