crypto:letsencrypt
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| crypto:letsencrypt [2019-05-20 00:50] – adding config snippet for nginx gabriel | crypto:letsencrypt [2019-05-21 22:00] – note re: badphotography.ca gabriel | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| We're currently using Let's Encrypt to generate and manage TLS certificates for quay.net and several other domains. | We're currently using Let's Encrypt to generate and manage TLS certificates for quay.net and several other domains. | ||
| - | Now that Let's Encrypt supports wildcard certs, our cert has been modified accordingly. | + | Now that Let's Encrypt supports wildcard certs, our cert has been modified accordingly. |
| Thus, we'll use the manual process for generating and managing our certificates. | Thus, we'll use the manual process for generating and managing our certificates. | ||
| Line 32: | Line 32: | ||
| < | < | ||
| - | #location / | + | # USAGE: enable this configuration for Route 53 validation for Let's Encrypt |
| - | # alias / | + | location / |
| - | # autoindex off; | + | alias / |
| - | #} | + | |
| + | } | ||
| </ | </ | ||
| + | |||
| + | > **Note:** locally we have to manage some custom config for [[https:// | ||
| The instructions are provided at each step and are fairly simple. | The instructions are provided at each step and are fairly simple. | ||
crypto/letsencrypt.txt · Last modified: 2019-10-16 13:03 by gabriel