# Acme.sh fails with value wasn't set **URL:** \ **Category:** Help\ **Created:** [May 13, 2024, 10:58pm UTC](https://community.letsencrypt.org/t/acme-sh-fails-with-value-wasnt-set/218332 "2024-05-13T22:58:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![gossamer](https://avatars.discourse-cdn.com/v4/letter/g/f07891/32.png) [@gossamer](https://community.letsencrypt.org/u/gossamer)\ **Post date:** [May 13, 2024, 10:58pm UTC](https://community.letsencrypt.org/t/acme-sh-fails-with-value-wasnt-set/218332/1 "2024-05-13T22:58:00Z")
I have a script that I use to renew certs from GoDaddy using their API key method and acme.sh that I've been using for more than a year. Somehow today it stopped working. I checked with my GoDaddy account and nothing has changed there. ```nohighlight ./acme.sh --dnssleep 300 --force --log --issue --use-wget -d wellingtonpotpies.com --dns dns_gd -d www.wellingtonpotpies.com --dns dns_gd -d webstage.wellingtonpotpies.com --dns dn s_gd -d wellingtontransportation.com --dns dns_cloudns -d www.wellingtontransportation.com --dns dns_cloudns -d wellingtontransportation.net --dns dns_cloudns -d www.wellingtontransp ortation.net --dns dns_cloudns --cert-file /etc/letsencrypt/wellington-certfile.pem --key-file /etc/letsencrypt/wellington-privkey.pem [Mon May 13 06:52:23 PM EDT 2024] Using CA: https://acme.zerossl.com/v2/DV90 [Mon May 13 06:52:24 PM EDT 2024] Multi domain='DNS:wellingtonpotpies.com,DNS:www.wellingtonpotpies.com,DNS:webstage.wellingtonpotpies.com,DNS:wellingtontransportation.com,DNS:www.we llingtontransportation.com,DNS:wellingtontransportation.net,DNS:www.wellingtontransportation.net' [Mon May 13 06:52:31 PM EDT 2024] Getting webroot for domain='wellingtonpotpies.com' [Mon May 13 06:52:31 PM EDT 2024] Getting webroot for domain='www.wellingtonpotpies.com' [Mon May 13 06:52:31 PM EDT 2024] Getting webroot for domain='webstage.wellingtonpotpies.com' [Mon May 13 06:52:31 PM EDT 2024] Getting webroot for domain='wellingtontransportation.com' [Mon May 13 06:52:31 PM EDT 2024] Getting webroot for domain='www.wellingtontransportation.com' [Mon May 13 06:52:31 PM EDT 2024] Getting webroot for domain='wellingtontransportation.net' [Mon May 13 06:52:31 PM EDT 2024] Getting webroot for domain='www.wellingtontransportation.net' [Mon May 13 06:52:31 PM EDT 2024] Adding txt value: g0tmChMlhwjrujzrEj-6qKTe5Wlo0vXexDQ9tufZJ5I for domain: _acme-challenge.wellingtonpotpies.com [Mon May 13 06:52:32 PM EDT 2024] Adding record [Mon May 13 06:52:33 PM EDT 2024] TXT record 'g0tmChMlhwjrujzrEj-6qKTe5Wlo0vXexDQ9tufZJ5I' for '_acme-challenge.wellingtonpotpies.com', value wasn't set! [Mon May 13 06:52:33 PM EDT 2024] Error add txt for domain:_acme-challenge.wellingtonpotpies.com [Mon May 13 06:52:33 PM EDT 2024] Please check log file for more details: /root/.acme.sh/acme.sh.log ``` I've also upgraded to version 3.0.8 and still having the same problem. I've even tried creating a new API key. This script also renews certs for a bunch of domains managed by cloudflare and they are having no difficulties using the same version of acme.sh. Where do I start troubleshooting this? ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [May 13, 2024, 11:04pm UTC](https://community.letsencrypt.org/t/acme-sh-fails-with-value-wasnt-set/218332/2 "2024-05-13T23:04:43Z")
Hi @gossamer, > [@gossamer](#): > > `Using CA: https://acme.zerossl.com/v2/DV90` Well it looks like you are not using Let's Encrypt CA. For Let's Encrypt I would suggest using the [Staging Environment - Let's Encrypt](https://letsencrypt.org/docs/staging-environment/) to while debugging. Edit: Also there seems to be new issue(s) with GoDaddy. - [How Replace GoDaddy API for DNS Challenge](https://community.letsencrypt.org/t/how-replace-godaddy-api-for-dns-challenge/218249) - [Getting unauthorized URL error while trying to get cert for subdomains](https://community.letsencrypt.org/t/getting-unauthorized-url-error-while-trying-to-get-cert-for-subdomains/217329) - [DNS Challenge with GoDaddy API Failed](https://community.letsencrypt.org/t/dns-challenge-with-godaddy-api-failed/215938) Edit: Another option would be to consider using [HTTP-01 challenge](https://letsencrypt.org/docs/challenge-types/#http-01-challenge) instead of the [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) you are presently using of the [Challenge Types - Let's Encrypt](https://letsencrypt.org/docs/challenge-types/). ---
**Author:** ![gossamer](https://avatars.discourse-cdn.com/v4/letter/g/f07891/32.png) [@gossamer](https://community.letsencrypt.org/u/gossamer)\ **Post date:** [May 14, 2024, 12:49am UTC](https://community.letsencrypt.org/t/acme-sh-fails-with-value-wasnt-set/218332/3 "2024-05-14T00:49:46Z")
The issue turned out to be a new restriction GoDaddy is applying to their budget-friendly customers (those with less than 10 domains) and the use of their API to update DNS records. > [@Getting unauthorized URL error while trying to get cert for subdomains](https://community.letsencrypt.org/t/getting-unauthorized-url-error-while-trying-to-get-cert-for-subdomains/217329): > > I… Working on migrating off them now. ---
**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 14, 2024, 1:32am UTC](https://community.letsencrypt.org/t/acme-sh-fails-with-value-wasnt-set/218332/4 "2024-05-14T01:32:34Z")
> [@gossamer](#): > > `--force` For future reference: Using `force` doesn't fix anything that is broken. Also, you might want to split that cert into multiple certs. [with just the names found in each individual vhost] ---
**Author:** ![gossamer](https://avatars.discourse-cdn.com/v4/letter/g/f07891/32.png) [@gossamer](https://community.letsencrypt.org/u/gossamer)\ **Post date:** [May 14, 2024, 7:27pm UTC](https://community.letsencrypt.org/t/acme-sh-fails-with-value-wasnt-set/218332/5 "2024-05-14T19:27:18Z")
> [@rg305](#): > > For future reference: Using `force` doesn't fix anything that is broken. Yes, understood. That was a remnant from a previous successful run. > [@rg305](#): > > Also, you might want to split that cert into multiple certs. > [with just the names found in each individual vhost] For easier management, security, or both? I also managed to switch the default CA: `/acme.sh --set-default-ca --server letsencrypt` And get it working with the document root method instead of moving off GoDaddy for now: `./acme.sh ... --webroot /docroot-path/html/` ---
**Author:** ![mirsuhailmohamad](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@mirsuhailmohamad](https://community.letsencrypt.org/u/mirsuhailmohamad)\ **Post date:** [June 13, 2024, 6:32am UTC](https://community.letsencrypt.org/t/acme-sh-fails-with-value-wasnt-set/218332/6 "2024-06-13T06:32:17Z")
Hi I am facing the same issue when I try to renew ssl certs for go daddy domains using acme.sh. It was working fine before. Could you please provide a solution. Appreciate your help! ---
**Author:** ![webprofusion](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/webprofusion/32/85310_2.png) [@webprofusion](https://community.letsencrypt.org/u/webprofusion)\ **Post date:** [June 13, 2024, 9:40am UTC](https://community.letsencrypt.org/t/acme-sh-fails-with-value-wasnt-set/218332/7 "2024-06-13T09:40:01Z")
> [@mirsuhailmohamad](#): > > Could you please provide a solution @mirsuhailmohamad - the solution is to move away from GoDaddy, they don't provide an API unless you are a big customer. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [July 13, 2024, 9:40am UTC](https://community.letsencrypt.org/t/acme-sh-fails-with-value-wasnt-set/218332/8 "2024-07-13T09:40:21Z")
Closed on July 13, 2024, 9:40am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.