Repository navigation
Replies: 1 comment
|
Yes, but acme.sh keys everything on the first That gives you three cases:
acme.sh --issue --server "$directory_url" -d '*.example.com' --keylength 2048 \
--cert-home /etc/acme/web --dns --yes-I-know-dns-manual-mode-enough-go-ahead-pleaseUse the same I checked this against 3.1.7: with a saved |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I've haven't been using acme.sh for too long, but I have been successfully issuing certs from our CA with the following:
acme.sh --issue --server ${directory_url} -d ${fqdn} --keylength 2048 --dns --yes-I-know-dns-manual-mode-enough-go-ahead-pleaseThis is happening on a central server and Ansible is used to deploy them to the target hosts.
We use separate wildcard certs in several places so I'm wondering if acme.sh can handle this. From my fairly limited experience so far, if I try to issue a cert with the same CN more than once, I get a message that the domain hasn't changed and that I need to force a renewal.
I haven't tested it w/ wildcard certs yet since I'm waiting for that profile to be enabled in our CA, but I'm assuming the same thing will happen. If that's the case, is there a way to do this?
All reactions