Challenges failed

Help
1

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: mm.eventproductions.info running an instance of Mattermost on a VPS

I ran this command: sudo certbot --nginx

It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log

Which names would you like to activate HTTPS for?
We recommend selecting either all domains, or all domains in a VirtualHost/server block.

1: mm.eventproductions.info

Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 1
Requesting a certificate for mm.eventproductions.info

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: mm.eventproductions.info
Type: unauthorized
Detail: 2a02:4780:a:1004:0:220d:f57:10: Invalid response from http://mm.eventproductions.info/.well-known/acme-challenge/YWAi81QnlOat9jcKD6UVh7btwXXpkkRjzxFfiUl8jug: 404

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible 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.

My web server is (include version):
Ubuntu 24.04 with Docker

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

My hosting provider, if applicable, is: Hostinger

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

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

2

You have both an IPv4 A record and an IPv6 AAAA record in your DNS

But, the IPv6 address points to a Hostinger service not your server. In your case it points to a LiteSpeed server which in any case is not your nginx server. Hostinger creates an AAAA record automatically for new setups.

You need to update the AAAA address or remove it if you do not support IPv6.

Any client trying to use IPv6 will connect to that Hostinger (LiteSpeed) service instead of your server. Let's Encrypt favors IPv6 when an AAAA record is present.

See Hostinger article here: How to manage AAAA records | Hostinger Help Center

And use this site to test connections. You will see a warning about multiple IP addresses with mixed responses:
https://letsdebug.net

4 Likes
3

Thanks for the prompt reply will check this out
ta much

1 Like
4

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