|
@@ -14,14 +14,13 @@ Several packages need access to the private key. Not all are run as root. An exa
|
14
|
14
|
|
15
|
15
|
Certificate renewal is done automatically using cron. The cron script must be aware of private key copies and update them as well. Services that depend on new keys must also be bounced. It is up to roles that rely on keys to modify the cron script (preferably using `lineinfile` or something similar) to accomplish this.
|
16
|
16
|
|
17
|
|
-### Testing support
|
|
17
|
+If you changed something that requires new domains or subdomains to be considered when generating the certificates, do not just delete the files in /etc/letsencrypt/live!
|
|
18
|
+Instead, use /root/letsencrypt/letsencrypt-auto delete to remove the old certificates and then re-run the common role in this playbook.
|
18
|
19
|
|
19
|
|
-An isolated VM deployed with Vagrant is used for testing. The Let's Encrypt service cannot be used to get keys for it, since it is not bound with DNS. A self-signed wildcard key is therefore used for testing. The wildcard key, certificate, and chain are installed in the same way that Let's Encrypt keys are installed.
|
|
20
|
+## Firewall
|
20
|
21
|
|
21
|
|
-### Alternative approaches
|
|
22
|
+ufw is used to provide a simpler iptables interface.
|
22
|
23
|
|
23
|
|
-Another way to generate certificates is to generate one certificate per domain and expect each module that uses a subdomain to generate its own certificate for the subdomain.
|
24
|
|
-
|
25
|
|
-This was prototyped. The common role included a parameterized task list that could be invoked by modules that needed to generate a key. The certificate renewal script run by cron could be modified to update all the certificates in the `live` directory.
|
26
|
|
-
|
27
|
|
-This approach was rejected due to complexity. This would have been the first time modules needed to invoke a task list from another module. Managing multiple certificates is also more complicated.
|
|
24
|
+You may run into some issues with enabling ufw. In my case, this was caused by installing
|
|
25
|
+updates, including a new kernel, but not rebooting before attempting to install ufw.
|
|
26
|
+A simple reboot fixed the problems.
|