A common problem. :(
I finally got around to improve acme-client's error reporting, it should be
better in -current and 6.8
On 23 May 2020 21:28:23 CEST, Teno Deuter wrote:
>On Sat, May 23, 2020 at 8:22 PM Stuart Henderson
>wrote:
>>
>> On 2020-05-23, Teno Deuter wrote:
>> > acme-client: challenge, token: , status: 2
>> > acme-client: dochngreq:
>> > https://acme-v02.api.letsencrypt.org/acme/authz-v3/4766326725
>> > acme-client: challenge, token: ... , status: 0
>> > acme-client: /var/www/acme/...: created
>> > acme-client:
>https://acme-v02.api.letsencrypt.org/acme/chall-v3/4766326725/TzAk5w:
>> > challenge
>> > acme-client: order.status -1
>> > acme-client: bad exit: netproc(62115): 1
>> >
>> > Thank you for your kind help
>> >
>> >
>>
>> https://acme-v02.api.letsencrypt.org/acme/authz-v3/4766326725 shows
>an
>> error from letsencrypt:
>>
>> "DNS problem: NXDOMAIN looking up A for www.jpcode.org - check that a
>> DNS record exists for this domain"
>>
>
>Thank you for your swift response. I didn't know how to debug the
>acme-client output.
>
>Correct. I forgot to update the DNS records. Now everything works well.
--
Sent from a mobile device. Please excuse poor formating.
