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.
I can login to a root shell on my machine (yes or no, or I don't know):
yes
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):2.1.0
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:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
Please don't remove any of the questions of the questionnaire, even if you think it's not important. That might be the case, but even then, just answer the question please. If you don't know the answer, then that's a valid answer too.
There's a Hostinger "LiteSpeed" server answering on this hostname on IPv6, presenting some Hostinger "Default page". And on IPv4 there's an Ubuntu nginx webserver reporting. So I guess your IPv6 address might be incorrect.
Let's Encrypt prefers IPv6, so requests for the challenge would go to Hostingers LiteSpeed server instead of your nginx. Hostinger also has a certificate issued for your hostname and is using it on their IPv6 address.