Let's Debug

Test result for divorcesourceapp.com using http-01

divorcesourceapp.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=2407:e700:2:11::cb,Address Type=IPv6,Server=LiteSpeed,HTTP Status=404] vs [Address=18.235.135.157,Address Type=IPv4,Server=Apache,HTTP Status=200]
Debug
Requests made to the domain
Request to: divorcesourceapp.com/2407:e700:2:11::cb, Result: [Address=2407:e700:2:11::cb,Address Type=IPv6,Server=LiteSpeed,HTTP Status=404], Issue:
Trace:
@0ms: Making a request to http://divorcesourceapp.com/.well-known/acme-challenge/letsdebug-test (using initial IP 2407:e700:2:11::cb)
@0ms: Dialing 2407:e700:2:11::cb
@423ms: Server response: HTTP 404 Not Found

Request to: divorcesourceapp.com/18.235.135.157, Result: [Address=18.235.135.157,Address Type=IPv4,Server=Apache,HTTP Status=200], Issue:
Trace:
@0ms: Making a request to http://divorcesourceapp.com/.well-known/acme-challenge/letsdebug-test (using initial IP 18.235.135.157)
@0ms: Dialing 18.235.135.157
@1423ms: Server response: HTTP 200 OK

Debug
A and AAAA records found for this domain
divorcesourceapp.com. 0 IN A 18.235.135.157
divorcesourceapp.com. 0 IN AAAA 2407:e700:2:11::cb
Challenge update failures for divorcesourceapp.com in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/55548842
acme: error code 403 "urn:ietf:params:acme:error:unauthorized": Invalid response from http://divorcesourceapp.com/.well-known/acme-challenge/Wm97tcWH5nNr2L5XDVZrrOJKsfS9bMbm7VOUesUNrsE [2407:e700:2:11::cb]: "<!DOCTYPE html>\n<html style=\"height:100%!\(MISSING)">\n<head>\n<meta name=\"viewport\" content=\"width=device-width, initial-scale=1, shrink-to-"
Debug
The IANA public suffix is the TLD of the Registered Domain
The TLD for divorcesourceapp.com is: com
Debug
The current status.io status for Let's Encrypt
Operational

Submitted Oct 12 01:08:32 2019. Sat in queue for 1ms. Completed in 6s. Hide verbose information.