1 # An ACME Shell script: acme.sh [![Build Status](https://travis-ci.org/Neilpang/acme.sh.svg?branch=master)](https://travis-ci.org/Neilpang/acme.sh)
3 [![Join the chat at https://gitter.im/acme-sh/Lobby](https://badges.gitter.im/acme-sh/Lobby.svg)](https://gitter.im/acme-sh/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
4 - An ACME protocol client written purely in Shell (Unix shell) language.
5 - Full ACME protocol implementation.
6 - Support ACME v1 and ACME v2
7 - Support ACME v2 wildcard certs
8 - Simple, powerful and very easy to use. You only need 3 minutes to learn it.
9 - Bash, dash and sh compatible.
10 - Simplest shell script for Let's Encrypt free certificate client.
11 - Purely written in Shell with no dependencies on python or the official Let's Encrypt client.
12 - Just one script to issue, renew and install your certificates automatically.
13 - DOES NOT require `root/sudoer` access.
17 It's probably the `easiest & smartest` shell script to automatically issue & renew the free certificates from Let's Encrypt.
19 Wiki: https://github.com/Neilpang/acme.sh/wiki
21 For Docker Fans: [acme.sh :two_hearts: Docker ](https://github.com/Neilpang/acme.sh/wiki/Run-acme.sh-in-docker)
23 Twitter: [@neilpangxa](https://twitter.com/neilpangxa)
26 # [中文说明](https://github.com/Neilpang/acme.sh/wiki/%E8%AF%B4%E6%98%8E)
28 # Who are using **acme.sh**
29 - [FreeBSD.org](https://blog.crashed.org/letsencrypt-in-freebsd-org/)
30 - [ruby-china.org](https://ruby-china.org/topics/31983)
31 - [Proxmox](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer))
32 - [pfsense](https://github.com/pfsense/FreeBSD-ports/pull/89)
33 - [webfaction](https://community.webfaction.com/questions/19988/using-letsencrypt)
34 - [Loadbalancer.org](https://www.loadbalancer.org/blog/loadbalancer-org-with-lets-encrypt-quick-and-dirty)
35 - [discourse.org](https://meta.discourse.org/t/setting-up-lets-encrypt/40709)
36 - [Centminmod](http://centminmod.com/letsencrypt-acmetool-https.html)
37 - [splynx](https://forum.splynx.com/t/free-ssl-cert-for-splynx-lets-encrypt/297)
38 - [archlinux](https://aur.archlinux.org/packages/acme.sh-git/)
39 - [opnsense.org](https://github.com/opnsense/plugins/tree/master/security/acme-client/src/opnsense/scripts/OPNsense/AcmeClient)
40 - [more...](https://github.com/Neilpang/acme.sh/wiki/Blogs-and-tutorials)
44 | NO | Status| Platform|
45 |----|-------|---------|
46 |1|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/ubuntu-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)| Ubuntu
47 |2|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/debian-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)| Debian
48 |3|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/centos-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|CentOS
49 |4|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/windows-cygwin.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Windows (cygwin with curl, openssl and crontab included)
50 |5|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/freebsd.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|FreeBSD
51 |6|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/pfsense.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|pfsense
52 |7|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/opensuse-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|openSUSE
53 |8|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/alpine-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Alpine Linux (with curl)
54 |9|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/base-archlinux.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Archlinux
55 |10|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/fedora-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|fedora
56 |11|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/kalilinux-kali-linux-docker.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Kali Linux
57 |12|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/oraclelinux-latest.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Oracle Linux
58 |13|[![](https://cdn.rawgit.com/Neilpang/acmetest/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
59 |14|-----| Cloud Linux https://github.com/Neilpang/le/issues/111
60 |15|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/openbsd.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|OpenBSD
61 |16|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/mageia.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Mageia
62 |17|-----| OpenWRT: Tested and working. See [wiki page](https://github.com/Neilpang/acme.sh/wiki/How-to-run-on-OpenWRT)
63 |18|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/solaris.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|SunOS/Solaris
64 |19|[![](https://cdn.rawgit.com/Neilpang/acmetest/master/status/gentoo-stage3-amd64.svg)](https://github.com/Neilpang/letest#here-are-the-latest-status)|Gentoo Linux
65 |20|[![Build Status](https://travis-ci.org/Neilpang/acme.sh.svg?branch=master)](https://travis-ci.org/Neilpang/acme.sh)|Mac OSX
67 For all build statuses, check our [weekly build project](https://github.com/Neilpang/acmetest):
69 https://github.com/Neilpang/acmetest
79 - [Stateless mode](https://github.com/Neilpang/acme.sh/wiki/Stateless-Mode)
86 Check this project: https://github.com/Neilpang/get.acme.sh
89 curl https://get.acme.sh | sh
95 wget -O - https://get.acme.sh | sh
99 ### 2. Or, Install from git
101 Clone this project and launch installation:
104 git clone https://github.com/Neilpang/acme.sh.git
109 You `don't have to be root` then, although `it is recommended`.
111 Advanced Installation: https://github.com/Neilpang/acme.sh/wiki/How-to-install
113 The installer will perform 3 actions:
115 1. Create and copy `acme.sh` to your home dir (`$HOME`): `~/.acme.sh/`.
116 All certs will be placed in this folder too.
117 2. Create alias for: `acme.sh=~/.acme.sh/acme.sh`.
118 3. Create daily cron job to check and renew the certs if needed.
123 0 0 * * * "/home/user/.acme.sh"/acme.sh --cron --home "/home/user/.acme.sh" > /dev/null
126 After the installation, you must close the current terminal and reopen it to make the alias take effect.
128 Ok, you are ready to issue certs now.
133 root@v1:~# acme.sh -h
136 # 2. Just issue a cert
138 **Example 1:** Single domain.
141 acme.sh --issue -d example.com -w /home/wwwroot/example.com
147 acme.sh --issue -d example.com -w /home/username/public_html
153 acme.sh --issue -d example.com -w /var/www/html
156 **Example 2:** Multiple domains in the same cert.
159 acme.sh --issue -d example.com -d www.example.com -d cp.example.com -w /home/wwwroot/example.com
162 The parameter `/home/wwwroot/example.com` or `/home/username/public_html` or `/var/www/html` is the web root folder where you host your website files. You **MUST** have `write access` to this folder.
164 Second argument **"example.com"** is the main domain you want to issue the cert for.
165 You must have at least one domain there.
167 You must point and bind all the domains to the same webroot dir: `/home/wwwroot/example.com`.
169 Generated/issued certs will be placed in `~/.acme.sh/example.com/`
171 The issued cert will be renewed automatically every **60** days.
173 More examples: https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert
176 # 3. Install the issued cert to Apache/Nginx etc.
178 After you issue a cert, you probably want to install/copy the cert to your Apache/Nginx or other servers.
179 You **MUST** use this command to copy the certs to the target files, **DO NOT** use the certs files in **~/.acme.sh/** folder, they are for internal use only, the folder structure may change in the future.
183 acme.sh --install-cert -d example.com \
184 --cert-file /path/to/certfile/in/apache/cert.pem \
185 --key-file /path/to/keyfile/in/apache/key.pem \
186 --fullchain-file /path/to/fullchain/certfile/apache/fullchain.pem \
187 --reloadcmd "service apache2 force-reload"
192 acme.sh --install-cert -d example.com \
193 --key-file /path/to/keyfile/in/nginx/key.pem \
194 --fullchain-file /path/to/fullchain/nginx/cert.pem \
195 --reloadcmd "service nginx force-reload"
198 Only the domain is required, all the other parameters are optional.
200 The ownership and permission info of existing files are preserved. You may want to precreate the files to have defined ownership and permission.
202 Install/copy the issued cert/key to the production Apache or Nginx path.
204 The cert will be renewed every **60** days by default (which is configurable). Once the cert is renewed, the Apache/Nginx service will be reloaded automatically by the command: `service apache2 force-reload` or `service nginx force-reload`.
207 # 4. Use Standalone server to issue cert
209 **(requires you to be root/sudoer or have permission to listen on port 80 (TCP))**
211 Port `80` (TCP) **MUST** be free to listen on, otherwise you will be prompted to free it and try again.
214 acme.sh --issue --standalone -d example.com -d www.example.com -d cp.example.com
217 More examples: https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert
220 # 5. Use Standalone TLS server to issue cert
222 **(requires you to be root/sudoer or have permission to listen on port 443 (TCP))**
224 acme.sh supports `tls-sni-01` validation.
226 Port `443` (TCP) **MUST** be free to listen on, otherwise you will be prompted to free it and try again.
229 acme.sh --issue --tls -d example.com -d www.example.com -d cp.example.com
232 More examples: https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert
237 **(requires you to be root/sudoer, since it is required to interact with Apache server)**
239 If you are running a web server, Apache or Nginx, it is recommended to use the `Webroot mode`.
241 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.
243 Just set string "apache" as the second argument and it will force use of apache plugin automatically.
246 acme.sh --issue --apache -d example.com -d www.example.com -d cp.example.com
249 More examples: https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert
253 **(requires you to be root/sudoer, since it is required to interact with Nginx server)**
255 If you are running a web server, Apache or Nginx, it is recommended to use the `Webroot mode`.
257 Particularly, if you are running an nginx server, you can use nginx mode instead. This mode doesn't write any files to your web root folder.
259 Just set string "nginx" as the second argument.
261 It will configure nginx server automatically to verify the domain and then restore the nginx config to the original version.
263 So, the config is not changed.
266 acme.sh --issue --nginx -d example.com -d www.example.com -d cp.example.com
269 More examples: https://github.com/Neilpang/acme.sh/wiki/How-to-issue-a-cert
273 Support the `dns-01` challenge.
276 acme.sh --issue --dns -d example.com -d www.example.com -d cp.example.com
279 You should get an output like below:
282 Add the following txt record:
283 Domain:_acme-challenge.example.com
284 Txt value:9ihDbjYfTExAYeDs4DBUeuTo18KBzwvTEjUnSwd32-c
286 Add the following txt record:
287 Domain:_acme-challenge.www.example.com
288 Txt value:9ihDbjxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
290 Please add those txt records to the domains. Waiting for the dns to take effect.
293 Then just rerun with `renew` argument:
296 acme.sh --renew -d example.com
301 **Take care, this is dns manual mode, it can not be renewed automatically. you will have to add a new txt record to your domain by your hand when you renew your cert.**
303 **Please use dns api mode instead.**
305 # 9. Automatic DNS API integration
307 If your DNS provider supports API access, we can use that API to automatically issue the certs.
309 You don't have to do anything manually!
311 ### Currently acme.sh supports:
313 1. CloudFlare.com API
318 1. OVH, kimsufi, soyoustart and runabove API
321 1. DNSMadeEasy.com API
323 1. aliyun.com(阿里云) API
325 1. Alwaysdata.com API
327 1. FreeDNS (https://freedns.afraid.org/)
329 1. Domain-Offensive/Resellerinterface/Domainrobot API
332 1. DigitalOcean API (native)
334 1. Infoblox NIOS API (https://www.infoblox.com/)
335 1. VSCALE (https://vscale.io/)
336 1. Dynu API (https://www.dynu.com)
341 1. Dyn Managed DNS API
342 1. Yandex PDD API (https://pdd.yandex.ru)
343 1. Hurricane Electric DNS service (https://dns.he.net)
344 1. UnoEuro API (https://www.unoeuro.com/)
345 1. INWX (https://www.inwx.de/)
346 1. Servercow (https://servercow.de)
347 1. Namesilo (https://www.namesilo.com)
348 1. InternetX autoDNS API (https://internetx.com)
352 1. lexicon DNS API: https://github.com/Neilpang/acme.sh/wiki/How-to-use-lexicon-dns-api
353 (DigitalOcean, DNSimple, DNSMadeEasy, DNSPark, EasyDNS, Namesilo, NS1, PointHQ, Rage4 and Vultr etc.)
357 **More APIs coming soon...**
359 If your DNS provider is not on the supported list above, you can write your own DNS API script easily. If you do, please consider submitting a [Pull Request](https://github.com/Neilpang/acme.sh/pulls) and contribute it to the project.
361 For more details: [How to use DNS API](dnsapi)
364 # 10. Issue ECC certificates
366 `Let's Encrypt` can now issue **ECDSA** certificates.
368 And we support them too!
370 Just set the `length` parameter with a prefix `ec-`.
374 ### Single domain ECC certificate
377 acme.sh --issue -w /home/wwwroot/example.com -d example.com --keylength ec-256
380 ### SAN multi domain ECC certificate
383 acme.sh --issue -w /home/wwwroot/example.com -d example.com -d www.example.com --keylength ec-256
386 Please look at the last parameter above.
390 1. **ec-256 (prime256v1, "ECDSA P-256")**
391 2. **ec-384 (secp384r1, "ECDSA P-384")**
392 3. **ec-521 (secp521r1, "ECDSA P-521", which is not supported by Let's Encrypt yet.)**
395 # 11. How to renew the issued certs
397 No, you don't need to renew the certs manually. All the certs will be renewed automatically every **60** days.
399 However, you can also force to renew any cert:
402 acme.sh --renew -d example.com --force
408 acme.sh --renew -d example.com --force --ecc
412 # 12. How to upgrade `acme.sh`
414 acme.sh is in constant development, so it's strongly recommended to use the latest code.
416 You can update acme.sh to the latest code:
422 You can also enable auto upgrade:
425 acme.sh --upgrade --auto-upgrade
428 Then **acme.sh** will be kept up to date automatically.
430 Disable auto upgrade:
433 acme.sh --upgrade --auto-upgrade 0
437 # 13. Issue a cert from an existing CSR
439 https://github.com/Neilpang/acme.sh/wiki/Issue-a-cert-from-existing-CSR
444 Speak ACME language using shell, directly to "Let's Encrypt".
449 # 15. Acknowledgments
451 1. Acme-tiny: https://github.com/diafygi/acme-tiny
452 2. ACME protocol: https://github.com/ietf-wg-acme/acme
453 3. Certbot: https://github.com/certbot/certbot
456 # 16. License & Others
460 Please Star and Fork me.
462 [Issues](https://github.com/Neilpang/acme.sh/issues) and [pull requests](https://github.com/Neilpang/acme.sh/pulls) are welcome.
466 Your donation makes **acme.sh** better:
468 1. PayPal/Alipay(支付宝)/Wechat(微信): [https://donate.acme.sh/](https://donate.acme.sh/)
470 [Donate List](https://github.com/Neilpang/acme.sh/wiki/Donate-list)