Take the 2-minute tour ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

I've been using an internal website at work without any issues until today when I received the error message:

"Safari can't open the page "https://...". The error is: "The server "..." did not accept the certificate." (NSURLErrorDomain:-1205)

I've looked in my Keychain to see if there was a certificate that I could delete and re-add, but nothing shows up there matching the URL of the website. I've fixed this problem once in the past (accidentally) by deleting my entire keychain and starting over but I didn't mean to do it the first time and I'd rather not do it again.

The website does load without an issue in other browsers without any errors/warnings. It's just Safari that's barfing.

Has anyone else seen this? Know how to fix it?

share|improve this question

4 Answers 4

up vote 4 down vote accepted

I've since solved the problem, though I'm not sure if this is the right answer for everyone.

The problem seemed to come from the certificate automatically generated from apple (com.apple.idms.appleid.prd.[large character string]). A quick Google search didn't tell me what this certificate was for, but I'm sure that deleting it was probably not the best solution. Ignoring that thought, I deleted it anyway and now I can log in without a problem. I'm sure that something bad will happen with other things on my computer (private key, other certificates, something), but it hasn't happened yet so I'm calling it a win.

UPDATE:

A couple of months on, I still haven't had anything bad happen so I guess this solution didn't break anything else.

UPDATE 2:

About a year on, this problem still comes up from time to time (even with 10.10). I keep deleting the certificate in the keychain and it keeps working for a while.

share|improve this answer
    
I must say, I've had this same issue after the migration to Mavericks, and deleting the com.apple.idms.appleid.prd.* certificate did solve the problem –  F'x Nov 14 '13 at 10:33

Have a look in

/etc/certificates

for certificates that begin with your certificate name.

Check for any duplicates of the name with different GUID values. If this is the case you will find that the certificate has either been updated or replaced at some point and is still registered to an application.

Check *.plist files for the particular certificate name to find where it is being used. Then you can determine how to fix that particular case.

share|improve this answer

I've seen it before but I don't remember how I resolved it. Perhaps resetting safari would work? Or maybe just deleting some stuff related to the website out of the keychain?

share|improve this answer
    
I have gone into "Reset Safari" and checked "Remove All Website Data" to no effect. I've also looked in the keychain and there aren't any entries related to the website in there. The only entry was a web password, which I deleted even though that really has nothing to do with this problem. –  Wesley Bland Jun 19 '13 at 15:36
    
Interesting. I've dug around a little and found some other people posting about this. It seems it is an actual bug in Safari that has been very persistent since version 3. This is the only "fix" I could find that was somewhat similar, but I think this is for a different problem. Apple Forums –  James Manes Jun 19 '13 at 15:43

Open Keychain Access to examine your Certificates. Sometimes I trash expired ones .. but instead of deleting a Certificate, you can tell the system to trust it. That's the place to do so.

share|improve this answer
    
That wont work for this case as safari is sending a CLIENT certificate to the server and the server is rejecting it. –  Andrew Burns Jan 8 at 19:21

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.