AFP548 Changing the world one server at a time.

Renewing Thawte Cert in 10.4.7 Server

Home › Forums › OS X Server and Client Discussion › Questions and Answers › Renewing Thawte Cert in 10.4.7 Server

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #366905
    jeepish
    Participant

    Background: Our server was running 10.3.x before, and had a valid Thawte certificate. Upgraded to 10.4.x (now at 10.4.7), and is serving fine.

    I paid for a renewal, and Thawte sent me the new certificate. However, in Server Admin, I cannot modify an existing valid certificate. Long and short of it, I’ve tried everything to get the new certificate recognized, but either it doesn’t work at all, or it runs fine, but still thinks the old certificate is the only one available, and I can’t figure out how to get it to see that it’s been renewed.

    Here’s where I am now (see this thread for more details):

    I’m now in the situation where Server Admin thinks my prior Thawte-signed cert is self-signed, but when I click on “Add Signed Certificate” paste in my new cert, hit save, I get “Error while writing settings (-1)”.
    This is what I see in server.log:
    servermgrd: servermgr_info: [45] [CertificateManager addSignedCertificate:]: SecCertificateAddToKeychain (err = -25299)
    When I visit my site, however (LUCKY for me), Safari and Firefox report a perfectly valid and signed certificate being served.

    I’ve read many various docs and articles, but none seem to cover this particular situation. I’ve blown away all certificates (including those in the system Keychain) and tried to re-enter just the renewed one, but Server Admin still refuses to see that it’s signed.

    Any tips?

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.