SSL unauthorized 404

[Eliseo-myneflow]

I have my domain hosted on Hostinger, and I've already set up my DigitalOcean droplet URL in Hostinger to display the webpage. However, when I try to add the SSL certificate to myneflow.com , I encounter this error:
On the other hand, I was able to configure the domain solutions.myneflow.com without any issues.

My domain is:
myneflow.com
I ran this command:

sudo certbot --nginx -d myneflow.com -d solutions.example.com

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for myneflow.com

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
  Domain: myneflow.com
  Type:   unauthorized
  Detail: 2a02:4780:b:846:0:149b:eba1:4: Invalid response from http://myneflow.com/.well-known/acme-challenge/xrz-y3iCjhXznwoMlXEbk6wRCsBZJdz2GKUE0D3g6dU: 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.

My web server is (include version):

nginx/1.24.0 (Ubuntu)

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

Ubuntu 24.04 (LTS) x64

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 2.11.0

[MikeMcQ]

Welcome @Eliseo-myneflow

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

But, the IPv6 address points to a Hostinger LiteSpeed server not your nginx 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. You would also need to ensure your nginx listen statements supported 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

[rg305]

It looks better now:

Name:    myneflow.com
Address: 134.209.77.221

Name:    solutions.myneflow.com
Address: 134.209.77.221

Were you able to get the cert?

[Eliseo-myneflow]

Yes, i deleted the only AAAA record on my hostinger domain and run the command again, thank you very much i was stuck on this for 3 whole days, really appreciate the help.