-

Thu, 06 May 2021 06:07:07 -0700

Hubzilla Support Forum

adminsforum@hubzilla.org

RockyIII schrieb den folgenden Beitrag Thu, 06 May 2021 06:07:07 -0700

CalDAV Calendar syncing with Thunderbird / Lighting

Just tested the HZ CalDAV Calendar once more. and with the android app DAVx it just works perfect

!!!

Than i tried it with Thunderbird / Lighting and here is what i found out:

I could NOT connect to any HZ CalDAV Calendar by CalDAV but by syncing the downloadable ics file. This was working fine if the ics file came from the account of the HZ CalDAV Calendar owner. If the ics file came from a shared CalDAV Calendar of a HZ contact this ics sync did NOT work, now idea why... is this a bug?

But why in the first place connecting by CalDAV does not work - is this something to work on an the Thunderbird / Lighting side?

mehr anzeigen 10

Thu, 06 May 2021 06:39:53 -0700

Stefan Haydn

sh@hub.hayfidelity.de

Have you tried the addon TBSync? That works for me with my caldav calendars, but haven't tried it with Hubzilla yet.

Thu, 06 May 2021 06:53:17 -0700

Stefan Haydn

sh@hub.hayfidelity.de

Yes, works for me.

You also need CalDAV & CardDAV inside TBSync. Then use your username and as servername https://hub.domain.com/cdav.

Thu, 06 May 2021 06:59:34 -0700

RockyIII

rockyiii@huby.infozoo.de

THANKS Stefan

just tried it with the addons

https://addons.thunderbird.net/de/thunderbird/addon/tbsync/
and
https://addons.thunderbird.net/de/thunderbird/addon/dav-4-tbsync/

on two different hubs - and it did not work

here are the two error logs:

URL:
https://hubzilla.eu/cdav/.well-known/carddav (PROPFIND)

Request:
<d:propfind xmlns:d="DAV:"><d:prop><d:current-user-principal /></d:prop></d:propfind>

Response:
<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
  <s:sabredav-version>4.1.5</s:sabredav-version>
  <s:exception>Sabre\DAV\Exception\NotFound</s:exception>
  <s:message>File not found: .well-known in 'root'</s:message>
</d:error>

and

URL:
https://lokal.social/cdav/.well-known/carddav (PROPFIND)

Request:
<d:propfind xmlns:d="DAV:"><d:prop><d:current-user-principal /></d:prop></d:propfind>

Response:
<html>
<head>
<title>403 Forbidden</title>
</head>
<body bgcolor="white">
<center>
<h1>403 Forbidden</h1>
</center>
<hr>
<center>nginx</center>
</body>
</html>

Thu, 06 May 2021 07:15:19 -0700

Stefan Haydn

sh@hub.hayfidelity.de

Hmmm...don't know what could be causing this. Do you use your channelname as username, like it is rockyiii here?

Thu, 06 May 2021 07:17:23 -0700

RockyIII

rockyiii@huby.infozoo.de

it woks with the addons !!!!

if an CalDAV account is added by the addons you have to choose "Benutzerdefinierte Konfiguration" and NOT the "Automatische Konfiguration"

PERFECT now-- verrrryyyy nice

Thu, 06 May 2021 07:29:15 -0700

Stefan Haydn

sh@hub.hayfidelity.de

Ah, yes, use userdefined.

Thu, 06 May 2021 07:38:47 -0700

Max Kostikov

kostikov@zotum.net

@RockyIII

https://lokal.social/cdav/.well-known/carddav

That's incorrect path. Correct is /.well-known/carddav
It return an access point which is requires authorization by default.

root@zotum:~ # curl -IL --request PROPFIND https://zotum.net/.well-known/carddav
HTTP/2 301
server: h2o/2.3.0-beta2
strict-transport-security: max-age=15768000; includeSubDomains; preload
public-key-pins: pin-sha256="poJyhjPZzT5gjdeEQv/vLCYBQj4TZX8q3sC55J3DT9A="; pin-sha256="J1WRnIaYoqOlbnvJQsJDWa6J6a7/al4sq13C4wG+5Iw="; max-age=2592000; includeSubDomains
date: Thu, 06 May 2021 14:34:38 GMT
set-cookie: PHPSESSID=e011affba67ea5732bd5980d7eccd4b7; path=/; secure; HttpOnly
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
location: https://zotum.net/cdav
content-type: text/html; charset=UTF-8

HTTP/2 401
server: h2o/2.3.0-beta2
strict-transport-security: max-age=15768000; includeSubDomains; preload
public-key-pins: pin-sha256="poJyhjPZzT5gjdeEQv/vLCYBQj4TZX8q3sC55J3DT9A="; pin-sha256="J1WRnIaYoqOlbnvJQsJDWa6J6a7/al4sq13C4wG+5Iw="; max-age=2592000; includeSubDomains
date: Thu, 06 May 2021 14:34:38 GMT
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
set-cookie: PHPSESSID=8fe99797308d30f9a316599325072b00; path=/; secure; HttpOnly
set-cookie: PHPSESSID=8fe99797308d30f9a316599325072b00; path=/; secure; HttpOnly
x-sabre-version: 4.1.5
content-type: application/xml; charset=utf-8
vary: Brief,Prefer
dav: 1, 3, extended-mkcol, resource-sharing, access-control, calendarserver-principal-property-search, calendar-access, calendar-proxy, calendarserver-sharing, addressbook
www-authenticate: Basic realm="HubzillaCalDAV/CardDAV", charset="UTF-8"

Thu, 06 May 2021 22:57:33 -0700

Mario Vavti

mario@hub.somaton.com

If the client supports discovery via the .well-known endpoint you should probably just enter as the url.

Fri, 07 May 2021 02:39:51 -0700

RockyIII

rockyiii@huby.infozoo.de

with dav-4-tbsync + tbsync and userdefined settings it works with /cdav

Fri, 07 May 2021 02:55:41 -0700

Manuel JF

manuel-jf@hub.volse.no

I've been using it since it was implemented in Hubzilla, synchronised with thunderbird and Android. I don't even remember the settings anymore, but they were pretty easy. It has never failed.