acme-challenge validation broken in 2.0.9 version - question "Try in default browser?" is missing

[wlodek76]

I would like to create certificates using unattended batch file and deploy acme-challenge files manually to the server. But it is not possible with 2.0.9 version.
The question [--test] Try in default browser? does not show up.

I do not want to use any automatic validation methods via FTP, SelfHosting or give any FTP access to the software. I would like to write acme-challenge files to the local disk, upload them manually to the server, then continue the validation process (with asking of user) as it was in 1.9.9 version.

I've tried all possible combination with --validation parameters but no success in 2.0.9
It does not work!

What is worst 2.0.9 even deletes created acme-challenge files.

wacs.exe --test --verbose --target manual --host "www.mydomain.com" --emailaddress "me@mydomain.com" --validation filesystem --webroot "c:\win-acme-2.0.9"

It works excellent in 1.9.9 version as in picture below.
letsencrypt.exe --test --verbose --plugin manual --manualhost "www.mydomain.com" --emailaddress "me@mydomain.com" --webroot "c:\win-acme-1.9.9"

[wlodek76]

Please add a possibility to upload acme-challenge files manually without using ftp, webdav in unattended mode.

How it should work.

1. I generate a real certificate.
2. win-acme plugin writes acme-challenge files to the specified folder on a local disk, it stops and waits for a confirmation like a "next" button.
3. I manually upload the files to the server.
4. Then I confirm "next" and win-acme do the rest of job.

Regards.

[WouterTinus]

The Try in default browser? option will be back in the next release in --test mode (which you can also use on the production endpoint when you specify --baseuri https://acme-v02.api.letsencrypt.org/).

Regarding your other idea, I don't really see much need for it once the workaround with --test is back in place, but if it turns out there are more people interested I will consider it.

[wlodek76]

Thank you.