Cloudflare DNS has longer delay

Author: robalexdev

examples/acme.sh/register-and-issue.sh

@@ -17,14 +17,14 @@ export ACMEDNS_USERNAME=$(jq -r .username creds.json)
 export ACMEDNS_PASSWORD=$(jq -r .password creds.json)
 
 # First staging environment
-~/.acme.sh/acme.sh --issue --dnssleep 1 --dns dns_acmedns --force -d ${ACMEDNS_FULLDOMAIN} --staging
+~/.acme.sh/acme.sh --issue --dns dns_acmedns --force -d ${ACMEDNS_FULLDOMAIN} --staging
 
 # Cleanup
 ~/.acme.sh/acme.sh --remove -d ${ACMEDNS_FULLDOMAIN} --staging
 
 if [[ $1 == "prod" ]]; then
   # Try prod if staging worked (force Let's Encrypt)
   # Only do this on a cron schedule, so we don't consume too much of the rate limit
-  ~/.acme.sh/acme.sh --issue --dnssleep 1 --dns dns_acmedns --force -d ${ACMEDNS_FULLDOMAIN} --server letsencrypt
+  ~/.acme.sh/acme.sh --issue --dns dns_acmedns --force -d ${ACMEDNS_FULLDOMAIN} --server letsencrypt
 fi
 

examples/caddy/test.sh

@@ -36,6 +36,8 @@ do
     fi
   else
     echo "Got a curl error"
+    cat output
+    echo ""
   fi
 done
 

examples/traefik/traefik.yml

@@ -8,7 +8,6 @@ certificatesResolvers:
       storage: /letsencrypt/acme.json
       dnsChallenge:
         provider: acme-dns
-        delayBeforeCheck: 0
 providers:
   docker:
     exposedByDefault: false