Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache 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): Apache (2.4.57)
The operating system my web server runs on is (include version): Ubuntu 23.10
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.10.0
ANotWorking
ERROR
samyscrepes.com has an A (IPv4) record (178.16.129.174) but a request to this address over port 80 did not succeed. Your web server must have at least one working IPv4 or IPv6 address.
A timeout was experienced while communicating with samyscrepes.com/178.16.129.174: Get "http://samyscrepes.com/.well-known/acme-challenge/letsdebug-test": context deadline exceeded
Trace:
@0ms: Making a request to http://samyscrepes.com/.well-known/acme-challenge/letsdebug-test (using initial IP 178.16.129.174)
@0ms: Dialing 178.16.129.174
@10000ms: Experienced error: context deadline exceeded
Using nmap shows Port 80 is filtered (i.e. block), generally this is due to a firewall.
$ nmap -Pn -p80,443 samyscrepes.com
Starting Nmap 7.80 ( https://nmap.org ) at 2024-05-12 14:53 UTC
Nmap scan report for samyscrepes.com (178.16.129.174)
Host is up (0.16s latency).
Other addresses for samyscrepes.com (not scanned): 2a02:4780:22:4bc5:4622:b80a:3af7:3f82
PORT STATE SERVICE
80/tcp filtered http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 3.04 seconds
Beyond that HTTP (not HTTPS) is being served on Port 443
Attempt of HTTP on Port 443 gets a response of "error:0A00010B:SSL routines::wrong version number"
$ curl -k -I https://samyscrepes.com:443/
curl: (35) error:0A00010B:SSL routines::wrong version number
Attempt of HTTP on Port 443 gets a response of "HTTP/1.1 200 OK"
It seems that my didn't listen on port 80. i have fix it.
But i still can't get my certificate same error.
I had a certificate who work on my port 443 but later day i can't renew it so i delate the old who was expired to get a new one and there is the point where i am
MultipleIPAddressDiscrepancy
WARNING
samyscrepes.com has multiple IP addresses in its DNS records. While they appear to be accessible on the network, we have detected that they produce differing results when sent an ACME HTTP validation request. This may indicate that some of the IP addresses may unintentionally point to different servers, which would cause validation to fail.
[Address=2a02:4780:32:ac31:ef68:ffce:e6f6:3a4f,Address Type=IPv6,Server=hcdn,HTTP Status=404] vs [Address=178.16.129.174,Address Type=IPv4,Server=Apache/2.4.57 (Ubuntu),HTTP Status=404]
The domain name has 2 IP Addresses, an IPv4 Address and an IPv6 Address
A and AAAA records found for this domain
samyscrepes.com. 0 IN A 178.16.129.174
samyscrepes.com. 0 IN AAAA 2a02:4780:32:ac31:ef68:ffce:e6f6:3a4f
Is that what you are expecting?
All IP Addresses need to respond the same; Let’s Encrypt prefers IPv6 over IPv4 if both are available.
And https://letsdebug.net/samyscrepes.com/1948284 is once again showing [Address=2a02:4780:23:1b25:e09f:4c7b:5aeb:4ee8,Address Type=IPv6,Server=hcdn,HTTP Status=404] vs [Address=178.16.129.174,Address Type=IPv4,Server=Apache/2.4.57 (Ubuntu),HTTP Status=404]
MultipleIPAddressDiscrepancy
WARNING
samyscrepes.com has multiple IP addresses in its DNS records. While they appear to be accessible on the network, we have detected that they produce differing results when sent an ACME HTTP validation request. This may indicate that some of the IP addresses may unintentionally point to different servers, which would cause validation to fail.
[Address=2a02:4780:23:1b25:e09f:4c7b:5aeb:4ee8,Address Type=IPv6,Server=hcdn,HTTP Status=404] vs [Address=178.16.129.174,Address Type=IPv4,Server=Apache/2.4.57 (Ubuntu),HTTP Status=404]
And just supplemental using nmap of both IPv4 & IPv6; samyscrepes.com resolves to both IPv4 & IPv6 addresses.
IPv4
>nmap -4 -Pn -p80,443 samyscrepes.com
Starting Nmap 7.94 ( https://nmap.org ) at 2024-05-12 15:58 UTC
Nmap scan report for samyscrepes.com (178.16.129.174)
Host is up (0.16s latency).
Other addresses for samyscrepes.com (not scanned): 2a02:4780:1d:941f:df78:a6a7:67c8:81a1
PORT STATE SERVICE
80/tcp open http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 0.19 seconds
IPv6
>nmap -6 -Pn -p80,443 samyscrepes.com
Starting Nmap 7.94 ( https://nmap.org ) at 2024-05-12 15:58 UTC
Nmap scan report for samyscrepes.com (2a02:4780:1d:941f:df78:a6a7:67c8:81a1)
Host is up (0.078s latency).
Other addresses for samyscrepes.com (not scanned): 178.16.129.174
PORT STATE SERVICE
80/tcp open http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 0.66 seconds
Edit: and there is the HTTPS response on Port 443 is different also between IPv4 (failing) and IPv6
IPv4 failing response
>curl -4 -Ii https://samyscrepes.com/.well-known/acme-challenge/sometestfile
curl: (35) OpenSSL/1.1.1t: error:1408F10B:SSL routines:ssl3_get_record:wrong version number
IPv4 is routing directly to an Apache server but that server appears to have at least one major configuration issue (port 443 is listening for HTTP instead of HTTPS)
IPv6 is attempting to route through a Hostinger CDN but not actually functional, this might be related to the port 443 configuration on the server (assuming the CDN is trying to communicate with the server via port 443) but it could be something else
also, having IPv6 routing through a CDN but not IPv4 is really weird
)