[root@g nginx]# certbot --nginx
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Which names would you like to activate HTTPS for?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: ratitutisesquema.org
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel):
Requesting a certificate for ratitutisesquema.org
Performing the following challenges:
http-01 challenge for ratitutisesquema.org
Waiting for verification...
Challenge failed for domain ratitutisesquema.org
http-01 challenge for ratitutisesquema.org
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: ratitutisesquema.org
Type: unauthorized
Detail: 2a02:4780:13:903:0:1ae2:584:4: Invalid response from
http://ratitutisesquema.org/.well-known/acme-challenge/W8sGR0MZRdLfU2a6xM_9XuLw4K9C2KhoPHxrIOlcsYc:
404
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
My web server is (include version): nginx 1.20.1
The operating system my web server runs on is (include version): CentOS Linux 7 (Core)
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): 1.11.0
The IPv6 address (2a02:4780:13:903:0:1ae2:584:4) for your website servers a different site than your IPv4 address (181.215.135.62). The IPv4 address seems to be serving some "Next.js" something through nginx, while the IPv6 address seems to be serving some Hostinger page.
$ nmap ratitutisesquema.org
Starting Nmap 7.80 ( https://nmap.org ) at 2022-12-18 23:21 UTC
Nmap scan report for ratitutisesquema.org (181.215.135.62)
Host is up (0.19s latency).
Not shown: 997 filtered ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
443/tcp closed https
Nmap done: 1 IP address (1 host up) scanned in 11.77 seconds
$ curl -I http://ratitutisesquema.org/.well-known/acme-challenge/W8sGR0MZRdLfU2a6xM_9XuLw4K9C2KhoPHxrIOlcsYc
HTTP/1.1 404 Not Found
Server: nginx/1.20.1
Date: Sun, 18 Dec 2022 23:30:59 GMT
Content-Type: text/html
Content-Length: 153
Connection: keep-alive
Yeah, I got some free certs from LetsEncrypt using a Hostinger's tool but for some reason it seems not working:
My domain is having some not expected behaviors. the above printscreen was took on Linux, Firefox, and serves a nextjs page.
But when I go to Windows 10, Chrome, it serves a Hostinger page (this was not supposed to happen) and the ssl cert works.
