Pulling my hair out here. Yesterday I set up an SSL Certificate in IIS10. This is the process I followed:
- In IIS, under Server Certificates complete Create Certificate Request (generated server.csr & server.key)
- Go to sslforfree.com and start "create certificate" process.
- Enter Static IP in Domain box
- In Validity, choose paste Existing CSR (paste in contents of server.csr)
- Select free 90 day certificate
- Choose HTTP file upload and add auth file to virtual share in IIS.
- Verified OK.
- Download certificate
- Back in IIS, select "Complete Certificate Request"
- Browse to and select "certificate.crt" file.
- Give it a friendly name etc, and save.
- Browse to website under sites in IIS, and select Bindings. Choose the IP of the server, the incoming Port, and the newly imported SSL certificate.
- Back in sslforfree, check the installation.
- Everything all good
So everything was working beautifully, could see the certificate in the browser etc, job done.
Now come to today, and the server is actively refusing requests. Go back to check the installation of my SSL on sslforfree, and it's no longer found. Tried removing and re-adding, but nothing I do seems to get the SSL to be visible.
It's not that the certificate is refused, the browser doesn't even think it's there. Why would IIS suddenly stop sharing the certificate? I am totally stumped.
EDIT
As per the advice below, I set up a DNS name with CloudFlare and pointed it at my server.
I Set up the bindings in IIS to link to the new hostname and removed the old certificate (one for port 443 and this one for port 4443 which the API runs on):
Ports 80, 443 and 4443 are all port-forwarded on the router to my server:
I then downloaded Win-ACME and successfully created the Let's Encrypt certificate, and the renewal task created in Task Scheduler.
SSL Cert now shows in Bindings:
SSL Certificate appears to be all good:
...but when I go to the site, using the new domain name. Same problem... no certificate:
So I'm not sure what the problem is here...
CodePudding user response：
This issue may happens when the imported cert does not have a private key associated. solution would be to import the .CER file to your system(from where certificate is requested) personel store and export it with private key. Then copy the .pfx file to required server and import it from server certificate option under IIS.
And you can refer to this link: 
