caddy-dns/duckdns

not working any more after new duckdns updates

Closed this issue · 2 comments

Error Msg:

solving challenges: waiting for solver certmagic.solverWrapper to be ready: 
checking DNS propagation of \"_acme-challenge.XXX.duckdns.org\": 
read tcp 127.0.0.1:55654->127.0.0.53:53: i/o timeout 
(order=https://acme.zerossl.com/v2/DV90/order/xxxxxxxxxxxxxx) 
(ca=https://acme.zerossl.com/v2/DV90)","attempt":1,"retrying_in":60,"elapsed":73.063274363,"max_duration":2592000}

seems to be the issue of network connection with AWS

PING appservers-duckdns-prod-1630339571.ca-central-1.elb.amazonaws.com (3.96.242.55) 56(84) bytes of data.
^C
--- appservers-duckdns-prod-1630339571.ca-central-1.elb.amazonaws.com ping statistics ---
8 packets transmitted, 0 received, 100% packet loss, time 7180ms

Did you find any solution to this as I am experiencing the same problem