Nginx Acme Challenge fails

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: domain.org
Type: unauthorized
Detail: 143.42.19.11: Invalid response from http://domain.org/.well-known/acme-challenge/We77GxDc7EkwYxff0fddghUUDvmDUsf_eAJ4SIYm0_A: 404

Domain: www.domain.org
Type: unauthorized
Detail: ip.addr.ess: Invalid response from http://www.ovpdashboard.org/.well-known/acme-challenge/cZHZHxRonWZ2isMMC0UsX5yPvKnOjlmhrXePI0c27Os: 404

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

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:

I ran this command:

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:

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

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

6 Likes

Hi @rolandeke,

Your supplied webroot path is probably not correct. As Certbot said, you may need to

Also as @Nummer378 said, it would be helpful if you could fill out the whole form.

5 Likes

Also please note that you have an IPv6 address that is not working at all. This will likely cause additional problems in the future (though it's not a part of the explanation for the errors that you've gotten so far). Can you check what your server's IPv6 address should be, and update the AAAA record to point to it correctly?

4 Likes

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