I'm trying to connect to a self-signed https (ssl) CalDAV server.
Apple Miniserver OSX 10.8

Rainlendar cannot find the calendars for the login (which is correct) and gives an 'Unable to connect to server' error when running.

With other CalDAV clients (iCal, Calendar on iOS and Outlook) I have to tell the client to trust the server. As the server is self-signed the other clients don't want to trust it and give an error. But there is an option to trust the server.

Does Rainlendar have something similar?

Cheers

Further to this... I tried putting in the full principals URL as in the iCloud/iCal instructions. It now gives me a 'Unable to authenticate server' error which tells me it is the Self-Signed SSL certificate that is causing the problem.

An option to trust the server would be excellent!

Rainlendar does not validate the server's certificate so also the self signed certificates should work too. Authentication error suggest that the username/password or the authentication mode is incorrect. If you run Rainlendar in the debug mode you can find more details about the connection from the debug log.

Thank you.. trying the various Authentication methods but no go. My CalDAV server is OSX 10.8 which I know does not have good legacy support with NTLM
There is an Error in the debug log:

10:06:33 PM: [0:07:04.301] **********.Staff: Making request: ***********.mooo.com:8443
10:06:33 PM: [0:07:04.842] **********.Staff: Result: (0) 401 Unauthorized.
10:06:33 PM: [0:07:04.842] ERROR: **********.Staff: The calendar-home-set is not set for the calendar.
10:06:41 PM: [0:07:12.295] WARNING: ASSERT: ..\..\src\msw\dialog.cpp:-1040251892

Looks like I managed to authenticate using Digest protocol.
However I cannot get the contents:

**********.Staff: Making request: **********.mooo.com:8443
10:18:29 PM: [0:19:00.616] **********.Staff: Result: (0) 207 Multi-Status.
10:18:29 PM: [0:19:00.617] **********.Staff: Making request: **********.mooo.com:8443/principals/__uids__/E8C4A1C1-9619-4933-983D-54C35AB07B30/
10:18:29 PM: [0:19:01.042] **********.Staff: Result: (0) 207 Multi-Status.
10:18:29 PM: [0:19:01.043] **********Staff: Making request: **********.mooo.com:8443/calendars/__uids__/E8C4A1C1-9619-4933-983D-54C35AB07B30/
10:18:30 PM: [0:19:01.598] **********.Staff: Result: (0) 207 Multi-Status.
10:18:30 PM: [0:19:01.599] **********.Staff: Making request: **********.mooo.com:8443/calendars/__uids__/E8C4A1C1-9619-4933-983D-54C35AB07B30/calendar/
10:18:31 PM: [0:19:02.733] **********.Staff: Result: (0) 207 Multi-Status.
10:18:31 PM: [0:19:02.738] WARNING: **********.Staff: Found some events but the server didn't send any content for them. Let's try with calendar-multiget instead.
10:18:31 PM: [0:19:02.738] **********.Staff: Making request: **********.mooo.com:8443/calendars/__uids__/E8C4A1C1-9619-4933-983D-54C35AB07B30/calendar/
10:18:31 PM: [0:19:03.049] **********.Staff: Result: (0) 400 Bad Request.
10:18:31 PM: [0:19:03.049] **********.Staff: Read 0 items from url "**********.mooo.com:8443/calendars/__uids__/E8C4A1C1-9619-4933-983D-54C35AB07B30/calendar/"

If you are using the same CalDAV server as Apple has in iCloud then it is not going to work. The iCloud server doesn't support any of the ways to fetch the events that work on other servers so I had to do things differently for iCloud. Unfortunately the workaround is currently hardcoded to be used only for icloud.com. I'll see if it could be made into a setting or done somehow automatically if everything else fails.