Let's Debug

Test result for nasdoury.ovh using http-01

Error
nasdoury.ovh has an A (IPv4) record (51.254.130.252) 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 nasdoury.ovh/51.254.130.252: Get http://nasdoury.ovh/.well-known/acme-challenge/letsdebug-test: context deadline exceeded

Trace:
@0ms: Making a request to http://nasdoury.ovh/.well-known/acme-challenge/letsdebug-test (using initial IP 51.254.130.252)
@0ms: Dialing 51.254.130.252
@10000ms: Experienced error: context deadline exceeded
A test authorization for nasdoury.ovh to the Let's Encrypt staging service has revealed issues that may prevent any certificate for this domain being issued.
Fetching http://nasdoury.ovh/.well-known/acme-challenge/qsOEkzug6b4GnkJ8aMpkgq9QP-wUVP6rUFQRC1-8Su0: Timeout during connect (likely firewall problem)
Debug
Requests made to the domain
Request to: nasdoury.ovh/51.254.130.252, Result: [Address=51.254.130.252,Address Type=IPv4,Server=,HTTP Status=0], Issue: ANotWorking
Trace:
@0ms: Making a request to http://nasdoury.ovh/.well-known/acme-challenge/letsdebug-test (using initial IP 51.254.130.252)
@0ms: Dialing 51.254.130.252
@10000ms: Experienced error: context deadline exceeded

Debug
A and AAAA records found for this domain
nasdoury.ovh. 0 IN A 51.254.130.252
An internal error occurred while checking the domain
Failed to query certwatch database to check rate limits: pq: bind message supplies 2 parameters, but prepared statement "" requires 1
Challenge update failures for nasdoury.ovh in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/74040050
acme: error code 400 "urn:ietf:params:acme:error:connection": Fetching http://nasdoury.ovh/.well-known/acme-challenge/qsOEkzug6b4GnkJ8aMpkgq9QP-wUVP6rUFQRC1-8Su0: Timeout during connect (likely firewall problem)
Debug
The IANA public suffix is the TLD of the Registered Domain
The TLD for nasdoury.ovh is: ovh
Debug
The current status.io status for Let's Encrypt
Operational

Submitted Feb 5 09:45:48 2020. Sat in queue for 1ms. Completed in 14s. Hide verbose information.