#5353 Letsencrypt

[Jaret]

We have a problem in FreeBSD with certificate createion using Letsnecrypt (acme.sh), trying to assign a certificate to Webmin.

Requesting a new certificate for webmin.domain.com, using the website directory /usr/home/webmin/public_html ..
.. request failed : Expected full certificate file /etc/letsencrypt/live/webmin.domain.com/fullchain.pem was not found

The location needs to be changed from /etc/letsencrypt/live to /usr/local/etc/letsencrypt/live to find the certificate.

[Ilia]

Install certbot package:

pkg install py37-certbot

[Jaret]

I tried with the py-certbot port and as well with acme.sh (which are essentially the same). Both report the exact same above issue in Webmin. Webmin expects /etc/letsencrypt/live/ to be the default location, but it's not anymore. You may want to check it out for yourself in a VM install. If it were possible change the default location Webmin expects in a module configuration for Letsencrypt, that would mitigate any future issues with Letsencrypt save locations across many operating systems should things change on those operating systems.

[Ilia]

Jamie made a patch:
https://github.com/webmin/webmin/commit/9639e29a63f029ad9e68c036b25c039dbfca4f56

[Jaret]

This needs to be reopened again. It's not fixed.

[Jamie Cameron]

Or as a work-around, you can run ln -s /usr/local/etc/letsencrypt /etc/letsencrypt

[Jaret]

Yeah I know. I did the workaround. I'm finding bugs to report so things work properly. If some settings for location options could be added to the module it would be good for all platforms, to set their own settings for the letsencrypt file drop location rather than using workarounds.

[Jamie Cameron]

Since /usr/local/etc is the default path for certs on FreeBSD, we'll have Webmin check that directory as well in the next release.