If no hostnames detected from bindings, allow hostname to be specified manually

[bandleader]

I run my IIS sites without a hostname.
Your program is therefore unable to detect the hostname (understandably). It presents me with various different options, and I must select manual mode.

Instead, a better option would be to show the IIS site, and prompt manually for the hostname.

Thanks for your great program.

[WouterTinus]

I'll look into this when refactoring the IIS plugins for the next release.

[WouterTinus]

I've looked into this, but it's actually pretty difficult to implement, especially when properly matching the certificate to the binding during renewal. In my opinion it would require at least one extra field in the internal representation of a target and a bunch of logic changes in different places.

Perhaps at some point in the future this will become easier as we refactor the code to be more flexible, but right now I'm removing this from the v1.9.5 milestone.

[WouterTinus]

You can do it in v1.9.7 by creating the certificate on another binding (might even be another website) and then link it to the hostless binding. After this initial manual step LEWS will keep the host-less binding updated after renewal.

[bandleader]

@WouterTinus How would that work -- if you choose a different binding, wouldn't LE issue the certificate for that wrong hostname?

[WouterTinus]

You would have to create a binding on port 80 somewhere with the correct hostname configured. It's not the perfect solution yet, but it's at least a way to get auto-renewing certificates set up on hostless bindings :).

[bandleader]

@WouterTinus It has to be on port 80? But then that will conflict with the user's existing binding...

[WouterTinus]

Yes it has to be port 80, but it can be on the same site as the hostless binding so that it doesn't conflict; all traffic would still go to the same site.

[WouterTinus]

It's possible now with v1.9.8 to install a manual hostname to the default IIS site.