问题原文
原帖链接 · Casey Crookston · CC BY-SA 4.0
We have an IIS ARR server which load balances out to two different individual IIS servers.
The servers in question are our internal Staging servers. Three months ago I created a free Let's Encrypt SSL Cert to use on these servers. As is the case with Let's Encrypt, it expired after 3 months. So today I got around to creating a new cert, and I replaced the old certs on the ARR server and both load balanced servers.
After doing that, and then going back to the site in any browser (including incognito mode), it's still showing the old invalid cert. I even went to the site on laptops that have never been to this site before just to see if the old cert was cached in my browser. Even those laptops loaded the site with the Not Secure warning.
These are the steps I've taken:
On the ARR server:
- In IIS, on the server, open "Server Certificates"
- Remove the old cert
- Import the new cert
- Verify the new expiry date is now 3 months out
- IISReset
On the Two Load Balanced Servers:
- In IIS, on the server, open "Server Certificates"
- Remove the old cert
- Import the new cert
- Verify the new expiry date is now 3 months out
- On the site, go into Bindings
- Drill into SSL and verify that the SSL cert is the new one
- IISReset
Yet despite all traces of the old cert being removed, including deleting the actual file, no matter what I do, it loads in every browser (ie, chrome, ff) on every computer showing the old cert still.
I don't know what else to do.
If this helps:
(I should add... there is a LOT of this exact same question on many different forums. I've read dozens of them. None of them have to lead me to a solution.)
社区高分解答
原帖链接 · MikeBeaton · CC BY-SA 4.0
The question actually gave me a clue to the required fixed.
When using netsh http show sslcert it actually showed entries for both 0.0.0.0:443 and {machine-ip}:443.
Hunting around (e.g. in Windows Admin Centre, or various other tools) to see which certificate was which (based on the displayed Certificate Hash), then I saw that the certificate bound to 0.0.0.0:443 was the required new one, and the certificate bound to {machine-ip}:443 was the old one.
So the fix, if netsh http show sslcert displays both certs as above, is:
netsh http delete sslcert ipport={machine-ip}:443
where {machine-ip} should be replaced with the actual IP address in question.
This immediately fixed it, and all sites started using the new certificate.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
