Let's Debug

Test result for opendrg.org using http-01

Debug
Requests made to the domain
Request to: opendrg.org/213.239.208.13, Result: [Address=213.239.208.13,Address Type=IPv4,Server=Apache/2.4.29 (Ubuntu),HTTP Status=301,Number of Redirects=2,Final HTTP Status=200], Issue:
Trace:
@0ms: Making a request to http://opendrg.org/.well-known/acme-challenge/letsdebug-test (using initial IP 213.239.208.13)
@0ms: Dialing 213.239.208.13
@162ms: Server response: HTTP 301 Moved Permanently
@162ms: Received redirect to https://opendrg.org/coinsync/login.well-known/acme-challenge/letsdebug-test
@162ms: Dialing 213.239.208.13
@595ms: Server response: HTTP 302 Found
@595ms: Received redirect to https://opendrg.org/coinsync/login
@595ms: Dialing 213.239.208.13
@1048ms: Server response: HTTP 200 OK

Debug
A and AAAA records found for this domain
opendrg.org. 0 IN A 213.239.208.13
An internal error occurred while checking the domain
Failed to query certwatch database to check rate limits: pq: no more connections allowed (max_client_conn)
Challenge update failures for opendrg.org in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/241531789
acme: error code 403 "urn:ietf:params:acme:error:unauthorized": Invalid response from https://opendrg.org/coinsync/login [213.239.208.13]: "<!DOCTYPE html>\n<html class=\"ng-csp\" data-placeholder-focus=\"false\" lang=\"de-DE\" data-locale=\"de_DE\" >\n\t<head\n data-requesttoken"
Debug
The IANA public suffix is the TLD of the Registered Domain
The TLD for opendrg.org is: org
Debug
The current status.io status for Let's Encrypt
Operational

Submitted Feb 16 10:26:46 2021. Sat in queue for 2ms. Completed in 3s. Hide verbose information.