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. https://crt.sh/?q=example.com ), so withholding your domain name here does not increase secr…

Hello @TurnTheLydon , You must specify a dns plugin to be used by acme.sh, it seems you are using namecheap as your dns provider so please, read carefully the doc to use it with acme.sh, because you need to use a username, an api key and a source ip. [image] acmesh-official/acme.sh - 53. …

This should let you do dns authentication manually without a plugin: acme.sh --issue --dns -d turnthelydon.com -d "*.turnthelydon.com" [image] acmesh-official/acme.sh - 9. Use DNS manual mode: A pure Unix shell script implementing ACME client protocol

The recently issued certs are confusing. crt.sh | %.turnthelydon.com [image] top-down apex only wildcard only [must have used DNS auth] apex and www [repeat of 7] same as 3 www only apex only [same as 1] apex and www [not from LE]

Yeah, I know. I'm sorry, I was just beating my head against the wall trying different combinations prior.

There is a complete staging environment for such cases [testing] Nevertheless, you managed to get #2 with DNS auth, so you must have some idea on how that was done. You simply need to do one cert with two names on it (2 DNS changes at the same time).

[image] griffin: This should let you do dns authentication manually without a plugin: acme.sh --issue --dns -d turnthelydon.com -d "*.turnthelydon.com" If it is possible I would avoid a manual authentication, he must use one more parameter --yes-I-know-dns-manual-mode-enough-go-ahead-please …

I think that parameter is obsolete. But yes, automated is better. :wink:

Let's start with what you DO have: /root/.acme.sh/acme.sh --list

[image] griffin: That parameter is obsolete. It isn't :wink: # acme.sh --version https://github.com/acmesh-official/acme.sh v2.8.8 # acme.sh --issue --dns -d turnthelydon.com -d "*.turnthelydon.com" [lun 04 ene 2021 03:00:49 CET] It seems that you are using dns manual mode. Read this link f…

I was fairly certain that the developer of acme.sh himself recently stated that --yes-I-know-dns-manual-mode-enough-go-ahead-please was obsolete somewhere in this community. I may be wrong. I can't seem to find the reference. :thinking:

The current cert (expires in 23 days) is only for apex and www. Do you really need a wilcard cert? [if not, this is quite simple and you've already issued such certs - #3,4]

Creating Wildcard Cert that includes base domain

Help

rg305 January 4, 2021, 2:19am 28

Hanging participle?
Hanging chad?
Hanging on your next syllable?

Topic		Replies	Views
Acme.sh supports ACME v2 wildcard now Client dev	60	41450	May 9, 2018
The supported validation types are: http-01 , but you specified: dns-01 Help	5	4535	February 26, 2020
Wildcard certificate Help	19	423	February 4, 2025
How to issue ACMEv2 Wildcard with Certbot 0.22.0? Help	47	42518	May 27, 2018
ACME V2: does wildcard SSL cover the base domain too? Client dev	17	6459	May 2, 2018

Creating Wildcard Cert that includes base domain

Related topics