You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide some information about your script:
Windows IIS
1.5.2
low / med
I am expecting that the challenge file ( http://<YOUR_DOMAIN>/.well-known/acme-challenge/ ) is to be created by the scripts. I do not see the file get created, so manually created on my own. I am able to browse to the file from outside my network, but because I manually built it, I assume it does not contain the right data.
e.g.: http://webtest.atlasorthoticlab.com/.well-known/acme-challenge/ZYt9woXBfjV5GbKV7d4NANe5Th-uQNn-YV8cucUdmMU
ACME-PS itself will not do anything without you making it do.
It's meant to build your script around it and do the protocol stuff for you - so the file won't be created automatically, but file name and content are provided to you.
The response indicates, there's been a 404 on your side. So Let's Encrypt did not get the file (at the time it tried)
Thanks Thomas!
Very much appreciate the quick follow up. It sounds like I took the right
steps (manually) to build the file. The name of the file is the value of
the token and the only data in the file is the value of "Content"
Any advice on why Let's Encrypt is returning a 404 when the file is
available at the URL?
current example:
webtest.atlasorthoticlab.com/.well-known/acme-challenge/kHYlM2FZLt9qIjMWbUcyCNQs8x1hUWyj_gxLdhWCSJ8
Thanks again and great work
On Fri, Sep 9, 2022 at 1:21 PM Thomas Ottenhus ***@***.***> wrote:
ACME-PS itself will not do anything without you making it do.
It's meant to build your script around it and do the protocol stuff for
you - so the file won't be created automatically, but file name and content
are provided to you.
The response indicates, there's been a 404 on your side. So Let's Encrypt
did not get the file (at the time it tried)
—
Reply to this email directly, view it on GitHub
<#132 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWFPKJCQDGV5ON7BBM5GOJTV5NWYZANCNFSM6AAAAAAQIZVNNM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
I've seen this with web farms that are not synchronized fast enough.
I don't know your script, but it might also be you are signaling the readiness of the challenge before saving the file?
It should be:
Create order, read challenge data, create file, signal challenge to be checked, update order until status change, finalize order, get cert.
Please provide some information about your script:
I am expecting that the challenge file ( http://<YOUR_DOMAIN>/.well-known/acme-challenge/ ) is to be created by the scripts. I do not see the file get created, so manually created on my own. I am able to browse to the file from outside my network, but because I manually built it, I assume it does not contain the right data.
e.g.: http://webtest.atlasorthoticlab.com/.well-known/acme-challenge/ZYt9woXBfjV5GbKV7d4NANe5Th-uQNn-YV8cucUdmMU
The challenge fails with this message:
Any advice on how to ensure the token file gets created correctly is appreciated
Eric
The text was updated successfully, but these errors were encountered: