running with --san --test works fine, i get certificates created but fails when remove --test

[JD-aus]

Firstly great app, it has taken me some time to learn the basics of LE and this app for use with exchange 2013, but now I understand it, the app appears to work fine in testing until I remove the --test .... then it does nothing.

App version: 1.9.1.10
OS: Win 2012R2
Exchange: 2013 latest RU
IIS version: 8.5

running
C:\programs\letsencrypt\letsencrypt.exe --test --san --centralsslstore C:\Central_SSL
creates multiple SAN certificates in the C:\Central_SSL\ directory (one *.pfx for each hostname in the SAN) and different version of the SAN certificate in the C:\Users<user>\AppData\Roaming\letsencrypt-win-simple\httpsacme-staging.api.letsencrypt.org\ (but funily no *.pfx certificate)

running
C:\programs\letsencrypt\letsencrypt.exe --san --centralsslstore C:\Central_SSL
I get the following response from every hostname listed in CSV format

---

The ACME server was probably unable to reach http://<sub>.<domain>.com.au/.well-known/acme-challenge/hIRtOVde_yDjrMqrhiFMeJDGWl-IUD5K7ZtW8ZyaC08

Check in a browser to see if the answer file is being served correctly.

---

When running in --test I can see the data flowing through my external firewall (in have logging enabled for testing this problem), but when running without test, the outbound servers don't event show as trying to connect ... not sure if its a problem with LE, or your app, but appears to be somewhere between them.

thanks for producing a great free & open source app. I contributed more information to the Exchange 2016 wiki page to hopefully assist others in locating the information quickly.

[WouterTinus]

From what I've gathered --test mode does less extensive validation than regular mode. The latest releases of LEWS give better feedback about why validation fails. You can try and open a new issue if you still run into problems.