remote.hobel.at has an A (IPv4) record (80.64.140.82) 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://remote.hobel.at/.well-known/acme-challenge/letsdebug-test: dial tcp 80.64.140.82:80: connect: connection refused
Trace:
@0ms: Making a request to http://remote.hobel.at/.well-known/acme-challenge/letsdebug-test (using initial IP 80.64.140.82)
@0ms: Dialing 80.64.140.82
@101ms: Experienced error: dial tcp 80.64.140.82:80: connect: connection refused
A test authorization for remote.hobel.at to the Let's Encrypt staging service has revealed issues that may prevent any certificate for this domain being issued.
Fetching http://remote.hobel.at/.well-known/acme-challenge/fNrO-71s3Wjh78fi2ooFapMPQ0hZnfGE2LrdOxMObwU: Connection refused
Requests made to the domain
Request to: remote.hobel.at/80.64.140.82, Result: [Address Type=IPv4,Server=,HTTP Status=0], Issue: ANotWorking
Trace:
@0ms: Making a request to http://remote.hobel.at/.well-known/acme-challenge/letsdebug-test (using initial IP 80.64.140.82)
@0ms: Dialing 80.64.140.82
@101ms: Experienced error: dial tcp 80.64.140.82:80: connect: connection refused
A and AAAA records found for this domain
remote.hobel.at. 0 IN A 80.64.140.82
Challenge update failures for remote.hobel.at in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/30556350
acme: error code 400 "urn:ietf:params:acme:error:connection": Fetching http://remote.hobel.at/.well-known/acme-challenge/fNrO-71s3Wjh78fi2ooFapMPQ0hZnfGE2LrdOxMObwU: Connection refused
The IANA public suffix is the TLD of the Registered Domain
The TLD for remote.hobel.at is: at
The current status.io status for Let's Encrypt
Operational