coolab.org has an A (IPv4) record (159.203.86.156) 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.
Get "http://coolab.org/.well-known/acme-challenge/letsdebug-test": dial tcp 159.203.86.156:80: connect: connection refused
Trace:
@0ms: Making a request to http://coolab.org/.well-known/acme-challenge/letsdebug-test (using initial IP 159.203.86.156)
@0ms: Dialing 159.203.86.156
@8015ms: Experienced error: dial tcp 159.203.86.156:80: connect: connection refused
A test authorization for coolab.org to the Let's Encrypt staging service has revealed issues that may prevent any certificate for this domain being issued.
159.203.86.156: Fetching http://coolab.org/.well-known/acme-challenge/p0GezCnOVBpigKpjHJ1mfLMnzHMAfK06t2xIBpWh8b0: Connection refused
Requests made to the domain
Request to: coolab.org/159.203.86.156, Result: [Address=159.203.86.156,Address Type=IPv4,Server=,HTTP Status=0], Issue: ANotWorking
Trace:
@0ms: Making a request to http://coolab.org/.well-known/acme-challenge/letsdebug-test (using initial IP 159.203.86.156)
@0ms: Dialing 159.203.86.156
@8015ms: Experienced error: dial tcp 159.203.86.156:80: connect: connection refused
A and AAAA records found for this domain
coolab.org. 0 IN A 159.203.86.156
Challenge update failures for coolab.org in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/2948420294
acme: error code 400 "urn:ietf:params:acme:error:connection": 159.203.86.156: Fetching http://coolab.org/.well-known/acme-challenge/p0GezCnOVBpigKpjHJ1mfLMnzHMAfK06t2xIBpWh8b0: Connection refused
The IANA public suffix is the TLD of the Registered Domain
The TLD for coolab.org is: org
1 Certificates contributing to rate limits for this domain
Serial: 312076013855616748994638741590250178004652
NotBefore: 2022-06-24 14:57:59 +0000 UTC
Names: [balaio.coolab.org]
The current status.io status for Let's Encrypt
Operational