X
Tap here to go to the mobile version of the site.

Support Forum

How to synchronize calendar with a caldav server using TLS

Posted

Adding a TLS caldav server in the calendar app of Firefox 1.3 causes an error message ("Ein unbekannter Fehler trat auf" - English translation: "An unknown error occurred"). Is there no support for encrypted caldav servers in Firefox OS? And in case it is supported: How do I get more details about the error happening?

The server I try to synchronize with is https://caldav.messagingengine.com. It supports TLS versions 1.0, 1.1 and 1.2.

Adding a TLS caldav server in the calendar app of Firefox 1.3 causes an error message ("Ein unbekannter Fehler trat auf" - English translation: "An unknown error occurred"). Is there no support for encrypted caldav servers in Firefox OS? And in case it is supported: How do I get more details about the error happening? The server I try to synchronize with is https://caldav.messagingengine.com. It supports TLS versions 1.0, 1.1 and 1.2.

Chosen solution

Hi Martin,

Here is the official response from one of the Calendar developers:

  • Caldav is done entirely over http/https and the calendar app is happy to send the xhr requests over ssl if you enter an https url. It's also (currently) happy to send unencrypted http requests though if you give it a url for a server that doesn't support ssl. Hope that helps!

So, it seems that it should technically work, and that you're already adding the CalDav address in a "https" format.

Are you able to access this calendar normally through other calendaring applications? I may need to open a bug for this issue.

- Ralph

Read this answer in context 0

Additional System Details

Application

  • User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0

More Information

Ralph Daub
  • Locale Leader
158 solutions 1182 answers

Helpful Reply

Hi dirichs,

I understand that you would like to set up the Calendar application in your Firefox OS device to access a CalDav server with TLS encryption.

I believe this feature is not currently available, but I forwarded this questions to our team of engineers in the Productivity Applications team for more guidance.

Thanks in advance for your patience while we wait for a definitive answer.

- Ralph

Hi dirichs, I understand that you would like to set up the Calendar application in your Firefox OS device to access a CalDav server with TLS encryption. I believe this feature is not currently available, but I forwarded this questions to our team of engineers in the Productivity Applications team for more guidance. Thanks in advance for your patience while we wait for a definitive answer. - Ralph

Question owner

Hi Ralph,

thanks for your reply, which summarizes accurately the problem I am facing myself - and probably many others as well, if this is a a missing feature.

Did you receive a definite answer from the Productivity Applications team?

Kind regards, Martin Dirichs

Hi Ralph, thanks for your reply, which summarizes accurately the problem I am facing myself - and probably many others as well, if this is a a missing feature. Did you receive a definite answer from the Productivity Applications team? Kind regards, Martin Dirichs
Ralph Daub
  • Locale Leader
158 solutions 1182 answers

Hi Martin,

I have not yet received a definite response from the Productivity Applications team. I contacted them again for a confirmation.

Thank you for your patience.

- Ralph

Hi Martin, I have not yet received a definite response from the Productivity Applications team. I contacted them again for a confirmation. Thank you for your patience. - Ralph
Ralph Daub
  • Locale Leader
158 solutions 1182 answers

Chosen Solution

Hi Martin,

Here is the official response from one of the Calendar developers:

  • Caldav is done entirely over http/https and the calendar app is happy to send the xhr requests over ssl if you enter an https url. It's also (currently) happy to send unencrypted http requests though if you give it a url for a server that doesn't support ssl. Hope that helps!

So, it seems that it should technically work, and that you're already adding the CalDav address in a "https" format.

Are you able to access this calendar normally through other calendaring applications? I may need to open a bug for this issue.

- Ralph

Hi Martin, Here is the official response from one of the Calendar developers: * Caldav is done entirely over http/https and the calendar app is happy to send the xhr requests over ssl if you enter an https url. It's also (currently) happy to send unencrypted http requests though if you give it a url for a server that doesn't support ssl. Hope that helps! So, it seems that it should technically work, and that you're already adding the CalDav address in a "https" format. Are you able to access this calendar normally through other calendaring applications? I may need to open a bug for this issue. - Ralph

Question owner

Hello Ralph,

thank you for your support.

I've now connected the Lightning calendar extension for Thunderbird (on my desktop PC) to the Caldav server Fastmail provides. In the process, I've learned that there are some clients that support auto-discovery of calendars and others that do not support this. Thus I had to use a longer url of the form https://caldav.messagingengine.com/dav/calendars/user/myaccount@fastmail.fm/1234a567-890b-12cd-345e-fa9b0123cdef/

The Lightning calendar client then worked as expected with the longer url. Testing the same url with the Firefox OS calendar unfortunately yielded no success. It's still the same "Unknown error".

Do you know whether it is possible to get a more detailed error log? I would like to help on this issue but the "Unknown error" does not provide any hints about the real cause of the failure.

-Martin

Hello Ralph, thank you for your support. I've now connected the Lightning calendar extension for Thunderbird (on my desktop PC) to the Caldav server Fastmail provides. In the process, I've learned that there are some clients that support auto-discovery of calendars and others that do not support this. Thus I had to use a longer url of the form https://caldav.messagingengine.com/dav/calendars/user/myaccount@fastmail.fm/1234a567-890b-12cd-345e-fa9b0123cdef/ The Lightning calendar client then worked as expected with the longer url. Testing the same url with the Firefox OS calendar unfortunately yielded no success. It's still the same "Unknown error". Do you know whether it is possible to get a more detailed error log? I would like to help on this issue but the "Unknown error" does not provide any hints about the real cause of the failure. -Martin
Ralph Daub
  • Locale Leader
158 solutions 1182 answers

Helpful Reply

Hi Martin,

You can use ADB to do a log of the actions you perform. This would actually be incredibly helpful to the engineers investigating this as well.

You can install ADB by following these steps:

And then run the following command:

adb logcat -v time > calendar.log

And after running the command, do the steps to yield the error you receive.

- Ralph

Hi Martin, You can use ADB to do a log of the actions you perform. This would actually be incredibly helpful to the engineers investigating this as well. You can install ADB by following these steps: * [https://developer.mozilla.org/en-US/Firefox_OS/Debugging/Installing_ADB Installing ADB] And then run the following command: adb logcat -v time > calendar.log And after running the command, do the steps to yield the error you receive. - Ralph

Question owner

Ok, so here it is:

11-04 07:41:22.951 E/GeckoConsole( 4471): Content JS WARN at app://calendar.gaiamobile.org/gaia_build_defer_index.js:1 in consoleWarn: [l10n] #error-caldav-unknown is undefined.

This is the only line of log output that is directly caused by the attempt to add the Caldav server.

-Martin

Ok, so here it is: 11-04 07:41:22.951 E/GeckoConsole( 4471): Content JS WARN at app://calendar.gaiamobile.org/gaia_build_defer_index.js:1 in consoleWarn: [l10n] #error-caldav-unknown is undefined. This is the only line of log output that is directly caused by the attempt to add the Caldav server. -Martin

Question owner

I just tested again using the longish url - and now it worked! Perhaps I made a mistake before with the cryptic url and gave up too soon. It now works. Fantastic!

Short summary:

  • Firefox OS calendar app works with Fastmail calendars (as well as other Caldav servers over http and https)
  • Auto-discovery of calendars (RFC 6764, I assume) it apparently not supported
  • The error message presented to the user could be a bit more meaningful, such as "Caldav server not recognized - please be aware that auto-discovery of calendars is not supported". That would have led me into the right direction much sooner.

Anyway, thanks a lot for your help. I would not have persisted through this issue without your support!

Kind regards,

 Martin Dirichs
I just tested again using the longish url - and now it worked! Perhaps I made a mistake before with the cryptic url and gave up too soon. It now works. Fantastic! Short summary: * Firefox OS calendar app works with Fastmail calendars (as well as other Caldav servers over http ''and'' https) * Auto-discovery of calendars (RFC 6764, I assume) it apparently ''not'' supported * The error message presented to the user could be a bit more meaningful, such as "Caldav server not recognized - please be aware that auto-discovery of calendars is not supported". That would have led me into the right direction much sooner. Anyway, thanks a lot for your help. I would not have persisted through this issue without your support! Kind regards, Martin Dirichs
Ralph Daub
  • Locale Leader
158 solutions 1182 answers

Hi dirichs, that's great to hear!

Thank you very much for writing back to us and letting us know that your problem has been resolved.

I also really appreciate your summary information, as that will be helpful in the future for anyone who is having similar issues and comes to this thread from a Google search. =)

Please welcome to the SUMO forums and feel free to ask any other questions you may have about your Firefox OS device.

Cheers!

- Ralph

Hi dirichs, that's great to hear! Thank you very much for writing back to us and letting us know that your problem has been resolved. I also really appreciate your summary information, as that will be helpful in the future for anyone who is having similar issues and comes to this thread from a Google search. =) Please welcome to the SUMO forums and feel free to ask any other questions you may have about your Firefox OS device. Cheers! - Ralph
Ralph Daub
  • Locale Leader
158 solutions 1182 answers

Hi dirichs,

I opened bug 1095001 to track this issue.

Thanks again for your help testing and troubleshooting this issue on your end. =)

- Ralph

Hi dirichs, I opened [https://bugzilla.mozilla.org/show_bug.cgi?id=1095001 bug 1095001] to track this issue. Thanks again for your help testing and troubleshooting this issue on your end. =) - Ralph
als 0 solutions 21 answers

Hi there,

Could it be the same issue when I try to connect to my owncloud calendar? The URL is like "https://server/owncloud/remote.php/webdav/ ". I searched for "owncloud webdav Auto-discovery", to get an idea of what "auto-discovery" actually does, but only found this: https://forum.owncloud.org/viewtopic.php?f=24&t=17307

Thanks, Albert

Hi there, Could it be the same issue when I try to connect to my owncloud calendar? The URL is like "https://server/owncloud/remote.php/webdav/ ". I searched for "owncloud webdav Auto-discovery", to get an idea of what "auto-discovery" actually does, but only found this: https://forum.owncloud.org/viewtopic.php?f=24&t=17307 Thanks, Albert

Question owner

Hi Albert, I am quite sure that your problem with owncloud is a separate issue and would deserve a thread on its own.

You already seem to have the complete url to use for calendar synchronization. Auto-discovery as specified in RFC 6764 proposes a solution how clients would discovery first the calendar server and then the exact url to use on a particular server. Since you already have a complete url, I don't see a connection with the topic of this thread.

Regards, Martin

Hi Albert, I am quite sure that your problem with owncloud is a separate issue and would deserve a thread on its own. You already seem to have the complete url to use for calendar synchronization. Auto-discovery as specified in RFC 6764 proposes a solution how clients would discovery first the calendar server and then the exact url to use on a particular server. Since you already have a complete url, I don't see a connection with the topic of this thread. Regards, Martin