Hello @Keneni,
Using the online tool Let's Debug yields these results https://letsdebug.net/menshdigitalbds.com/2318955?debug=y
MultipleIPAddressDiscrepancy
Warning
menshdigitalbds.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:42:8c1d:8c82:ecd7:2425:e0e9,Address Type=IPv6,Server=hcdn,HTTP Status=404] vs [Address=46.202.154.98,Address Type=IPv4,Server=nginx/1.24.0 (Ubuntu),HTTP Status=404]
Which was commented by previous posters.
Using curl showing both IPv4 and IPv6 check one can see distinct differences.
IPv4 check got Server: nginx/1.24.0 (Ubuntu)
>curl -4 -Ii http://menshdigitalbds.com/.well-known/acme-challenge/sometestfile
HTTP/1.1 404 Not Found
Server: nginx/1.24.0 (Ubuntu)
Date: Tue, 24 Dec 2024 20:44:40 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 2448
Connection: keep-alive
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
Referrer-Policy: same-origin
Cross-Origin-Opener-Policy: same-origin
Vary: origin
IPv6 check got Server: hcdn
>curl -6 -Ii http://menshdigitalbds.com/.well-known/acme-challenge/sometestfile
HTTP/1.1 404 Not Found
Date: Tue, 24 Dec 2024 20:44:51 GMT
Content-Type: text/html
Content-Length: 150
Connection: keep-alive
Vary: Accept-Encoding
platform: hostinger
panel: hpanel
content-security-policy: upgrade-insecure-requests
x-turbo-charged-by: LiteSpeed
Server: hcdn
alt-svc: h3=":443"; ma=86400
x-hcdn-request-id: 200a63b5a3e8f8c4e8cc14a925aaf72f-fra-edge1
Either make the IPv6 Address (DNS AAAA Record) point to the same machine as the IPv4 Address or remove the IPv6 Address (at least to start with).
Please see Unable to generate SSL - #2 by MikeMcQ
Supplemental Port 443 is being filtered (i.e. access being blocked) on IPv4.
$ nmap -Pn -p80,443 menshdigitalbds.com
Starting Nmap 7.80 ( https://nmap.org ) at 2024-12-24 20:56 UTC
Nmap scan report for menshdigitalbds.com (46.202.154.98)
Host is up (0.16s latency).
Other addresses for menshdigitalbds.com (not scanned): 2a02:4780:42:8c1d:8c82:ecd7:2425:e0e9
rDNS record for 46.202.154.98: srv656664.hstgr.cloud
PORT STATE SERVICE
80/tcp open http
443/tcp filtered https
Nmap done: 1 IP address (1 host up) scanned in 3.10 seconds
IPv4 curl cannot access HTTPS
>curl -4 -Ii https://menshdigitalbds.com/.well-known/acme-challenge/sometestfile
curl: (28) Failed to connect to menshdigitalbds.com port 443 after 75000 ms: Could not connect to server
IPv6 curl can access HTTPS
>curl -6 -Ii https://menshdigitalbds.com/.well-known/acme-challenge/sometestfile
HTTP/2 404
date: Tue, 24 Dec 2024 21:18:04 GMT
content-type: text/html
content-length: 150
vary: Accept-Encoding
platform: hostinger
panel: hpanel
content-security-policy: upgrade-insecure-requests
server: hcdn
alt-svc: h3=":443"; ma=86400
x-hcdn-request-id: fb92dcda79f0111eb920b61b47331751-fra-edge2
Also from a DNS IP Address view
