Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Hello,
I am using win-acme ver. 2.1.6.773 (x64, Releasepluggable).
Output win-acme:
Cached order available but not used with the --force switch.
First chance error calling into ACME server, retrying with new nonce...
Authorize identifier www.sd.iteam-samara.ru
Authorizing www.sd.iteam-samara.ru using http-01 validation (FileSystem)
Answer should now be browsable at http://www.sd.iteam-samara.ru/.well-known/acm
e-challenge/DGjbOrFhmv043GHULFRt7QpSLSQqS0Gs4EOirbn9zgk
Preliminary validation failed, the server answered '(null)' instead of 'DGjbOrF
hmv043GHULFRt7QpSLSQqS0Gs4EOirbn9zgk.VRe1zfVp9BNlfKOACzekRYrAItkQbn7-Zy-CMJgrsJQ
'. The ACME server might have a different perspective
{
"type": "urn:ietf:params:acme:error:unauthorized",
"detail": "Invalid response from http://www.sd.iteam-samara.ru/.well-known/acm
e-challenge/DGjbOrFhmv043GHULFRt7QpSLSQqS0Gs4EOirbn9zgk[my ip]: "<html
So what I’m guessing is that your win-acme might have an incorrect configuration or something similar, which didn’t set the right Nginx path when writing files.
What did you input when you request your certificate?
Thank you very much.
I mistake in the right Nginx path (folder .well-known).
Problem is solved. SSL certificate has been issued and installed to Nginx.