[mdomenici]

There’s also another bug where even though Server Admin shows your certificate as selected, it really isn’t.

This frequently happens when you are upgrading from a self-signed cert to a signed one from a CA. The common names stay the same.

The best way to fix this is to go in one-by-one to the effected services, switch them to the Default certificate, save, restart the service, and then change back to certificate again, save, and restart the service.

I had this problem when I switched cert vendors and had a self signed cert in between.

– Matt

[mdomenici]

One item I should note…

I never fully deleted the configuration in Server Admin for my old cert, just in Keychain Access. For the heck of it, I went ahead and tried to create a new cert with the same name thinking it would fail (it did) — so it makes me wonder if I need to delete the old cert and then import the new one.

I’m somewhat leery of doing this given the error message, but perhaps that is the problem, do you have any thoughts on this?

– Matt

[Author]

Posts