I have this Windows Server 2016 where a windows third-party Windows service is listening to a specific port that is in turn associated with a specific SSL certificate. At first, the SSL certificate was issued for the wrong CN (internal IP rather than external) so there was a certificate error when browsing the services URL. When re-registering (remove, then add again) with a correctly generated certificate, however, to my surprise, the error did not go away.
Bewildered, I ended up doing other things for a couple of hours, and upon return I was even more surprised to see that now there were no errors anymore. I don't understand this behavior, and I'm hoping you can shed some light on it. What's going on here, why didn't my changes take effect immediately?
(All manipulation of the ports was done using netsh
, and the certificate chain was always OK. I did restart my browser and the service in question.)