i think it could depend on how the clients (e.g. Davdroid works, Thunderbird not) sends the authorization information. Maybe Thunderbird handles this different and has some issues with connecting to the ownCloud server?
I just encountered this situation. It affected my calendars and my address book. Once the initial panic subsided, I made similar determinations as those shared in the OP. DavX5 (FKA Davdroid) was working. Only Thunderbird was failing.
I had just added Duo and OAuth to my ownCloud the night before, so I spent a little more time than necessary focused on app passwords. Once I found the 401 response in the Thunderbird error console, I performed further diagnosis using private browsing of the DAV URLs in Firefox.
I was able to implement a workaround from the following findings. The URLs as shown in ownCloud are listed below under the label of ‘not working’ since they failed to trigger an authorization request and just failed immediately, The ones labeled ‘working’ provided the necessary HTTP authorization prompt.
Mine was fine with the dav links right up until I added Duo and OAuth apps.
I added both during the same evening prior to noticing that I was hitting 401s in Thunderbird, so I can’t really narrow it down further than those two apps for now.
I’m glad to have a functioning workaround in place until I can do further testing.
I’d like to see OAuth support for CardDAV/CalDAV in Thunderbird (technically SoGo Connector & Lightning in my case) just like it does with Google accounts, but that’s input that I need to provide over on those projects rather than here.
I don’t think that I’ve configured 2 factor authentication with Owncloud, unless this is the default configuration, which I have some doubt that it is the case. There is another Owncloud app for 2 factor authentication https://marketplace.owncloud.com/apps/twofactor_totp which I don’t have installed. So I don’t think that is the problem.
I have even deactivated the OAuth2 app, but the issue persists. So it’s probably not OAuth that is the problem.
While the workaround from LinkP works well for 1 single calendar, it doesn’t if I add a second calendar with different username and password. Then a similar thing happens as before. There is no password prompt for the second calendar. Hence the second calendar is not working. I get a triangle on the calendar name with this error message when I hover with the mouse arrow on that traingle:
Thunderbird calendar 'momentarily not available
I’ve reproduced this problem on a different PC with Windows TB instead of Linux TB. Once I remove my primary calendar, restart TB and add the secondary calendar, then this calendar works fine. So it’s not an issue with the secondary calendar itself, but simply 2 calendars at the same time with a different user name and password.
So my problem is only partly solved. For the time being I’ll use a second TB in a virtual machine for my other calendar, but that is of course also only a workaround that is not ideal.
then i think it would indeed make sense to report this to the ownCloud developers. If the OAuth2 app isn’t the problem then maybe the following bugtracker could fit: https://github.com/owncloud/core/issues
great, same server account was the problem.
at least on Windows, but on Linux I do now get a log-in prompt and the credentials are accepted, but the calendar is not loading. The triangle is still there. There is also some info available here, but I think I will just wait until I’ve upgrade my Mint installation soon and hope it will work right away.
I don’t quite get why multirealm is not enabled by default in TB. A regular user would have no chance of solving this issue. Even I , with my years of experience in IT was not even able to find the solution on the internet myself.
Since this is a TB issue, the documentation should be in really in Lightning documentation. But, yes in the Owncloud doc’s it would be also good.
Anyways, thanks for your help.
Update: I’ve unsubcribed from the second calendar, close TB and reopened it. Then added the calendar again and for some reason it worked. I have to say that I did this a few times before. I’ve not idea why it now works.
Either way , this issue is now also solved …until the next installation
Update 2: it looks like Cardbook has the same multirealm issue with CardDav. I’m not able to add 2 addressbooks from the same server. But since this is not critical to me, I will just leave it.
i’m not sure if the linked mozilla bugreport is related. From what i know/have read in the ownCloud is using Basic authentication but the bugreport is about Digest authentication.
But it seems a few other open bugreports are available there about calendar.network.multirealm:
so if i understand this correctly one URL works with an app password where another one doesn’t? If this is the case then i think it is really required to open a bug report to the ownCloud devs.
No. There were a lot of unrelated replies posted between mine and the one I was replying to, so I should add some clarification. I am having no issues whatsoever after changing the URL as indicated in my earlier reply. I am using multiple calendars, but they are all from the same ownCloud account.
The problem @Dude11 is experiencing appears to be multiple issues. One of which I experienced with the OAuth application interfering with Thunderbird (Lightning) access to the official calendar URL. The other is accessing calendars from 2 accounts, which is something I don’t employ, so I have not experienced it.