CCS stop working for no visible reason about autoacme HOT 4 CLOSED

Set SNI on, set the hostname field and set IP address to All Unassigned. If you don't set SNI (with a hostname) or set a specific IP address you steal the binding from all other sites because it gets priority.

Really only one cert can be bound on port 443 per IP address, but SNI + All Unassigned IP creates a virtual binding to let the OS decide how to map the cert. So anything you do that disables SNI or creates a more specific IP binding will upset all other bindings served from the same IP address.

from autoacme.

Thank you for your answer Christopher. I am setting the SNI and host name, but thank you for confirming.

I have dug a little deeper and I have noticed that the SSL is not working for existing websites if a website has been deleted on the VPS. This is a development system and the deletion is automatic in our inhouse application. So not through the IIS interface, my thought is that something is breaking the binding between the website binding and the CCS.

I am going to try and remove the binding before deletion using the Autoacme "delhost" option.

Do you have any other ideas?

from autoacme.

OK, the only way I can find to get it working after a website delete is to turn off and on the SNI. For my purpose this is OK.

I will close this task because I don't think it's related to AutoAcme.

from autoacme.

AutoACME does not control the CCS, so you are right to close the issue.

That being said, deleting the HTTPS binding before deleting the site may solve your issue (haven't tried it though).

from autoacme.