Tin Minnow wrote:Is there any plan to add this functionality to dietpi-letsencrypt in the future? I only ask because it's really nice having it automated for you and have it setting up a cron job as well, especially if you're looking to host multiple websites. I might have a look at adding this if I get time.
Hi Tin,
Its not planned at the moment, but if you can create a ticket on Github, we can look into it:
https://github.com/Fourdee/DietPi/issues. The main issue is we would need to support all 3 webservers for this, so initially a simple job, multiplied by 3
Code: Select all
--duplicate --agree-tos $cli_redirect
Duplicate means: If a cert already exists, overwrite it with this one.
Agree Tos means: I accept the terms and services of Certbot.
$cli_redirect: If this is enabled (--redirect), all http traffic will be forward to https
So basically that involves making an vhost entry then running certbot-auto with some parameters?
Not sure if i'am honest.
I think certbot just sends a simple ping on port 80, out from your system, back to the base webserver (eg:
http://myweb.com). Once thats been accepted, certbot-auto will continue setting up the cert.
I'am also not sure if certbot-auto works with subdomains. A good example is users trying to use
http://mywebsite.noip.org. Regardless of the subdomain, Certbot only allows 5 certs per month (from my testing a while back). So Free NoIp users cannot setup a cert.