nextcloud22.net has an A (IPv4) record (208.104.38.94) 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.
A timeout was experienced while communicating with nextcloud22.net/208.104.38.94: Get "http://nextcloud22.net/.well-known/acme-challenge/letsdebug-test": dial tcp 208.104.38.94:80: i/o timeout
Trace:
@0ms: Making a request to http://nextcloud22.net/.well-known/acme-challenge/letsdebug-test (using initial IP 208.104.38.94)
@0ms: Dialing 208.104.38.94
@10001ms: Experienced error: dial tcp 208.104.38.94:80: i/o timeout
An internal error occurred while checking the domain
An unknown issue occurred when performing a test authorization against the Let's Encrypt staging service: acme: challenge update timeout
Requests made to the domain
Request to: nextcloud22.net/208.104.38.94, Result: [Address=208.104.38.94,Address Type=IPv4,Server=,HTTP Status=0], Issue: ANotWorking
Trace:
@0ms: Making a request to http://nextcloud22.net/.well-known/acme-challenge/letsdebug-test (using initial IP 208.104.38.94)
@0ms: Dialing 208.104.38.94
@10001ms: Experienced error: dial tcp 208.104.38.94:80: i/o timeout
A and AAAA records found for this domain
nextcloud22.net. 0 IN A 208.104.38.94
Challenge update failures for nextcloud22.net in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/5415605844
acme: challenge update timeout
The IANA public suffix is the TLD of the Registered Domain
The TLD for nextcloud22.net is: net
The current status.io status for Let's Encrypt
Operational