I ran this command: certbot certonly --authenticator standalone --pre-hook “apachectl -k stop” --post-hook “apachectl -k start”
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Please enter in your domain name(s) (comma and/or space separated) (Enter ‘c’
to cancel): rm.supportform.se
Running pre-hook command: apachectl -k stop
Error output from apachectl:
[Mon Sep 17 22:29:22.203629 2018] [so:warn] [pid 20767] AH01574: module dav_module is already loaded, skipping
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for rm.supportform.se
Waiting for verification…
Cleaning up challenges
Running post-hook command: apachectl -k start
Error output from apachectl:
[Mon Sep 17 22:29:27.524210 2018] [so:warn] [pid 20786] AH01574: module dav_module is already loaded, skipping
IMPORTANT NOTES:
Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/rm.supportform.se/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/rm.supportform.se/privkey.pem
Your cert will expire on 2018-12-16. To obtain a new or tweaked
version of this certificate in the future, simply run certbot
again. To non-interactively renew all of your certificates, run
“certbot renew”
If you like Certbot, please consider supporting our work by:
Even better: just use --apache, so it also will be the authenticator, not just the installer
@ouaburst You could use certbot --apache --cert-name rm.supportform.se to install the certificate into Apache. It should tell you you already have a certificate for that hostname and will ask you if you just want to install the certificate. You can choose just installing the existing certificate.
If that works (if not, tell us here), you can use certbot renew for future renewals. But I think Debian has a systemd timer or cronjob in its package. If a cronjob or systemd timer exist, you won't have to worry about running certbot renew manually.
Gives: Assessment failed: Unable to connect to the server
root@redmine ~# certbot --apache --cert-name rm.supportform.se
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Cert not yet due for renewal
You have an existing certificate that has exactly the same domains or certificate name you requested and isn’t close to expiry.
(ref: /etc/letsencrypt/renewal/rm.supportform.se.conf)
What would you like to do?
1: Attempt to reinstall this existing certificate
2: Renew & replace the cert (limit ~5 per 7 days)
Select the appropriate number [1-2] then [enter] (press ‘c’ to cancel): 1
Keeping the existing certificate
Deploying Certificate to VirtualHost /etc/apache2/sites-enabled/redmine.conf
Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.
1: No redirect - Make no further changes to the webserver configuration.
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for
new sites, or if you’re confident your site works on HTTPS. You can undo this
change by editing your web server’s configuration.
Select the appropriate number [1-2] then [enter] (press ‘c’ to cancel): 1
Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/rm.supportform.se/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/rm.supportform.se/privkey.pem
Your cert will expire on 2018-12-16. To obtain a new or tweaked
version of this certificate in the future, simply run certbot again
with the “certonly” option. To non-interactively renew all of
your certificates, run “certbot renew”
If you like Certbot, please consider supporting our work by: