@KCYeoh wrote:
Hi, I’m trying to restart my DuckDNS today and there is an error at the end of the log and it seems like it is failing to get the new certificate. But I’m still able to access my Hassio with my domain name. In the error log below, i have replaced my domain to xxxxxxx.
Is anyone encountering the same error?
# INFO: Using main config file /data/workdir/config + Account already registered! [18:40:43] INFO: OK 175.140.31.226 NOCHANGE # INFO: Using main config file /data/workdir/config Processing xxxxxxxxxxxxxxxx + Checking domain name(s) of existing cert... unchanged. + Checking expire date of existing cert... + Valid till Apr 28 06:10:31 2020 GMT Certificate will expire (Less than 30 days). Renewing! + Signing domains... + Generating private key... + Generating signing request... + Requesting new certificate order from CA... + Received 1 authorizations URLs from the CA + Handling authorization for xxxxxxxxxxxxxxxxx + Found valid authorization for xxxxxxxxxxxxxxxx + 0 pending challenge(s) + Requesting certificate... ERROR: Problem connecting to server (post for https://acme-v02.api.letsencrypt.org/acme/finalize/xxxxxxx/xxxxxxxx; curl returned with 92)
Posts: 1
Participants: 1