Let's Debug

Test result for ingber.com using http-01

ingber.com has an AAAA (IPv6) record (2600:3c01::f03c:91ff:fe93:e6f3) but a test request to this address over port 80 did not succeed. Your web server must have at least one working IPv4 or IPv6 address. You should either ensure that validation requests to this domain succeed over IPv6, or remove its AAAA record.
A timeout was experienced while communicating with ingber.com/2600:3c01::f03c:91ff:fe93:e6f3: Get "http://ingber.com/.well-known/acme-challenge/letsdebug-test": dial tcp [2600:3c01::f03c:91ff:fe93:e6f3]:80: i/o timeout

Trace:
@0ms: Making a request to http://ingber.com/.well-known/acme-challenge/letsdebug-test (using initial IP 2600:3c01::f03c:91ff:fe93:e6f3)
@0ms: Dialing 2600:3c01::f03c:91ff:fe93:e6f3
@10000ms: Experienced error: dial tcp [2600:3c01::f03c:91ff:fe93:e6f3]:80: i/o timeout
Error
ingber.com has an A (IPv4) record (173.255.212.226) 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 ingber.com/173.255.212.226: Get "https://www.ingber.com/.well-known/acme-challenge/letsdebug-test": context deadline exceeded

Trace:
@0ms: Making a request to http://ingber.com/.well-known/acme-challenge/letsdebug-test (using initial IP 173.255.212.226)
@0ms: Dialing 173.255.212.226
@130ms: Server response: HTTP 302 Found
@130ms: Received redirect to https://ingber.com/.well-known/acme-challenge/letsdebug-test
@130ms: Dialing 173.255.212.226
@328ms: Server response: HTTP 302 Found
@329ms: Received redirect to https://www.ingber.com/.well-known/acme-challenge/letsdebug-test
@648ms: Dialing 2600:3c01::f03c:91ff:fe93:e6f3
@10000ms: Experienced error: context deadline exceeded
A test authorization for ingber.com to the Let's Encrypt staging service has revealed issues that may prevent any certificate for this domain being issued.
Fetching https://ingber.com/.well-known/acme-challenge/mVNrv1_9Wk87_l560BeQvZE5lgevWKSXuXRJyvmDCFE: Timeout during connect (likely firewall problem)

Submitted Dec 2 20:05:36 2020. Sat in queue for 2ms. Completed in 22s. Show verbose information.