# Issue failure after successful \_acme-challenge **URL:** \ **Category:** Help\ **Created:** [May 25, 2022, 4:26pm UTC](https://community.letsencrypt.org/t/issue-failure-after-successful-acme-challenge/178307 "2022-05-25T16:26:51Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![baudmaud](https://avatars.discourse-cdn.com/v4/letter/b/b5a626/32.png) [@baudmaud](https://community.letsencrypt.org/u/baudmaud)\ **Post date:** [May 25, 2022, 4:26pm UTC](https://community.letsencrypt.org/t/issue-failure-after-successful-acme-challenge/178307/1 "2022-05-25T16:26:51Z")
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [crt.sh | example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help. My domain is:\*.dawn2dusk.uk I ran this command: ./acme.sh --server letsencrypt --issue --debug 2 -d '\*.dawn2dusk.uk' --dns dns\_nsupdate --log --force It produced this output: [Wed May 25 15:53:45 UTC 2022] \_on\_issue\_err [Wed May 25 15:53:45 UTC 2022] Please check log file for more details: /root/.acme.sh/acme.sh.log My web server is (include version): not relevant, using dns challenge (successful) The operating system my web server runs on is (include version): NetBSD-9.2 My hosting provider, if applicable, is: N/A I can login to a root shell on my machine (yes or no, or I don't know):yes I'm using a control panel to manage my site (no, or provide the name and version of the control panel): The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): using acme.sh 3.0.4 ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [May 25, 2022, 4:31pm UTC](https://community.letsencrypt.org/t/issue-failure-after-successful-acme-challenge/178307/2 "2022-05-25T16:31:42Z")
> [@baudmaud](#): > > [Wed May 25 15:53:45 UTC 2022] Please check log file for more details: /root/.acme.sh/acme.sh.log Please show the log file. Currently there's nothing to go on unfortunately. Also note that using `--force` _usually_ doesn't help and has the potential to cause more harm than good, such as running into rate limits. On a second note regarding rate limits: when something doesn't go exactly according to plan, it's better to switch over to the staging environment. Or even better: start with the staging environment until everything works and _then_ switch over to the production environment. See [Server · acmesh-official/acme.sh Wiki · GitHub](https://github.com/acmesh-official/acme.sh/wiki/Server) for the parameters which can be used for the acme.sh `--server` option. ---
**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\ **Post date:** [May 25, 2022, 8:03pm UTC](https://community.letsencrypt.org/t/issue-failure-after-successful-acme-challenge/178307/4 "2022-05-25T20:03:56Z")
> [@baudmaud](#): > > --dns dns\_nsupdate The domain has its nameservers hosted with GoDaddy. How are you planning to update them with `nsupdate`? Shouldn't you be using [`acme.sh`'s GoDaddy support](https://github.com/acmesh-official/acme.sh/wiki/dnsapi#4-use-godaddycom-domain-api-to-automatically-issue-cert)? ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [May 25, 2022, 11:05pm UTC](https://community.letsencrypt.org/t/issue-failure-after-successful-acme-challenge/178307/5 "2022-05-25T23:05:08Z")
> [@\_az](#): > > The domain has its nameservers hosted with GoDaddy. I don't see GoDaddy, I get: ```nohighlight dawn2dusk.uk nameserver = viking.prd.co.uk dawn2dusk.uk nameserver = trafalgar.prd.co.uk ``` [maybe this was changed recently...] ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [May 25, 2022, 11:30pm UTC](https://community.letsencrypt.org/t/issue-failure-after-successful-acme-challenge/178307/6 "2022-05-25T23:30:10Z")
> [@rg305](#): > > [maybe this was changed recently...] Definitely changed. I saw GoDaddy dns too ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [May 25, 2022, 11:31pm UTC](https://community.letsencrypt.org/t/issue-failure-after-successful-acme-challenge/178307/7 "2022-05-25T23:31:05Z")
> [@MikeMcQ](#): > > Definitely changed. Then... We are making progress! ---
**Author:** ![baudmaud](https://avatars.discourse-cdn.com/v4/letter/b/b5a626/32.png) [@baudmaud](https://community.letsencrypt.org/u/baudmaud)\ **Post date:** [May 26, 2022, 9:32am UTC](https://community.letsencrypt.org/t/issue-failure-after-successful-acme-challenge/178307/8 "2022-05-26T09:32:35Z")
Looks like it took more than the oft-quoted 48 hours for changes to propagate. I now have the cert. What I don't get is why the log file reported success on the dns-update challenge and then the \_on\_issue\_error with no error code or explanation (it says look in the log file, but there's nothing there). ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [May 26, 2022, 5:23pm UTC](https://community.letsencrypt.org/t/issue-failure-after-successful-acme-challenge/178307/9 "2022-05-26T17:23:07Z")
The dns-update was presumably done to the correct DNS system. While the external DNS challenge requests were being done against the old DNS system. The "look in the log file" message is generic and is always a good place to look - but it can't possibly know everything that might have gone wrong outside of its' view. None-the-less, glad to hear you are secure and automated! Cheers 🍻 ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [June 25, 2022, 5:23pm UTC](https://community.letsencrypt.org/t/issue-failure-after-successful-acme-challenge/178307/10 "2022-06-25T17:23:41Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.