1 # An ACME Shell script: acme.sh
2 - An ACME protocol client written purely in Shell (Unix shell) language.
3 - Fully ACME protocol implementation.
4 - Simple, powerful and very easy to use. You only need 3 minutes to learn.
5 - Bash, dash and sh compatible.
6 - Simplest shell script for Let's Encrypt free certificate client.
7 - Purely written in Shell with no dependencies on python or Let's Encrypt official client.
8 - Just one script, to issue, renew and install your certificates automatically.
9 - DOES NOT require `root/sudoer` access.
11 It's probably the `easiest&smallest&smartest` shell script to automatically issue & renew the free certificates from Let's Encrypt.
14 Wiki: https://github.com/Neilpang/acme.sh/wiki
17 | NO | Status| Platform|
18 |----|-------|---------|
19 |1|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/ubuntu-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)| Ubuntu
20 |2|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/debian-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)| Debian
21 |3|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/centos-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|CentOS
22 |4|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/windows.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Windows (cygwin with curl, openssl and crontab included)
23 |5|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/freebsd.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|FreeBSD
24 |6|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/pfsense.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|pfsense
25 |7|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/opensuse-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|openSUSE
26 |8|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/alpine-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Alpine Linux (with curl)
27 |9|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/base-archlinux.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Archlinux
28 |10|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/fedora-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|fedora
29 |11|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/kalilinux-kali-linux-docker.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Kali Linux
30 |12|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/oraclelinux-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Oracle Linux
31 |13|[![](https://cdn.rawgit.com/Neilpang/letest/master/status/proxmox.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)| Proxmox https://pve.proxmox.com/wiki/HTTPSCertificateConfiguration#Let.27s_Encrypt_using_acme.sh
32 |14|--| Cloud Linux https://github.com/Neilpang/le/issues/111
34 For all build statuses, check our [daily build project](https://github.com/Neilpang/acmetest):
36 https://github.com/Neilpang/acmetest
45 # Upgrade from 1.x to 2.x
47 You can simply uninstall 1.x and re-install 2.x.
48 2.x is 100% compatible to 1.x. You will feel right at home as if nothing has changed.
50 # le.sh renamed to acme.sh NOW!
52 All configurations are 100% compatible between `le.sh` and `acme.sh`. You just need to uninstall `le.sh` and re-install `acme.sh` again.
53 Nothing will be broken during the process.
57 ### 1. Install online:
59 Check this project:https://github.com/Neilpang/get.acme.sh
62 curl https://get.acme.sh | sh
69 wget -O - https://get.acme.sh | sh
74 ### 2. Or, Install from git:
79 git clone https://github.com/Neilpang/acme.sh.git
84 You `don't have to be root` then, although `it is recommended`.
86 The installer will perform 3 actions:
88 1. Create and copy `acme.sh` to your home dir (`$HOME`): `~/.acme.sh/`.
89 All certs will be placed in this folder.
90 2. Create alia for: `acme.sh=~/.acme.sh/acme.sh`.
91 3. Create everyday cron job to check and renew the cert if needed.
96 0 0 * * * "/home/user/.acme.sh"/acme.sh --cron --home "/home/user/.acme.sh" > /dev/null
99 After the installation, you must close current terminal and reopen again to make the alias take effect.
101 Ok, you are ready to issue cert now.
106 https://github.com/Neilpang/acme.sh
108 Usage: acme.sh command ...[parameters]....
110 --help, -h Show this help message.
111 --version, -v Show version info.
112 --install Install acme.sh to your system.
113 --uninstall Uninstall acme.sh, and uninstall the cron job.
114 --issue Issue a cert.
115 --installcert Install the issued cert to apache/nginx or any other server.
116 --renew, -r Renew a cert.
117 --renewAll Renew all the certs
118 --revoke Revoke a cert.
119 --installcronjob Install the cron job to renew certs, you don't need to call this. The 'install' command can automatically install the cron job.
120 --uninstallcronjob Uninstall the cron job. The 'uninstall' command can do this automatically.
121 --cron Run cron job to renew all the certs.
122 --toPkcs Export the certificate and key to a pfx file.
123 --createAccountKey, -cak Create an account private key, professional use.
124 --createDomainKey, -cdk Create an domain private key, professional use.
125 --createCSR, -ccsr Create CSR , professional use.
128 --domain, -d domain.tld Specifies a domain, used to issue, renew or revoke etc.
129 --force, -f Used to force to install or force to renew a cert immediately.
130 --staging, --test Use staging server, just for test.
131 --debug Output debug info.
133 --webroot, -w /path/to/webroot Specifies the web root folder for web root mode.
134 --standalone Use standalone mode.
135 --apache Use apache mode.
136 --dns [dns-cf|dns-dp|dns-cx|/path/to/api/file] Use dns mode or dns api.
138 --keylength, -k [2048] Specifies the domain key length: 2048, 3072, 4096, 8192 or ec-256, ec-384.
139 --accountkeylength, -ak [2048] Specifies the account key length.
141 These parameters are to install the cert to nginx/apache or anyother server after issue/renew a cert:
143 --certpath /path/to/real/cert/file After issue/renew, the cert will be copied to this path.
144 --keypath /path/to/real/key/file After issue/renew, the key will be copied to this path.
145 --capath /path/to/real/ca/file After issue/renew, the intermediate cert will be copied to this path.
146 --fullchainpath /path/to/fullchain/file After issue/renew, the fullchain cert will be copied to this path.
148 --reloadcmd "service nginx reload" After issue/renew, it's used to reload the server.
150 --accountconf Specifies a customized account config file.
151 --home Specifies the home dir for acme.sh .
152 --certhome Specifies the home dir to save all the certs, only valid for '--install' command.
153 --useragent Specifies the user agent string. it will be saved for future use too.
154 --accountemail Specifies the account email for registering, Only valid for the '--install' command.
155 --accountkey Specifies the account key path, Only valid for the '--install' command.
156 --days Specifies the days to renew the cert when using '--issue' command. The max value is 80 days.
162 **Example 1:** Single domain.
165 acme.sh --issue -d aa.com -w /home/wwwroot/aa.com
168 **Example 2:** Multiple domains in the same cert.
171 acme.sh --issue -d aa.com -d www.aa.com -d cp.aa.com -w /home/wwwroot/aa.com
174 The parameter `/home/wwwroot/aa.com` is the web root folder. You **MUST** have `write access` to this folder.
176 Second argument **"aa.com"** is the main domain you want to issue cert for.
177 You must have at least a domain there.
179 You must point and bind all the domains to the same webroot dir: `/home/wwwroot/aa.com`.
181 Generate/issued certs will be placed in `~/.acme.sh/aa.com/`
183 The issued cert will be renewed every 80 days automatically.
185 More examples: https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert
188 # Install issued cert to apache/nginx etc.
190 After you issue a cert, you probably want to install the cert with your nginx/apache or other servers you may be using.
193 acme.sh --installcert -d aa.com \
194 --certpath /path/to/certfile/in/apache/nginx \
195 --keypath /path/to/keyfile/in/apache/nginx \
196 --capath /path/to/ca/certfile/apache/nginx \
197 --fullchainpath path/to/fullchain/certfile/apache/nginx \
198 --reloadcmd "service apache2|nginx reload"
201 Only the domain is required, all the other parameters are optional.
203 Install the issued cert/key to the production apache or nginx path.
205 The cert will be `renewed every 80 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`.
207 # Use Standalone server to issue cert
209 **(requires you be root/sudoer, or you have permission to listen tcp 80 port)**
211 Same usage as above, just give `no` as `--webroot` or `-w`.
213 The tcp `80` port **MUST** be free to listen, otherwise you will be prompted to free the `80` port and try again.
216 acme.sh --issue --standalone -d aa.com -d www.aa.com -d cp.aa.com
219 More examples: https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert
223 **(requires you be root/sudoer, since it is required to interact with apache server)**
225 If you are running a web server, apache or nginx, it is recommended to use the `Webroot mode`.
227 Particularly, if you are running an apache server, you should use apache mode instead. This mode doesn't write any files to your web root folder.
229 Just set string "apache" as the second argument, it will force use of apache plugin automatically.
232 acme.sh --issue --apache -d aa.com -d www.aa.com -d user.aa.com
235 More examples: https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert
239 Support the `dns-01` challenge.
242 acme.sh --issue --dns -d aa.com -d www.aa.com -d user.aa.com
245 You should get the output like below:
248 Add the following txt record:
249 Domain:_acme-challenge.aa.com
250 Txt value:9ihDbjYfTExAYeDs4DBUeuTo18KBzwvTEjUnSwd32-c
252 Add the following txt record:
253 Domain:_acme-challenge.www.aa.com
254 Txt value:9ihDbjxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
256 Please add those txt records to the domains. Waiting for the dns to take effect.
260 Then just rerun with `renew` argument:
263 acme.sh --renew -d aa.com
268 # Automatic DNS API integration
270 If your DNS provider supports API access, we can use API to automatically issue the certs.
272 You don't have do anything manually!
274 ### Currently acme.sh supports:
276 1. Cloudflare.com API
279 4. AWS Route 53, see: https://github.com/Neilpang/acme.sh/issues/65
281 ##### More APIs are coming soon...
283 If your DNS provider is not on the supported list above, you can write your own script API easily. If you do please consider submitting a [Pull Request](https://github.com/Neilpang/acme.sh/pulls) and contribute to the project.
285 For more details: [How to use dns api](dnsapi)
287 # Issue ECC certificate:
289 `Let's Encrypt` now can issue **ECDSA** certificates.
291 And we also support it.
293 Just set the `length` parameter with a prefix `ec-`.
297 ### Single domain ECC cerfiticate:
300 acme.sh --issue -w /home/wwwroot/aa.com -d aa.com --keylength ec-256
303 SAN multi domain ECC certificate:
306 acme.sh --issue -w /home/wwwroot/aa.com -d aa.com -d www.aa.com --keylength ec-256
309 Please look at the last parameter above.
313 1. **ec-256 (prime256v1, "ECDSA P-256")**
314 2. **ec-384 (secp384r1, "ECDSA P-384")**
315 3. **ec-521 (secp521r1, "ECDSA P-521", which is not supported by Let's Encrypt yet.)**
319 Speak ACME language using shell, directly to "Let's Encrypt".
324 1. Acme-tiny: https://github.com/diafygi/acme-tiny
325 2. ACME protocol: https://github.com/ietf-wg-acme/acme
326 3. letsencrypt: https://github.com/letsencrypt/letsencrypt
332 Please Star and Fork me.
334 [Issues](https://github.com/Neilpang/acme.sh/issues) and [pull requests](https://github.com/Neilpang/acme.sh/pulls) are welcomed.