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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I ran this command: winacme using dns-01 validation (manual)
It produced this output:
[webtest.0hi.me] Authorizing...
[webtest.0hi.me] Authorizing using dns-01 validation (Manual)
Domain: webtest.0hi.me
Record: txtwebtest.api.fran.id
Type: TXT
Content: "gKl_J0i23-palnYt-eN_-1L42frjiHnB3AQMPvt9jfo"
Note: Some DNS managers add quotes automatically. A single set
is needed.
Please press <Enter> after you've created and verified the record
[webtest.0hi.me] Preliminary validation succeeded
[webtest.0hi.me] Preliminary validation succeeded
First chance error calling into ACME server, retrying with new nonce...
[webtest.0hi.me] Authorization result: invalid
[webtest.0hi.me] {
"type": "urn:ietf:params:acme:error:dns",
"detail": "DNS problem: query timed out looking up TXT for _acme-challenge.webtest.0hi.me",
"status": 400
}
Domain: webtest.0hi.me
Record: txtwebtest.api.fran.id
Type: TXT
Content: "gKl_J0i23-palnYt-eN_-1L42frjiHnB3AQMPvt9jfo"
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): winacme v2.1.20.1185 (x64, ReleasePluggable)
Everything was running as usual until yesterday when i couldn't create a new certificate. i don't know what to do. please help me. thank you
There's no other way; your DNS needs to be accessible for Let's Encrypt to be able to issue you a certificate. (It also has to be accessible for your users to be able to access your site, too.)
When any of those are asked for the NS entries they say: 0hi.me canonical name = 0hi.me.cdn.cloudflare.net
[Because: 0hi.me does an apex CNAME to 0hi.me.cdn.cloudflare.net]
[complete delegation - from this point forward there is no further requests on 0hi.me]
So, we continue our search for your NS records.
But... 0hi.me.cdn.cloudflare.net doesn't list any NS entries. me.cdn.cloudflare.net doesn't list any NS entries. cdn.cloudflare.net doesn't list any NS entries. cloudflare.net lists NS:
None of which know anything about any NS entries for 0hi.me.cdn.cloudflare.net
Sure, they do know about the NS for 0hi.me, but the CNAME killed that request.
Everyone is now looking for 0hi.me.cdn.cloudflare.net and no one knows where that is.
thanks for the replies from all of you.
i know the exact configuration of my DNS, starting from the advantages and disadvantages. you guys seem to think SSL/TLS issuance never works. it works, but since yesterday i can't anymore. i just wanted to know if there is something was happening on your side, but never mind.
I don't know, nor think anything about, such issuance(s).
What I do know is that if one follows from the root DNS zone ("."), the answer to "What is the TXT record for _acme-challenge.0hi.me?" can't be answered.
[webtest.0hi.me] Authorizing...
[webtest.0hi.me] Authorizing using dns-01 validation (Manual)
Domain: webtest.0hi.me
Record: txtwebtest.api.fran.id
Type: TXT
Content: "T6GZ_u1xZZdlb92aHC1FVsix9aqHOuCdLKqjPSzJEWE"
Note: Some DNS managers add quotes automatically. A single set
is needed.
Please press <Enter> after you've created and verified the record
[webtest.0hi.me] Preliminary validation succeeded
[webtest.0hi.me] Preliminary validation succeeded
First chance error calling into ACME server, retrying with new nonce...
[webtest.0hi.me] Authorization result: valid
Domain: webtest.0hi.me
Record: txtwebtest.api.fran.id
Type: TXT
Content: "T6GZ_u1xZZdlb92aHC1FVsix9aqHOuCdLKqjPSzJEWE"
this is all my fault. sorry for the inconvenience.
i have removed all bot flows and procedures for Let's Encrypt due to a short-term decision... but it is ok. i can still make it from square one.
thank you everyone
