Update README.md
formatting
This commit is contained in:
Michael J. Stealey
committed by
GitHub
GitHub
parent
a83b903096
commit
7537f3ac09
@@ -47,107 +47,107 @@ If you plan to run your WordPress site over https on port 443, then do the follo
|
||||
If you plan on using SSL certificates from [Let's Encrypt](https://letsencrypt.org) it is important that your public domain is already registered and reachable.
|
||||
|
||||
Run: `./letsencrypt/letsencrypt-init.sh DOMAIN_NAME`, where `DOMAIN_NAME` is the publicly registered domain name of your host.
|
||||
|
||||
```
|
||||
$ ./letsencrypt-init.sh example.com
|
||||
mysql uses an image, skipping
|
||||
wordpress uses an image, skipping
|
||||
nginx uses an image, skipping
|
||||
Creating mysql ...
|
||||
Creating mysql ... done
|
||||
Creating wordpress ...
|
||||
Creating wordpress ... done
|
||||
Creating nginx ...
|
||||
Creating nginx ... done
|
||||
Reloading nginx: nginx.
|
||||
Saving debug log to /var/log/letsencrypt/letsencrypt.log
|
||||
Plugins selected: Authenticator webroot, Installer None
|
||||
Enter email address (used for urgent renewal and security notices) (Enter 'c' to
|
||||
cancel): mjstealey@gmail.com
|
||||
|
||||
-------------------------------------------------------------------------------
|
||||
Please read the Terms of Service at
|
||||
https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf. You must agree
|
||||
in order to register with the ACME server at
|
||||
https://acme-v01.api.letsencrypt.org/directory
|
||||
-------------------------------------------------------------------------------
|
||||
(A)gree/(C)ancel: a
|
||||
|
||||
-------------------------------------------------------------------------------
|
||||
Would you be willing to share your email address with the Electronic Frontier
|
||||
Foundation, a founding partner of the Let's Encrypt project and the non-profit
|
||||
organization that develops Certbot? We'd like to send you email about EFF and
|
||||
our work to encrypt the web, protect its users and defend digital rights.
|
||||
-------------------------------------------------------------------------------
|
||||
(Y)es/(N)o: y
|
||||
Obtaining a new certificate
|
||||
Performing the following challenges:
|
||||
http-01 challenge for example.com
|
||||
http-01 challenge for www.example.com
|
||||
Using the webroot path /data/letsencrypt for all unmatched domains.
|
||||
Waiting for verification...
|
||||
Cleaning up challenges
|
||||
|
||||
IMPORTANT NOTES:
|
||||
ssl on;
|
||||
- Congratulations! Your certificate and chain have been saved at:
|
||||
/etc/letsencrypt/live/example.com/fullchain.pem
|
||||
Your key file has been saved at:
|
||||
/etc/letsencrypt/live/example.com/privkey.pem
|
||||
Your cert will expire on 2018-02-06. 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"
|
||||
- Your account credentials have been saved in your Certbot
|
||||
configuration directory at /etc/letsencrypt. You should make a
|
||||
secure backup of this folder now. This configuration directory will
|
||||
also contain certificates and private keys obtained by Certbot so
|
||||
making regular backups of this folder is ideal.
|
||||
- If you like Certbot, please consider supporting our work by:
|
||||
|
||||
Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
|
||||
Donating to EFF: https://eff.org/donate-le
|
||||
|
||||
Stopping nginx ... done
|
||||
Stopping wordpress ... done
|
||||
Stopping mysql ... done
|
||||
Going to remove nginx, wordpress, mysql
|
||||
Removing nginx ... done
|
||||
Removing wordpress ... done
|
||||
Removing mysql ... done
|
||||
INFO: update the nginx/wordpress_ssl.conf file
|
||||
- 4: server_name example.com;
|
||||
- 19: server_name example.com www.example.com;
|
||||
- 46: ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
|
||||
- 47: ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
|
||||
- 48: ssl_trusted_certificate /etc/letsencrypt/live/example.com/chain.pem;
|
||||
```
|
||||
|
||||
```console
|
||||
$ ./letsencrypt-init.sh example.com
|
||||
mysql uses an image, skipping
|
||||
wordpress uses an image, skipping
|
||||
nginx uses an image, skipping
|
||||
Creating mysql ...
|
||||
Creating mysql ... done
|
||||
Creating wordpress ...
|
||||
Creating wordpress ... done
|
||||
Creating nginx ...
|
||||
Creating nginx ... done
|
||||
Reloading nginx: nginx.
|
||||
Saving debug log to /var/log/letsencrypt/letsencrypt.log
|
||||
Plugins selected: Authenticator webroot, Installer None
|
||||
Enter email address (used for urgent renewal and security notices) (Enter 'c' to
|
||||
cancel): mjstealey@gmail.com
|
||||
|
||||
-------------------------------------------------------------------------------
|
||||
Please read the Terms of Service at
|
||||
https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf. You must agree
|
||||
in order to register with the ACME server at
|
||||
https://acme-v01.api.letsencrypt.org/directory
|
||||
-------------------------------------------------------------------------------
|
||||
(A)gree/(C)ancel: a
|
||||
|
||||
-------------------------------------------------------------------------------
|
||||
Would you be willing to share your email address with the Electronic Frontier
|
||||
Foundation, a founding partner of the Let's Encrypt project and the non-profit
|
||||
organization that develops Certbot? We'd like to send you email about EFF and
|
||||
our work to encrypt the web, protect its users and defend digital rights.
|
||||
-------------------------------------------------------------------------------
|
||||
(Y)es/(N)o: y
|
||||
Obtaining a new certificate
|
||||
Performing the following challenges:
|
||||
http-01 challenge for example.com
|
||||
http-01 challenge for www.example.com
|
||||
Using the webroot path /data/letsencrypt for all unmatched domains.
|
||||
Waiting for verification...
|
||||
Cleaning up challenges
|
||||
|
||||
IMPORTANT NOTES:
|
||||
ssl on;
|
||||
- Congratulations! Your certificate and chain have been saved at:
|
||||
/etc/letsencrypt/live/example.com/fullchain.pem
|
||||
Your key file has been saved at:
|
||||
/etc/letsencrypt/live/example.com/privkey.pem
|
||||
Your cert will expire on 2018-02-06. 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"
|
||||
- Your account credentials have been saved in your Certbot
|
||||
configuration directory at /etc/letsencrypt. You should make a
|
||||
secure backup of this folder now. This configuration directory will
|
||||
also contain certificates and private keys obtained by Certbot so
|
||||
making regular backups of this folder is ideal.
|
||||
- If you like Certbot, please consider supporting our work by:
|
||||
|
||||
Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
|
||||
Donating to EFF: https://eff.org/donate-le
|
||||
|
||||
Stopping nginx ... done
|
||||
Stopping wordpress ... done
|
||||
Stopping mysql ... done
|
||||
Going to remove nginx, wordpress, mysql
|
||||
Removing nginx ... done
|
||||
Removing wordpress ... done
|
||||
Removing mysql ... done
|
||||
INFO: update the nginx/wordpress_ssl.conf file
|
||||
- 4: server_name example.com;
|
||||
- 19: server_name example.com www.example.com;
|
||||
- 46: ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
|
||||
- 47: ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
|
||||
- 48: ssl_trusted_certificate /etc/letsencrypt/live/example.com/chain.pem;
|
||||
```
|
||||
Information about updating your Let's Encrypt certificate can be found further down in this document.
|
||||
|
||||
- **Self signed**
|
||||
|
||||
If you plan on using self signed SSL certificates, run: `./letsencrypt/self-signed-init.sh DOMAIN_NAME`, where `DOMAIN_NAME` is the `CN` you want to assign to the host (commonly `localhost`).
|
||||
|
||||
```
|
||||
$ cd letsencrypt/
|
||||
$ ./self-signed-init.sh localhost
|
||||
INFO: making certs directory
|
||||
Generating a 4096 bit RSA private key
|
||||
................................................................................................................................................................................................................................................++
|
||||
....................................................++
|
||||
writing new private key to 'key.pem'
|
||||
-----
|
||||
INFO: update the nginx/wordpress_ssl.conf file
|
||||
- 4: server_name localhost;
|
||||
- 19: server_name localhost www.localhost;
|
||||
- 46: ssl_certificate /etc/letsencrypt/live/localhost/cert.pem;
|
||||
- 47: ssl_certificate_key /etc/letsencrypt/live/localhost/privkey.pem;
|
||||
- 48: #ssl_trusted_certificate /etc/letsencrypt/live/DOMAIN_NAME/chain.pem; <-- COMMENT OUT OR REMOVE
|
||||
```
|
||||
```console
|
||||
$ cd letsencrypt/
|
||||
$ ./self-signed-init.sh localhost
|
||||
INFO: making certs directory
|
||||
Generating a 4096 bit RSA private key
|
||||
................................................................................................................................................................................................................................................++
|
||||
....................................................++
|
||||
writing new private key to 'key.pem'
|
||||
-----
|
||||
INFO: update the nginx/wordpress_ssl.conf file
|
||||
- 4: server_name localhost;
|
||||
- 19: server_name localhost www.localhost;
|
||||
- 46: ssl_certificate /etc/letsencrypt/live/localhost/cert.pem;
|
||||
- 47: ssl_certificate_key /etc/letsencrypt/live/localhost/privkey.pem;
|
||||
- 48: #ssl_trusted_certificate /etc/letsencrypt/live/DOMAIN_NAME/chain.pem; <-- COMMENT OUT OR REMOVE
|
||||
```
|
||||
|
||||
- **Bring your own**
|
||||
|
||||
If you plan to use pre-existing certificates you will need to update the `nginx/wordpress_ssl.conf` file with the appropriate settings to the kind of certificates you have.
|
||||
If you plan to use pre-existing certificates you will need to update the `nginx/wordpress_ssl.conf` file with the appropriate settings to the kind of certificates you have.
|
||||
|
||||
**Finally**
|
||||
|
||||
|
||||
Reference in New Issue
Block a user