Let's Debug

Test result for host5.johnsimmonshypertext.com using http-01

host5.johnsimmonshypertext.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=2604:180:f4::30d,Address Type=IPv6,Server=nginx/1.18.0 (Ubuntu),HTTP Status=404] vs [Address=168.235.72.134,Address Type=IPv4,Server=nginx/1.18.0 (Ubuntu),HTTP Status=200]
Debug
Requests made to the domain
Request to: host5.johnsimmonshypertext.com/2604:180:f4::30d, Result: [Address=2604:180:f4::30d,Address Type=IPv6,Server=nginx/1.18.0 (Ubuntu),HTTP Status=404], Issue:
Trace:
@0ms: Making a request to http://host5.johnsimmonshypertext.com/.well-known/acme-challenge/letsdebug-test (using initial IP 2604:180:f4::30d)
@0ms: Dialing 2604:180:f4::30d
@122ms: Server response: HTTP 404 Not Found

Request to: host5.johnsimmonshypertext.com/168.235.72.134, Result: [Address=168.235.72.134,Address Type=IPv4,Server=nginx/1.18.0 (Ubuntu),HTTP Status=200], Issue:
Trace:
@0ms: Making a request to http://host5.johnsimmonshypertext.com/.well-known/acme-challenge/letsdebug-test (using initial IP 168.235.72.134)
@0ms: Dialing 168.235.72.134
@189ms: Server response: HTTP 200 OK

Debug
A and AAAA records found for this domain
host5.johnsimmonshypertext.com. 0 IN A 168.235.72.134
host5.johnsimmonshypertext.com. 0 IN AAAA 2604:180:f4::30d
Challenge update failures for host5.johnsimmonshypertext.com in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/7763698844
acme: error code 403 "urn:ietf:params:acme:error:unauthorized": 2604:180:f4::30d: Invalid response from http://host5.johnsimmonshypertext.com/.well-known/acme-challenge/UBCh7G9l8G_6usyHfLCxO4zugOHmv8oAwL9zhr7saMQ: 404
Debug
The IANA public suffix is the TLD of the Registered Domain
The TLD for host5.johnsimmonshypertext.com is: com
Debug
The current status.io status for Let's Encrypt
Operational

Submitted Mar 15 23:49:17 2023. Sat in queue for 3ms. Completed in 6s. Hide verbose information.