Unable to pass challenge give a new cert! :/

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:
misterbazar.com www.misterbazar.com

I ran this command:
certbot certonly --test-cert -a webroot --webroot-path=/var/www/misterbazar.com -d misterbazar.com

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for misterbazar.com
Using the webroot path /var/www/misterbazar.com for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. misterbazar.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from https://misterbazar.com/.well-known/acme-challenge/7Q57pNjJw8VUQEQvjiLgRb_uElw0h1rnp-GAjS_lsDY [2001:41d0:2:5c2f::]: "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>nginx</center>\r\n"

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: misterbazar.com
   Type:   unauthorized
   Detail: Invalid response from
   https://misterbazar.com/.well-known/acme-challenge/7Q57pNjJw8VUQEQvjiLgRb_uElw0h1rnp-GAjS_lsDY
   [2001:41d0:2:5c2f::]: "<html>\r\n<head><title>404 Not
   Found</title></head>\r\n<body>\r\n<center><h1>404 Not
   Found</h1></center>\r\n<hr><center>nginx</center>\r\n"

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A/AAAA record(s) for that domain
   contain(s) the right IP address.

My web server is (include version):
nginx/1.14.2

The operating system my web server runs on is (include version):
Debian 10

My hosting provider, if applicable, is:
standalone clean vps

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

Maybe the problem is related to AAAA record and IPV6 ? never happend

help!! thanks

2 Likes

Welcome to the Let's Encrypt Community, Augusto :slightly_smiling_face:

I concur with your conclusion about the IPv6 address possibly causing issues.


I also noticed that both

https://misterbazar.com
https://www.misterbazar.com

have a 301 Moved Permanently redirect to

https://nuovo.misterbazar.com/

Is that desired behavior?

2 Likes

thank you Griffn :slight_smile:

I just fixed the 301 redirect but i get the same result :confused:

I also create a file test.txt inside
/var/www/misterbazar.com/.well-know/acme-challenge

and i see the file pointing from web browser
http://misterbazar.com/.well-know/acme-challenge/test.txt

i'am getting crazy.. thousand of ssl and never happen this

2 Likes

Your domain has an AAAA record set (IPv6) which points to what it looks like a different server.

4 Likes

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