hi all,
I need to share calendars between two users. both are Zimbra users but with different domains and on different servers. something like this: user1@zimbra1 and user2@zimbra2.
I tried to generate the ICS link on user1@zimbra1 then adding an external calendar on user2@zimbra2 with ICS link from user1@zimbra1, but it says "The following URL is not currently reachable: https://zimbraserver/home/username/Calendar" (if I pase the same link on the browser I can download the ICS file)
also tried adding an external calendar via CalDAV on user2@zimbra2, using credentials from user1@zimbra1. then it list the calendar on user2@zimbra2 but no data is displayed.
what am I missing? is there a better way to do this?
thanks in advance
accessing calendar from Zimbra to another Zimbra using CalDAV
Re: accessing calendar from Zimbra to another Zimbra using CalDAV
I miss to mention. I can access to both calendars via CalDAV using Thunderbird Lightning calendar app.
Re: accessing calendar from Zimbra to another Zimbra using CalDAV
Sorry, posted in wrong Topic.
Re: accessing calendar from Zimbra to another Zimbra using CalDAV
Any ideas on what's going on or where to look about this issue?
- Gren Elliot
- Advanced member
- Posts: 183
- Joined: Tue Jun 10, 2014 4:45 am
Re: accessing calendar from Zimbra to another Zimbra using CalDAV
What URL are you using when you use CalDAV?
Is there anything interesting in mailbox.log? You could always increase the logging level for that using something like:
Is there anything interesting in mailbox.log? You could always increase the logging level for that using something like:
Code: Select all
zmprov aal user@example.com zimbra.datasource trace
Re: accessing calendar from Zimbra to another Zimbra using CalDAV
hi!
i'm adding an external calendar from user1 account, then select Caldav and put user2@zimbra2.com/password2 and mail.zimbra2.com
also tried adding ICS calendar with this url: https://mail.zimbra2.com/home/user2@zim ... m/Calendar
after running zmprov aal user1@zimbra1.com zimbra.datasource trace
this is the error I can see on mailbox.log
i'm adding an external calendar from user1 account, then select Caldav and put user2@zimbra2.com/password2 and mail.zimbra2.com
also tried adding ICS calendar with this url: https://mail.zimbra2.com/home/user2@zim ... m/Calendar
after running zmprov aal user1@zimbra1.com zimbra.datasource trace
this is the error I can see on mailbox.log
Code: Select all
2016-09-03 12:07:28,102 INFO [ScheduledTask-5] [name=user1@zimbra1.com;mid=6;ds=enba;] datasource - Requested import.
2016-09-03 12:07:28,102 INFO [ScheduledTask-5] [name=user1@zimbra1.com;mid=6;ds=enba;] datasource - Importing data for data source 'enba'
2016-09-03 12:07:28,102 DEBUG [ScheduledTask-5] [name=user1@zimbra1.com;mid=6;ds=enba;] datasource - Get all mappings for enba in folder 86609
2016-09-03 12:07:28,207 INFO [ScheduledTask-5] [name=user1@zimbra1.com;mid=6;ds=enba;] datasource - Import completed for data source 'enba'
2016-09-03 12:07:28,207 WARN [ScheduledTask-5] [name=user1@zimbra1.com;mid=6;ds=enba;] datasource - Scheduled DataSource import failed.
com.zimbra.common.service.ServiceException: system failure: error importing CalDAV data
ExceptionId:ScheduledTask-5:1472915248205:ff57d2cf94d70b84
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:260)
at com.zimbra.cs.datasource.CalDavDataImport.importData(CalDavDataImport.java:101)
at com.zimbra.cs.datasource.DataSourceManager.importData(DataSourceManager.java:323)
at com.zimbra.cs.datasource.DataSourceManager.importData(DataSourceManager.java:279)
at com.zimbra.cs.datasource.DataSourceTask.call(DataSourceTask.java:83)
at com.zimbra.cs.datasource.DataSourceTask.call(DataSourceTask.java:31)
at com.zimbra.common.util.TaskScheduler$TaskRunner.call(TaskScheduler.java:69)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: d2:CN17:mail.zimbra2.com1:O27:Zimbra Collaboration Server2:OU27:Zimbra Collaboration Server6:accept4:true5:alias28:mail.zimbra2.com:14339665564:fromi1433966559000e4:host17:mail.zimbra2.com3:icn17:mail.zimbra2.com2:io27:Zimbra Collaboration Server3:iou27:Zimbra Collaboration Server3:md532:D69207E4E2F12553A53D8A896466FE878:mismatch5:false1:s10:14339665564:sha140:DB6830EB83A9EA4665FD2DC512C240AE4302744D2:toi1591646559000ee
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1917)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:301)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:295)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1369)
at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:156)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:925)
at sun.security.ssl.Handshaker.process_record(Handshaker.java:860)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1043)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1343)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1371)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1355)
at com.zimbra.common.net.CustomSSLSocket.startHandshake(CustomSSLSocket.java:95)
at com.zimbra.common.net.CustomSSLSocket.getInputStream(CustomSSLSocket.java:360)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:745)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at com.zimbra.common.httpclient.HttpClientUtil.executeMethod(HttpClientUtil.java:58)
at com.zimbra.common.httpclient.HttpClientUtil.executeMethod(HttpClientUtil.java:44)
at com.zimbra.cs.dav.client.WebDavClient.executeMethod(WebDavClient.java:204)
at com.zimbra.cs.dav.client.WebDavClient.execute(WebDavClient.java:183)
at com.zimbra.cs.dav.client.WebDavClient.executeFollowRedirect(WebDavClient.java:159)
at com.zimbra.cs.dav.client.WebDavClient.sendMultiResponseRequest(WebDavClient.java:94)
at com.zimbra.cs.dav.client.CalDavClient.login(CalDavClient.java:106)
at com.zimbra.cs.datasource.CalDavDataImport.getClient(CalDavDataImport.java:167)
at com.zimbra.cs.datasource.CalDavDataImport.syncFolders(CalDavDataImport.java:221)
at com.zimbra.cs.datasource.CalDavDataImport.importData(CalDavDataImport.java:90)
... 11 more
Caused by: java.security.cert.CertificateException: d2:CN17:mail.zimbra2.com1:O27:Zimbra Collaboration Server2:OU27:Zimbra Collaboration Server6:accept4:true5:alias28:mail.zimbra2.com:14339665564:fromi1433966559000e4:host17:mail.zimbra2.com3:icn17:mail.zimbra2.com2:io27:Zimbra Collaboration Server3:iou27:Zimbra Collaboration Server3:md532:D69207E4E2F12553A53D8A896466FE878:mismatch5:false1:s10:14339665564:sha140:DB6830EB83A9EA4665FD2DC512C240AE4302744D2:toi1591646559000ee
at com.zimbra.common.net.CustomTrustManager.checkServerTrusted(CustomTrustManager.java:92)
at sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:865)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1351)
... 35 more
Re: accessing calendar from Zimbra to another Zimbra using CalDAV
i could not solve this, yet... any ideas?
- Gren Elliot
- Advanced member
- Posts: 183
- Joined: Tue Jun 10, 2014 4:45 am
Re: accessing calendar from Zimbra to another Zimbra using CalDAV
The errors suggest that there are certificate problems on your servers.