Alexandre Aufrere

Please see documentation there: https://github.com/aloopkin/WinCertes/blob/master/Registry.md

@tg123 Thanks a lot for this, it's very helpful! Could you please add an example on how to use this for TLS cert authentication? I guess the whole thing is...

@tg123 thanks, and this is what i did, but i get: "tls: failed to sign handshake: bad private key" (( Here's my further code to the request, that works if...

IIS bindings update should be completely independant from the validation mode (HTTP-01 webroot, HTTP-01 standalone, or DNS-01). Could you please provide the error logs ? BTW, verbose mode is performed...

1. that's correct, but it's the intended behaviour: wincertes is first of all an ACME client, not an IIS cert manager. work-around is very simple: handle the binding manually. 2....

The logic for the IIS bindings is the following, executed after the certificate has been issued from the ACME server: - list all the SubjectAlternativeNames in the certificate, and for...

Hello, Could you please upload the suspicious certificate? Maybe simply copy-paste it as PEM (Base64 encoded) The error is in Linq, meaning i should probably add extra controls, but it's...

Can you provide the error logs please ?

From the logs it seems your IIS website is answering incorrect content to Let's Encrypt. In other words, there's an IIS configuration issue when serving the .well-known/acme-challenge directory. Quickest way...

when WinCertes creates a new binding, it creates it under port 443. however, if the binding already exists, WinCertes uses the existing settings to bind the certificate to it. So...