Rainlendar - Rainlendar with DAViCal

Welcome, Guest
Please Login or Register. Lost Password?

Kunena

Rainlendar2

Support

Rainlendar with DAViCal

(1 viewing) (1) Guest

Page: 1

TOPIC: Rainlendar with DAViCal

Forum Tools

#18204

Rainlendar with DAViCal 8 Months ago

Hello!

I'm using my own DAViCal-Server with Thunderbird and my iPhone. With this clients everything works right.

Yesterday I tried to connect my Rainlendar installation with my server, after I found Rainlendar listed as supported client at wiki.ubuntuusers.de/DAViCal.

The existing entries have been successfully displayed. But if I try to enter a new date, I get a error message "405 Method Not Allowed". At the server log I counldn't find any meaningful information.

Do you have any idea, what I can do, to get the connection running complete?

I tested with "Rainlendar-Pro-2.10-64bit.exe" and the actual beta "Rainlendar-2.11.b125-64bit.zip".

Many thanks and greetings!
Matthias

matthiasvogt

Fresh Boarder

Posts: 1

The administrator has disabled public write access.

#18222

Re: Rainlendar with DAViCal 8 Months ago
You are probably trying to access the calendar with the WebDAV protocol ("Network Shared Calendar" in Rainlendar) instead with the CalDAV which is only available in the newer beta versions. I tried this and with CalDAV Rainlendar is able to write events to the server but it cannot read them so it's not very useable. I'll see if there is something I can do about this.

Rainy

Moderator

Posts: 5401

The administrator has disabled public write access.

#18772

Re: Rainlendar with DAViCal 4 Months, 2 Weeks ago

Hi Rainy,

... with CalDAV Rainlendar is able to write events to the server but it cannot read them...

I'm phasing similar problems with a Synology Diskstation server. Please find below some lines of the debug log. As I stated in the other thread, Lightning has no problems to access the calendar.

I would appreciate, if somebody could give a hint, how to solve this problem.

Kind regards
Karsten

Code:

20:37:49: [0:00:05.086] CURLINFO_DATA_OUT: <?xml version="1.0" encoding="utf-8" ?>

<D:propfind xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav"><D:prop><D:getetag/><C:calendar-data/></D:prop></D:propfind>

20:37:49: [0:00:05.086] CURLINFO_TEXT: We are completely uploaded and fine

20:37:49: [0:00:05.108] CURLINFO_HEADER_IN: HTTP/1.1 207 Multi-Status

20:37:49: [0:00:05.108] CURLINFO_HEADER_IN: Date: Sun, 03 Feb 2013 19:40:43 GMT

20:37:49: [0:00:05.108] CURLINFO_HEADER_IN: Server: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.1c-fips DAV/2

20:37:49: [0:00:05.108] CURLINFO_HEADER_IN: Content-Length: 1459

20:37:49: [0:00:05.108] CURLINFO_HEADER_IN: Content-Type: application/xml; charset="utf-8"

20:37:49: [0:00:05.108] CURLINFO_HEADER_IN:

20:37:49: [0:00:05.109] CURLINFO_DATA_IN: <?xml version="1.0" encoding="utf-8"?>

<D:multistatus xmlns:D="DAV:" xmlns:ns1="urn:ietf:params:xml:ns:caldav" xmlns:ns0="DAV:">

<D:response xmlns:lp1="DAV:" xmlns:lp2="http://apache.org/dav/props/" xmlns:g0="urn:ietf:params:xml:ns:caldav">

<D:href>/Dokumente/Kalender/Entsorgung/</D:href>

<D:propstat>

<D:prop>

<lp1:getetag>"4d4d6da377500"</lp1:getetag>

</D:prop>

<D:status>HTTP/1.1 200 OK</D:status>

</D:propstat>

<D:propstat>

<D:prop>

<g0:calendar-data/>

</D:prop>

<D:status>HTTP/1.1 404 Not Found</D:status>

</D:propstat>

</D:response>

<D:response xmlns:lp1="DAV:" xmlns:lp2="http://apache.org/dav/props/" xmlns:g0="urn:ietf:params:xml:ns:caldav">

<D:href>/Dokumente/Kalender/Entsorgung/32259bca-6e36-11e2-97a7-27a87aea13d7.ics</D:href>

<D:propstat>

<D:prop>

<lp1:getetag>"4d4d6da377500"</lp1:getetag>

</D:prop>

<D:status>HTTP/1.1 200 OK</D:status>

</D:propstat>

<D:propstat>

<D:prop>

<g0:calendar-data/>

</D:prop>

<D:status>HTTP/1.1 404 Not Found</D:status>

</D:propstat>

</D:response>

<D:response xmlns:lp1="DAV:" xmlns:lp2="http://apache.org/dav/props/" xmlns:g0="urn:ietf:params:xml:ns:caldav">

<D:href>/Dokumente/Kalender/Entsorgung/fe7586b7-6f5b-4896-8150-8487874a581f.ics</D:href>

<D:propstat>

<D:prop>

<lp1:getetag>"4d4d6675bc540"</lp1:getetag>

</D:prop>

<D:status>HTTP/1.1 200 OK</D:status>

</D:propstat>

<D:propstat>

<D:prop>

<g0:calendar-data/>

</D:prop>

<D:status>HTTP/1.1 404 Not Found</D:status>

</D:propstat>

</D:response>

</D:multistatus>

20:37:49: [0:00:05.109] CURLINFO_TEXT: Connection #0 to host diskstation left intact

20:37:49: [0:00:05.109] Entsorgung2: Result: (0) 207 Multi-Status.

20:37:49: [0:00:05.109] CURLINFO_TEXT: Closing connection #0

20:37:49: [0:00:05.109] CURLINFO_TEXT: SSLv3, TLS alert, Client hello (1):

20:37:49: [0:00:05.109] 

20:37:49: [0:00:05.112] WARNING: Entsorgung2: Found some events but the server didn't send any content for them. Let's try with calendar-multiget instead.

20:37:49: [0:00:05.112] Entsorgung2: Making request: https://diskstation:5006/Dokumente/Kalender/Entsorgung/

20:37:49: [0:00:05.112] CURLINFO_TEXT: About to connect() to diskstation port 5006 (#0)

20:37:49: [0:00:05.112] CURLINFO_TEXT:   Trying IP_ADDRESS...

20:37:49: [0:00:05.113] CURLINFO_TEXT: connected

20:37:49: [0:00:05.113] CURLINFO_TEXT: Connected to diskstation (IP_ADDRESS) port 5006 (#0)

20:37:49: [0:00:05.129] CURLINFO_TEXT: successfully set certificate verify locations:

20:37:49: [0:00:05.129] CURLINFO_TEXT:   CAfile: /etc/ssl/certs/ca-certificates.crt

  CApath: none

20:37:49: [0:00:05.129] CURLINFO_TEXT: SSLv3, TLS handshake, Client hello (1):

20:37:49: [0:00:05.129] 

20:37:49: [0:00:05.186] CURLINFO_TEXT: SSLv3, TLS handshake, Server hello (2):

20:37:49: [0:00:05.186] 

20:37:49: [0:00:05.186] CURLINFO_TEXT: SSLv3, TLS handshake, CERT (11):

20:37:49: [0:00:05.186] 

20:37:49: [0:00:05.187] CURLINFO_TEXT: SSLv3, TLS handshake, Server key exchange (12):

20:37:49: [0:00:05.187] 

20:37:49: [0:00:05.187] CURLINFO_TEXT: SSLv3, TLS handshake, Server finished (14):

20:37:49: [0:00:05.187] 

20:37:49: [0:00:05.192] CURLINFO_TEXT: SSLv3, TLS handshake, Client key exchange (16):

20:37:49: [0:00:05.192] 

20:37:49: [0:00:05.192] CURLINFO_TEXT: SSLv3, TLS change cipher, Client hello (1):

20:37:49: [0:00:05.192] 

20:37:49: [0:00:05.192] CURLINFO_TEXT: SSLv3, TLS handshake, Finished (20):

20:37:49: [0:00:05.192] 

20:37:49: [0:00:05.239] CURLINFO_TEXT: SSLv3, TLS change cipher, Client hello (1):

20:37:49: [0:00:05.239] 

20:37:49: [0:00:05.239] CURLINFO_TEXT: SSLv3, TLS handshake, Finished (20):

20:37:49: [0:00:05.239] 

20:37:49: [0:00:05.239] CURLINFO_TEXT: SSL connection using DHE-RSA-AES256-SHA

20:37:49: [0:00:05.239] CURLINFO_TEXT: Server certificate:

20:37:49: [0:00:05.239] CURLINFO_TEXT: 	 subject: C=TW; ST=Taiwan; L=Taipei; O=Synology Inc.; OU=FTP Team; CN=synology.com; emailAddress=product@synology.com

20:37:49: [0:00:05.239] CURLINFO_TEXT: 	 start date: 2011-03-11 12:43:00 GMT

20:37:49: [0:00:05.239] CURLINFO_TEXT: 	 expire date: 2030-11-26 12:43:00 GMT

20:37:49: [0:00:05.239] CURLINFO_TEXT: 	 issuer: C=TW; ST=Taiwan; L=Taipei; O=Synology Inc.; OU=Certificate Authority; CN=Synology Inc. CA; emailAddress=product@synology.com

20:37:49: [0:00:05.240] CURLINFO_TEXT: 	 SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.

20:37:49: [0:00:05.240] CURLINFO_TEXT: Server auth using Basic with user 'XXXX'

20:37:49: [0:00:05.240] CURLINFO_HEADER_OUT: REPORT /Dokumente/Kalender/Entsorgung/ HTTP/1.1

Authorization:<REMOVED FROM LOG>

User-Agent: Rainlendar-CalDAVPlugin/1.0

Host: diskstation:5006

Accept: */*

Content-Type: application/xml; charset="utf-8"

DEPTH:0

Content-Length: 409

Expect: 100-continue

20:37:49: [0:00:05.280] CURLINFO_HEADER_IN: HTTP/1.1 100 Continue

20:37:49: [0:00:05.280] CURLINFO_DATA_OUT: <?xml version="1.0" encoding="utf-8" ?>

<C:calendar-multiget xmlns:D="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav"><D:prop><D:getetag/><C:calendar-data/></D:prop><D:href>/Dokumente/Kalender/Entsorgung/fe7586b7-6f5b-4896-8150-8487874a581f.ics</D:href><D:href>/Dokumente/Kalender/Entsorgung/</D:href><D:href>/Dokumente/Kalender/Entsorgung/32259bca-6e36-11e2-97a7-27a87aea13d7.ics</D:href></C:calendar-multiget>

20:37:49: [0:00:05.280] CURLINFO_TEXT: We are completely uploaded and fine

20:37:49: [0:00:05.299] CURLINFO_HEADER_IN: HTTP/1.1 404 Not Found

20:37:49: [0:00:05.299] CURLINFO_HEADER_IN: Date: Sun, 03 Feb 2013 19:40:43 GMT

20:37:49: [0:00:05.299] CURLINFO_HEADER_IN: Server: Apache/2.2.22 (Unix) mod_ssl/2.2.22 OpenSSL/1.0.1c-fips DAV/2

20:37:49: [0:00:05.299] CURLINFO_HEADER_IN: Cache-Control: no-cache

20:37:49: [0:00:05.299] CURLINFO_HEADER_IN: Content-Length: 0

20:37:49: [0:00:05.299] CURLINFO_HEADER_IN: Content-Type: httpd/unix-directory

20:37:49: [0:00:05.299] CURLINFO_HEADER_IN:

20:37:49: [0:00:05.299] CURLINFO_TEXT: Connection #0 to host diskstation left intact

20:37:49: [0:00:05.300] Entsorgung2: Result: (0) 404 Not Found.

20:37:49: [0:00:05.300] CURLINFO_TEXT: Closing connection #0

20:37:49: [0:00:05.300] CURLINFO_TEXT: SSLv3, TLS alert, Client hello (1):

20:37:49: [0:00:05.300] 

20:37:49: Error: XML parsing error: 'no element found' at line 1

20:37:49: [0:00:05.303] Entsorgung2: Read 0 items from url "https://diskstation:5006/Dokumente/Kalender/Entsorgung/"

zergman

Fresh Boarder

Posts: 3

The administrator has disabled public write access.

#18784

Re: Rainlendar with DAViCal 4 Months, 1 Week ago
The server doesn't seem to support neither of the methods that Rainlendar uses to read the events. Unfortunately to be able to fix the problem I would have to have access to the server to see how Lightning communicates with it.

Rainy

Moderator

Posts: 5401

The administrator has disabled public write access.

Page: 1

Kunena

Rainlendar2

Support