cloud.etol.nl has both AAAA (IPv6) and A (IPv4) records. While they both 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 the IPv4 and IPv6 addresses may unintentionally point to different servers, which would cause validation to fail.
[Address Type=IPv4,Server=Apache/2.4.7 (Ubuntu),HTTP Status=404] vs [Address Type=IPv6,Server=openresty,HTTP Status=404]
Requests made to the domain
Request to: cloud.etol.nl/2001:888:0:18::117:80, Result: [Address Type=IPv6,Server=openresty,HTTP Status=404], Issue:
Trace:
@0ms: Making a request to http://cloud.etol.nl/.well-known/acme-challenge/letsdebug-test (using initial IP 2001:888:0:18::117:80)
@0ms: Dialing 2001:888:0:18::117:80
@152ms: Server response: HTTP 404 Not Found
Request to: cloud.etol.nl/176.31.241.57, Result: [Address Type=IPv4,Server=Apache/2.4.7 (Ubuntu),HTTP Status=404], Issue:
Trace:
@0ms: Making a request to http://cloud.etol.nl/.well-known/acme-challenge/letsdebug-test (using initial IP 176.31.241.57)
@0ms: Dialing 176.31.241.57
@179ms: Server response: HTTP 404 Not Found
A and AAAA records found for this domain
cloud.etol.nl. 0 IN A 176.31.241.57
cloud.etol.nl. 0 IN AAAA 2001:888:0:18::117:80
Challenge update failures for cloud.etol.nl in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/6520701
acme: error code 403 "urn:ietf:params:acme:error:unauthorized": Invalid response from http://cloud.etol.nl/.well-known/acme-challenge/r5ecbK2FP83t50hYuembrCRAlg8qQYuqtmV3Bcu1wJE: "<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>"
The IANA public suffix is the TLD of the Registered Domain
The TLD for cloud.etol.nl is: nl
The current status.io status for Let's Encrypt
Operational