Letsencrypt Certificate for www vhost

Submitted by gnilebein on Sun, 05/21/2017 - 05:28

Hello,

I have three questions.

  1. Why you have removed the www vhosts from the "Domains associated with this server" list for letsencrypt? You create the www vhost... www DNS Records... why not the certificate? I think this should be the same at any point.

  2. Is it possible to bypass the HTTP validation and use DNS validation or is dns validation only used when HTTP validation is not possible?

  3. Is it possible that you add all aliasa domains of a primary domain thoe the "Domains associated with this server". So the certificate is valid for all domains?!

Best regards, Patrick

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Sun, 05/21/2017 - 12:48

1 - By default the cert request should be for domain.com and www.domain.com , as long as your webserver is configured to accept requests for both of those.

2 - Virtualmin should fall back to DNS validation in the upcoming 5.99 release.

3 - Not yet, but that would be a nice feature..

Submitted by gnilebein on Sun, 05/21/2017 - 13:55

Hey Jamie,

thanks for you answer.

  1. Now i am confused. Please see the youtube Video. I have created a new sub server. But the default request only contains the domain name without www. But the alias is created in nginx config and the DNS Record for www i also there...

https://youtu.be/GfifM2oHjsI

  1. Maybe you could add this feature in one of the next releases. This would ne very nice. I would be very grateful.

Submitted by JamieCameron on Sun, 05/21/2017 - 20:14

Oh, I didn't realize you were using Nginx there. That maybe the cause of this bug ..

Submitted by JamieCameron on Mon, 05/22/2017 - 00:10

Both of these issues will be fixed in future releases.

Submitted by JamieCameron on Mon, 05/22/2017 - 00:11

Status: Active » Fixed

Submitted by IssueBot on Mon, 06/05/2017 - 01:42

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.