Acme.sh appears no longer to receive any support

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), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: mountolive.com

I ran this command: acme.sh --renew -d server.mountolive.com --force

It produced this output: Error, can not get domain token "type":"dns-01","url":"https://acme.zerossl.com/v2/DV90/chall/LT04Iv1AJ6_UClgChSf0bA","status":"invalid","error":{

My web server is (include version): Apache/2.4.52 (Ubuntu)

The operating system my web server runs on is (include version): Linux Mint (Linux Mint 21.1 Vera \n \l)

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): No

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): acme.sh v3.0.8

I have been using acme.sh to manage my LetsEncrypt certificate on a local server. Recently, certificate renewal stopped working. I attempted to get some help on the acme.sh issues forum, but it appears no one is paying attention to its posts. Does anyone happen to know if acme.sh is still supported? If not, then what is the easiest way to migrate from acme.sh to Certbot? Note that our DNS server is IONOS and originally I had to use acme.sh to test a txt field associated with our domain mountolive.com so it knew the request for a certificate (a wildcard cert *.mountolive.com) was legitimate.

I can't speak to acme.sh level of support. There are 'issues' posted to their github regularly and closed.

But, you are requesting a cert from ZeroSSL, not Let's Encrypt

You may have lost your default CA setting or need to specify --server letsencrypt

In fact, you have not gotten a cert from Let's Encrypt since Mar2023

6 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.