Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
module:letsyncrypt [2018/02/27 22:30] – Document ToS stuff deuce | module:letsyncrypt [2019/07/17 00:48] – [Setup] Add syntax highlighting digital man |
---|
If you have multiple domain names, you can have LetSyncrypt put them all in a single certificate, even if you have virtual hosts. Edit the ''[[dir:ctrl]]/letsyncrypt.ini'' file and add a [Domains] section where the key is the hostname, and the value is the web root for that domain: | If you have multiple domain names, you can have LetSyncrypt put them all in a single certificate, even if you have virtual hosts. Edit the ''[[dir:ctrl]]/letsyncrypt.ini'' file and add a [Domains] section where the key is the hostname, and the value is the web root for that domain: |
| |
<file> | <file ini> |
[Domains] | [Domains] |
nix.synchro.net=/sbbs/web/root | nix.synchro.net=/sbbs/web/root |
This example has four domains (nix.synchro.net, home.bbsdev.net, gallery.bbsdev.net, and pics.bbsdev.net). The last two are virtual hosts, so have their web root as a subdirectory of the main web root. | This example has four domains (nix.synchro.net, home.bbsdev.net, gallery.bbsdev.net, and pics.bbsdev.net). The last two are virtual hosts, so have their web root as a subdirectory of the main web root. |
| |
You can specify the ACMEv2 endpoint using the ''Host'' and ''Directory'' global keys. ''Host'' is the domain name of the ACMEv2 endpoint, and ''Directory'' is appended to it to generate the URL that is fetched for the Directory object. You can also indicate that you agree to the Terms of Service by setting TOSAgreed to true. | You can specify the ACMEv2 endpoint using the ''Host'' and ''Directory'' keys in the [[config:ini_files#root_section|root section]]. ''Host'' is the domain name of the ACMEv2 endpoint, and ''Directory'' is appended to it to generate the URL that is fetched for the Directory object. You can also indicate that you agree to the Terms of Service by setting TOSAgreed to true. |
| |
<file> | <file ini> |
Host=acme-staging-v02.api.letsencrypt.org | Host=acme-v02.api.letsencrypt.org |
Directory=/directory | Directory=/directory |
TOSAgreed=true | TOSAgreed=true |
</file> | </file> |
| |
| Note that without the TOSAgreed=true line, you will likely never get a certificate, but the first few words in this file at present are "This Subscriber Agreement (“Agreement”) is a legally binding contract" |
| |
Do not modify the ''State'' or ''key_id'' sections of this file. | Do not modify the ''State'' or ''key_id'' sections of this file. |
| |
''%%--tos%%'' Prints the URL for the Terms of Service. | ''%%--tos%%'' Prints the URL for the Terms of Service. |
| |
===== Important Caveat ===== | |
| |
At present (February 27, 2018), Let's Encrypt does not support ACMEv2 for trusted certificates. The server was expected to go live on February 27, 2018, but it was [[https://community.letsencrypt.org/t/acmev2-and-wildcard-launch-delay/53654|delayed]]. Once it goes live, letsyncrypt.js will be updated to use the newly announced server (likely acme-v02.api.letsencrypt.org). Until then, installed certificates will not be trusted, being issued by the staging server, signed by “Fake LE Intermediate X1”. | |
| |
===== See Also ===== | ===== See Also ===== |