[CalendarServer-dev] SOLVED: HTTPS-Problem

Georg Troska georg.troska at uni-dortmund.de
Thu Feb 19 10:09:53 PST 2009

Hi Wilfredo ,
thank you very much,

I found this out in this morning already. I had answered to the users- 
list already (see below) but forgot to mark this topic as solved in  
the dev-list
> Dear Cyrille,
> It's so easy.... so clear that I need nearly two days to understand...
> The point is to tell iCal to accept the certificate. As I accepted  
> it with my Browser and I saw that it was stored in apple service  
> programm where the certs and keys (not sure about the english name)  
> I thought every must be ok.
> To tell iCal to accept the certs one has to open the SSL-Site with  
> safari - not with firefox. When I had accepted the certs with safari  
> everything in iCal was ok
> Thanks you very much for the time you spent on this
> Georg
> P.S. maybe someone can add this iCal feature to the iCal-Howto on www.calendarserver.org

Thank you very much also for you time


Am 19.02.2009 um 19:04 schrieb Wilfredo Sánchez Vega:

> On Feb 18, 2009, at 6:08 AM, Georg Troska wrote:
>> "The account inforation could not be found - Unexpected error at  
>> the secure name resoltion (Error -9813). The servername <name> is  
>> maybe incorrect "
>  "Secure name resolution" usually means, I think, that something is  
> fishy about your certificate and the client can't validate it.  It's  
> not my favorite error message.
>  One way to validate that SSL is otherwise working on your server is  
> to try loading up /calendars on it in Safari.  If that works, the  
> problem is probably a cert issue.
> 	-wsv

Georg Troska
Experimentelle Physik IV
TU Dortmund
+49 231 755 3501

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/calendarserver-dev/attachments/20090219/ab73d4a4/attachment.html>

More information about the calendarserver-dev mailing list