Virtualmin LetsEncrypt path doesn't match DocumentRoot

Submitted by dfj on Tue, 11/08/2016 - 08:56

I've gotten the LetsEncrypt module to work on multiple other virtualhosts, but since this one uses a non-default DocumentRoot. The acme-challenge fails to download.

How do i get LetsEncrypt module to generate the challenge-file in the correct location?

Files: 
Image icon Screen Shot 2016-11-08 at 15.44.00.png
Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Tue, 11/08/2016 - 19:17

How did you change the document root for this domain exactly?

Submitted by dfj on Wed, 11/09/2016 - 01:22

Through Edit directives, as a guy whos used to working without a gui "Edit directives" seemed familiar

Submitted by just_me on Wed, 11/09/2016 - 23:25

I am using one directory for all letsencrypt validation, but i also only use one certificate; which holds all domains of that virutal server. This is a little work to do, but i think its much easier to maintain lateron. You can read more about this here: https://www.virtualmin.com/node/42012

But i will have to update it, reflecting new information.

Submitted by JamieCameron on Thu, 11/10/2016 - 00:24

Try instead changing the home dir on the Website Options page (on the left menu). This way, Virtualmin will know what the correct home directory is.

Submitted by dfj on Thu, 11/10/2016 - 01:24

That changes the directory as expected but its relative to /home/[username]/domains/[virtualhost-name], and it does not allow an absolute path or symbolic links. I need it to be /home/[username]/apps/[git-repo-name]/api/web. Because i have multiple domains using the same application.

Submitted by JamieCameron on Thu, 11/10/2016 - 11:25

One work-around is as follows :

  1. SSH in as root and get the domain's unique ID with the command virtualmin list-domains --domain example.com --id-only
  2. Edit the file under /etc/webmin/virtual-server/domains with that ID
  3. Change the public_html_path line to the correct directory

Submitted by eraser on Mon, 08/20/2018 - 04:02

Thanks to JamieCameron. That workaround helped me alot. I am using a non-default document root aswell and was facing the same Let's Encrypt certificate requesting issue.

Submitted by IssueBot on Mon, 09/03/2018 - 04:07

Status: Fixed ยป Closed (fixed)

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