acme.sh/README.md

162 lines
4.3 KiB
Markdown
Raw Normal View History

2015-12-26 13:44:39 +00:00
# le
Simplest shell script for LetsEncrypt free Certificate client
Pure written in bash, no dependencies to python , acme-tiny or LetsEncrypt official client (https://github.com/letsencrypt/letsencrypt)
2015-12-30 14:15:33 +00:00
Just one script, to issue, renew your certificates automatically.
2015-12-26 13:44:39 +00:00
2015-12-26 13:55:26 +00:00
Probably it's the smallest&easiest&smartest shell script to automatically issue&renew the free certificates from LetsEncrypt.
2015-12-26 13:44:39 +00:00
#Supported OS
2015-12-27 05:23:25 +00:00
1. Ubuntu/Debian.
2. CentOS
2015-12-26 13:44:39 +00:00
2016-01-10 02:59:51 +00:00
#Supported Mode
1. Webroot mode
2. Standalone mode
3. Apache mode
2016-01-21 16:17:20 +00:00
4. Dns mode
2016-01-10 02:59:51 +00:00
2015-12-26 13:44:39 +00:00
#How to use
1. Clone this project: https://github.com/Neilpang/le.git
2. Install le:
```
./le.sh install
```
2015-12-27 05:50:40 +00:00
Which does 3 jobs:
* create and copy `le.sh` to your home dir: `~/.le`
2015-12-26 13:44:39 +00:00
All the certs will be placed in this folder.
2015-12-26 14:06:11 +00:00
* create symbol link: `/bin/le -> ~/.le/le.sh`
2015-12-27 05:50:40 +00:00
* create everyday cron job to check and renew the cert if needed.
2015-12-27 05:52:46 +00:00
2015-12-27 05:50:40 +00:00
Ok, you are ready to issue cert now.
2015-12-26 13:44:39 +00:00
Show help message:
```
root@xvm:~# le
Usage: issue|renew|renewAll|createAccountKey|createDomainKey|createCSR|install|uninstall
root@xvm:~# le issue
2016-01-21 16:16:43 +00:00
Usage: le issue webroot|no|apache|dns a.com [www.a.com,b.com,c.com]|no [key-length]|no [cert-file-path]|no [key-file-path]|no [ca-cert-file-path]|no [reloadCmd]|no
2015-12-26 13:44:39 +00:00
```
2016-01-07 10:10:05 +00:00
2016-01-10 05:02:00 +00:00
Set the param value to "no" means you want to ignore it.
For example, if you give "no" to "key-length", it will use default length 2048.
And if you give 'no' to 'cert-file-path', it will not copy the issued cert to the "cert-file-path".
In all the cases, the issued cert will be placed in "~/.le/domain.com/"
2015-12-26 13:44:39 +00:00
# Just issue a cert:
```
le issue /home/wwwroot/aa.com aa.com www.aa.com,cp.aa.com
```
2015-12-28 08:00:28 +00:00
First argument `/home/wwwroot/aa.com` is the web root folder, You must have `write` access to this folder.
2015-12-26 13:44:39 +00:00
2015-12-28 07:57:22 +00:00
Second argument "aa.com" is the main domain you want to issue cert for.
2015-12-26 13:44:39 +00:00
2015-12-28 08:00:28 +00:00
Third argument is the additional domain list you want to use. Comma separated list, which is Optional.
2015-12-26 13:44:39 +00:00
2015-12-28 07:57:22 +00:00
You must point and bind all the domains to the same webroot dir:`/home/wwwroot/aa.com`
2015-12-26 13:44:39 +00:00
The cert will be placed in `~/.le/aa.com/`
The issued cert will be renewed every 50 days automatically.
2015-12-26 16:35:59 +00:00
# Issue a cert, and install to apache/nginx
2015-12-26 13:44:39 +00:00
```
2016-01-08 13:44:32 +00:00
le issue /home/wwwroot/aa.com aa.com www.aa.com,cp.aa.com 2048 /path/to/certfile/in/apache/nginx /path/to/keyfile/in/apache/nginx /path/to/ca/certfile/apahce/nginx "service apache2/nginx reload"
2015-12-26 13:44:39 +00:00
```
2015-12-28 08:00:28 +00:00
Which issues the cert and then links it to the production apache or nginx path.
The cert will be renewed every 50 days by default (which is configurable), Once the cert is renewed, the apache/nginx will be automatically reloaded by the command: ` service apache2 reload` or `service nginx reload`
2015-12-26 13:44:39 +00:00
2016-01-05 13:59:27 +00:00
# Use Standalone server:
2016-01-07 10:10:05 +00:00
Same usage as all above, just give `no` as the webroot.
2016-01-05 13:59:27 +00:00
The tcp `80` port must be free to listen, otherwise you will be prompted to free the `80` port and try again.
```
le issue no aa.com www.aa.com,cp.aa.com
```
2016-01-10 02:59:51 +00:00
# Use Apache mode:
2016-01-10 03:03:53 +00:00
If you are running a web server, apache or nginx, it is recommended to use the Webroot mode.
2016-01-10 02:59:51 +00:00
Particularly, if you are running an apache server, you can use apache mode instead. Which doesn't write any file to your web root folder.
Just set string "apache" to the first argument, it will use apache plugin automatically.
```
le issue apache aa.com www.aa.com
```
All the other arguments are the same with previous.
2015-12-26 13:44:39 +00:00
2016-01-21 16:16:43 +00:00
# Use DNS mode:
Support the latest dns-01 challenge.
```
le issue dns aa.com www.aa.com
```
Use domain api to automatically add dns record is not finished yet.
2016-01-21 16:19:54 +00:00
So, you must manually add the txt record to finish verifying.
2016-01-21 16:16:43 +00:00
2016-01-21 16:19:54 +00:00
You will get the output like bellow:
2016-01-21 16:16:43 +00:00
```
Add the following txt record:
Domain:_acme-challenge.aa.com
Txt value:9ihDbjYfTExAYeDs4DBUeuTo18KBzwvTEjUnSwd32-c
Add the following txt record:
Domain:_acme-challenge.www.aa.com
Txt value:9ihDbjxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
```
Please add those txt records to the domains. Waiting for the dns to take effect.
2016-01-21 16:19:54 +00:00
Then just retry with 'renew' command:
2016-01-21 16:16:43 +00:00
```
le renew aa.com
```
Ok, it's finished.
2015-12-26 13:44:39 +00:00
#Under the Hood
2015-12-26 16:33:53 +00:00
Speak ACME language with bash directly to Let's encrypt.
2015-12-26 13:44:39 +00:00
TODO:
2016-01-11 05:23:02 +00:00
#Acknowledgment
1. Acme-tiny: https://github.com/diafygi/acme-tiny
2. ACME protocol: https://github.com/ietf-wg-acme/acme
3. letsencrypt: https://github.com/letsencrypt/letsencrypt
2015-12-26 13:44:39 +00:00
#License & Other
License is GPLv3
2015-12-26 13:47:28 +00:00
Please Star and Fork me.
2015-12-26 13:44:39 +00:00
Issues and pullrequests are welcomed.