A site server has had its name changed and no longer publishes HTTPS codebase
When a site server configured with HTTPS bindings has its name changed, the certificate bound in IIS is no longer valid because it issued in the old name.
This should cause the Site Server to rebind 443 with an updated certificate.
If the Site Server is already using a custom policy, before making this change, first disable the policy, save changes, wait for the site server to get the change, and start with step 5 above.