The key authorization file from the server did not match this challenge

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.

My domain is: Multi domain='DNS:alisiosasesores.com,DNS:www.alisiosasesores.com'

I ran this command:

docker run -d -e VIRTUAL_HOST='alisiosasesores.com, www.alisiosasesores.com' \

-e LETSENCRYPT_HOST='alisiosasesores.com, www.alisiosasesores.com'  \
-e LETSENCRYPT_EMAIL=alejandro.sanchez@XXXXXX.XXX   \
--network=webproxy  \
--name alisios  \
--restart unless-stopped \
-v /data/alisiosasesores.com/html:/usr/local/apache2/htdocs/  \
httpd:alpine

It produced this output:

Creating/renewal alisiosasesores.com certificates... (alisiosasesores.com www.alisiosasesores.com)
[Mon Oct 25 11:59:12 UTC 2021] Using CA: https://acme-v02.api.letsencrypt.org/directory
[Mon Oct 25 11:59:13 UTC 2021] Creating domain key
[Mon Oct 25 11:59:13 UTC 2021] The domain key is here: /etc/acme.sh/XXXXXX@XXXXXX/alisiosasesores.com/alisiosasesores.com.key
[Mon Oct 25 11:59:13 UTC 2021] Multi domain='DNS:alisiosasesores.com,DNS:www.alisiosasesores.com'
[Mon Oct 25 11:59:13 UTC 2021] Getting domain auth token for each domain
[Mon Oct 25 11:59:16 UTC 2021] Getting webroot for domain='alisiosasesores.com'
[Mon Oct 25 11:59:16 UTC 2021] Getting webroot for domain='www.alisiosasesores.com'
[Mon Oct 25 11:59:16 UTC 2021] Verifying: alisiosasesores.com
[Mon Oct 25 11:59:20 UTC 2021] alisiosasesores.com:Verify error:The key authorization file from the server did not match this challenge
[Mon Oct 25 11:59:20 UTC 2021] Please check log file for more details: /dev/null

My web server is (include version): Docker solutions base on NGINX

The operating system my web server runs on is (include version): UBUNTU test on many versions

My hosting provider, if applicable, is: Google, 1and1, IONOS, AWS

I can login to a root shell on my machine (yes or no, or I don't know): yes

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):

GitHub - nginx-proxy/acme-companion: Automated ACME SSL certificate generation for nginx-proxy.

I am starting thinking that the problem maybe come about ipv6 ...
anybody know if LE using IPV6 before IPV4 ?
Thanks

1 Like

Yes, if your DNS has an IPv6 that is preferred by LE (and yours does)

3 Likes

Thanks os much !!! we can close that :slight_smile:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.