So, our SSL certificate has expired on a site we host on a dedicated server in the middle of the internets. We us IIS 6 on Windows Server 2003. Hardware specs can be grabbed if needed.
On Friday, before the cert expired, we generated a "Renew" CSR, but didn't receive the actual certificate until Saturday. This leaves me attempting to install the certificate this morning, which would have been all fine and dandy, except that when I went to finish processing the pending request, I instead got the screen asking me if I wanted to issue a new request.
I'm not too experienced with SSL setup, but I did some digging around and I can see what I would imagine is the request in the Certificates snap-in on MMC. The request exists in the "Certificate Enrollment Requests" folder of said snap-in.
The response .cer file can be installed fine through the MMC snap-in, except when I attempt to access the site it complains about lacking a private key. The request (under Certificate Enrollment Requests) can be installed just fine too, except that it lacks a signature.
So my primary question is: Is there a means to force a pending request onto an IIS site without issuing a new request? Issuing a new request is looking more and more like the only option...
My secondary question is: Does anyone have any experience with IIS forgetting about pending request? I have to wonder if the pending request maybe vanished in IIS' mind over the weekend, or perhaps was lost due to a freak restart accident (not that we've restarted at all, but maybe something crashed). I'm shooting in the dark here, though; I really don't know what happened to this request.
My tertiary question is: Do you have some chips? I'm hungry and I could really go for some chips right about now...