I need a certificate for some subdomains/sites, like for exemple: www.mydomain.com demo.mydomain.com test.mydomain.com For this I need to request one certificate for each site7subdomain? Or I can request a certificate for the domain, valid for all subdomains? For example: *.mydomain.com Thanks…

Hi @Rui these are your options: one certificate per subdomain -> 7 certificates one certificate with all domain names -> 1 certificate, used with all subdomains one wildcard certificate See [image] FAQ - Let's Encrypt - Free SSL/TLS Certificates Last updated: Apr 23, 2020 | See all D…

As Jürgen says, all three options are available. There is a policy difference from Let's Encrypt's side about issuing the wildcard certificate—if you want a wildcard certificate, you'll have to use the DNS challenge method to prove your control over the domain name. [image] Challenge Types…

Before open this topic, I already get the certificate for www.mydomain.com , using the command: certbot certonly –standalone And now I read some here that: “ both *.example.com and www.example.com would produce an error since the wildcard entry makes the latter redundant. ” How could I request th…

You can request it with --manual, like certbot certonly --manual -d '*.mydomain.com' or if you want to include the apex domain mydomain.com too (which would not be covered by *.mydomain.com because it only has one .), certbot certonly --manual -d '*.mydomain.com' -d mydomain.com Certbot will tel…

I have tried the command: certbot certonly --cert-name www.mydomain.com -d *.mydomain.com but get the error: e[31mClient with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. You may need to use an authenticator plugin that can do chall…

That's probably because your original cert has an authentication plugin which uses the http-01 challenge configured. I think you should get the wildcard cert without specifying the previous cert with --cert-name. You'll get a new certificate, but that doesn't matter. Then, re-configure your webserv…

Here you'll need to specify an authenticator (like apache or nginx or webroot -w /path/to/your/webroot or standalone) and an installer (like apache or nginx or null for none): certbot run --cert-name mydomain.com -a authenticator -d "mydomain.com,www.mydomain.com,sub1.mydomain.com,sub2.mydomain.com…

[image] Osiris: That's probably because your original cert has an authentication plugin which uses the http-01 challenge configured. You can override that by explicitly adding --manual, although I think @Osiris 's suggestion not to reuse the same --cert-name also makes sense here.

[image] schoen: although I think @Osiris 's suggestion not to reuse the same --cert-name also makes sense here. In the commands I gave I actually did specify a --cert-name for a very good reason. It enables knowing exactly under which certificate name the active certificate resides, which allo…

Unfortunately, I don’t have easy access to the DNS server, just have access to the server where are installed the sites. And as I understood to request a wildcard certificate, I need to have access to the DNS server, right? So, for now I will create a certificate for the main domain and for the 2 s…

Subdomain certificates

Help

Topic		Replies	Views
Different certificate for subdomain Server	16	30905	May 9, 2018
Can I use letsencrypt in more than one subdomain?	37	141106	July 8, 2017
Create certificate for domain contain alot of subdomain Help	17	13841	July 10, 2018
Certificates for sub.subs.domian Help	4	8120	November 29, 2019
Is a certificate needed for each single subdomain?	4	1980	May 4, 2016

Subdomain certificates

Related topics