I am unable to register my certbot for my DNS

[mchow44]

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. https://crt.sh/?q=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: rimanagement.co

I ran this command: sudo certbot --nginx -d rimanagement.co -d www.rimanagement.co

It produced this output:
Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: rimanagement.co
Type: unauthorized
Detail: 2600:1901:0:84ef::: Invalid response from http://rimanagement.co/.well-known/acme-challenge/bkFoeTuymHVWnbj70D63VYZgpSGonQmBe7jvC__gPPM: 404

Domain: www.rimanagement.co
Type: unauthorized
Detail: 2600:1901:0:84ef::: Invalid response from http://www.rimanagement.co/.well-known/acme-challenge/A5Ke_r_dsJxKN4solS5yUQUhBuKSxDrFBCwW3995PYM: 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): Nginx (version 1.20.x)

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

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

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

[linkp]

Welcome to the Let's Encrypt Community.

Your IPv6 address connects to an OpenResty server not nginx. Since IPv6 is preferred over IPv4, you will want to fix that by either updating your AAAA record to use an IP that connects to your nginx server or remove the AAAA record.

See the following test results for more details.

Test result for rimanagement.co: Warning

[MikeMcQ]

@mchow44 The problem is as shown by @linkp

For new setups on Hostinger we often see this problem. I even have my own template to provide further advice. Hope it is helpful

===================

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. Hostinger creates this 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 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
https://letsdebug.net