Donât forget to write the complete url of your calendar in Thunderbird/Lightning
https://your-server/remote.php/dav/calendars/your-user-name/name-of-the-calendar/
and https://your-server/remote.php/dav/calendars/your-user-name/contact_birthdays/
Yes, Iâm using the full URL. And it used to work for many years actually. But since my provider updated to http2 it does not work anymore with Thunderbird/Lightning but all other clients still work.
O.K. meanwhile be sure that the openssl library version is = 1.0.2 or greater.
The1.0.2 version include specification RFC7301 (protocol ALPN) required for being able to accept HTTP/2 negociations.
The 1.0.1 version permit only NPN protocol wich is now obsolete.
I know some administrators have been obliged to tweak their ciphers (no cipher from a specified black list may be used) but i didnât have to do that here. Anyway must be a problem with your hosting provider.
I have to correct myself: The issue was that two users obviously didnât enter their passwords correctly, although they were 100% sure they did. The question remains, why Lightning wants them to reenter their credentials after migration, but anyways, it works now.
Sorry to barge in on this thread and I hope youâll find a solution soon!
I have the same problem, since I switched my server to http/2.
Actually I was hoping that adding it with Protocols h2 h2c http/1.1 would allow it to fall back to http/1.1 if http/2 is not working. But I also enabled H2Direct, which I read brings some compatibility issues. I will try it without and see if it helps. But it will take time until tomorrow. My preview generator is still pre-generating previews of dozens GB of pictures .
Opera Mini actually works fine for me, with and without data compression (inaktiv while WLAN connection). I use the newest beta 21.0.2254, maybe they added support recently.
http://caniuse.com/#feat=http2 shows browser compatibility. Opera Mini is still listed as unsupported. Maybe this changed in the current beta, maybe it just works because of successful http/1.1 fall-back?
âŹ: disable H2Direct directive doesnât fix the thunderbird issue. I also updated thunderbird and lightning to the current beta (50 beta 3) but still no http2 support. Poor thing⌠maybe someone with access to mozilla forums can give some hint there.
âŹâŹ: Okay, the latest issue was just because of the calender cache could not be touched or something. I deleted to old ones and added the exactly same DAV urls again and now it works. Also the contacts now work, why ever . I donât know if this is new, but at least in the thunderbird 50 beta there is also some setting in about:config to enable/disable SPDY and http2 suppoert.
I finally found a workaround and got Thunderbird/Lightning got to sync again with nextcloud
The workaround is to set ânetwork.http.spdy.enabled.http2â to false in the Thunderbird config.
See also https://bugzilla.mozilla.org/show_bug.cgi?id=1106727#c18
Interesting, for me actually it worked after removing and adding the caldav calendars again, with ânetwork.http.spdy.enabled.http2 = trueâ.
But as mentioned above, I used version 50 beta, the stable one seems to be still in the 40s. The fix might be implemented in between.
It seems that I have a similar problem (see here), but setting network.http.spdy.enabled.http2 to false did not fix it. This said, going back in this thread, I see that the version of OpenSSL on my server is not âĽ1.0.2:
# openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
Could that be the issue? If that is the case, is there any workaround? I am on a shared server and it is not in my power to update OpenSSLâŚ
Thanks MikeLupe for your answer. It does help to see Iâm not the only one having this problem⌠but it did not fix my issue, unfortunately.
I went a bit deeper in my tests and trials, including trying an empty profile and changing a hidden pref, to no avail (details in this thread). Any suggestion would be greatly appreciated.
I know this is rather an old thread, but I suddenly started experiencing the exact issue first described. The change, in my case, was a move from using the fastcgi mod in Apache 2.4 for php5-fpm to using the proxy_fcgi alternative. The result is that Lightning no longer connects to Nextcloud calendars.
The issue can be seen in the nextcloud log as "No âAuthorization: Basicâ header found. Either the client didnât send one, or the server is misconfigured,"
The difference is that, under the fastcgi option, the parameter â-pass-header Authorizationâ is added to the php5-fpm socket description, while this is not usual, or possible, when passing as a proxy.
The issue seems to be resolved in apache 2.4.13 and above, with a âCGIPASSAUTHâ directive, but this is not available under earlier versions. In theory, according to what I have found, adding âSetEnvIf Authorization â(.*)â HTTP_AUTHORIZATION=$1â to the .htaccess should work, but this is already in Nextcloudâs .htaccess
Hope this helps someone.
As of now, I have no solution, but I think, at least, I have understood the issue.
I have stumbled on a solution, but to be honest, I do not understand the reason. I have been able to confirm that using php5-fpm with proxy_fcgi is the cause of authorisation issues, resulting in Lightning not being able to connect correctly to the NC server. Reverting to mod_fastcgi resolves the problem, but it seems NC devs are aware of this, and add relevant use cases into the .htaccess file. Unfortunately this still does not resolve the problem. Eventually I stumbled on an incantation that resolves this, using a proxy directive ahead of a SetHandler directive, and with this, mod_proxy_fcgi option with php5-fpm works for Lightning, as before.
The way I have done this is to add and enable a âphp5-fcgi.confâ with the following
<Proxy âfcgi://localhost:9000/â>