You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

512 lines
20 KiB

4 years ago
4 years ago
8 years ago
4 years ago
4 years ago
4 years ago
9 years ago
8 years ago
9 years ago
9 years ago
9 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
7 years ago
9 years ago
4 years ago
3 years ago
4 years ago
3 years ago
4 years ago
3 years ago
9 years ago
3 years ago
9 years ago
9 years ago
3 years ago
7 years ago
8 years ago
9 years ago
9 years ago
4 years ago
9 years ago
4 years ago
9 years ago
4 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
7 years ago
9 years ago
9 years ago
9 years ago
9 years ago
8 years ago
9 years ago
9 years ago
8 years ago
9 years ago
9 years ago
9 years ago
7 years ago
9 years ago
7 years ago
9 years ago
7 years ago
7 years ago
8 years ago
8 years ago
8 years ago
8 years ago
9 years ago
7 years ago
7 years ago
8 years ago
9 years ago
7 years ago
8 years ago
9 years ago
5 years ago
7 years ago
7 years ago
7 years ago
7 years ago
5 years ago
7 years ago
7 years ago
7 years ago
9 years ago
6 years ago
7 years ago
7 years ago
7 years ago
7 years ago
7 years ago
8 years ago
8 years ago
7 years ago
8 years ago
7 years ago
7 years ago
8 years ago
7 years ago
7 years ago
8 years ago
7 years ago
8 years ago
7 years ago
7 years ago
7 years ago
7 years ago
7 years ago
8 years ago
8 years ago
7 years ago
8 years ago
7 years ago
7 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
9 years ago
8 years ago
9 years ago
8 years ago
  1. # An ACME Shell script: acme.sh
  2. ![LetsEncrypt](https://github.com/acmesh-official/acme.sh/workflows/LetsEncrypt/badge.svg)
  3. ![Shellcheck](https://github.com/acmesh-official/acme.sh/workflows/Shellcheck/badge.svg)
  4. ![PebbleStrict](https://github.com/acmesh-official/acme.sh/workflows/PebbleStrict/badge.svg)
  5. ![DockerHub](https://github.com/acmesh-official/acme.sh/workflows/Build%20DockerHub/badge.svg)
  6. <a href="https://opencollective.com/acmesh" alt="Financial Contributors on Open Collective"><img src="https://opencollective.com/acmesh/all/badge.svg?label=financial+contributors" /></a>
  7. [![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)
  8. [![Docker stars](https://img.shields.io/docker/stars/neilpang/acme.sh.svg)](https://hub.docker.com/r/neilpang/acme.sh "Click to view the image on Docker Hub")
  9. [![Docker pulls](https://img.shields.io/docker/pulls/neilpang/acme.sh.svg)](https://hub.docker.com/r/neilpang/acme.sh "Click to view the image on Docker Hub")
  10. - An ACME protocol client written purely in Shell (Unix shell) language.
  11. - Full ACME protocol implementation.
  12. - Support ACME v1 and ACME v2
  13. - Support ACME v2 wildcard certs
  14. - Simple, powerful and very easy to use. You only need 3 minutes to learn it.
  15. - Bash, dash and sh compatible.
  16. - Purely written in Shell with no dependencies on python or the official Let's Encrypt client.
  17. - Just one script to issue, renew and install your certificates automatically.
  18. - DOES NOT require `root/sudoer` access.
  19. - Docker friendly
  20. - IPv6 support
  21. - Cron job notifications for renewal or error etc.
  22. It's probably the `easiest & smartest` shell script to automatically issue & renew the free certificates from Let's Encrypt.
  23. Wiki: https://github.com/acmesh-official/acme.sh/wiki
  24. For Docker Fans: [acme.sh :two_hearts: Docker ](https://github.com/acmesh-official/acme.sh/wiki/Run-acme.sh-in-docker)
  25. Twitter: [@neilpangxa](https://twitter.com/neilpangxa)
  26. # [中文说明](https://github.com/acmesh-official/acme.sh/wiki/%E8%AF%B4%E6%98%8E)
  27. # Who:
  28. - [FreeBSD.org](https://blog.crashed.org/letsencrypt-in-freebsd-org/)
  29. - [ruby-china.org](https://ruby-china.org/topics/31983)
  30. - [Proxmox](https://pve.proxmox.com/wiki/Certificate_Management)
  31. - [pfsense](https://github.com/pfsense/FreeBSD-ports/pull/89)
  32. - [webfaction](https://community.webfaction.com/questions/19988/using-letsencrypt)
  33. - [Loadbalancer.org](https://www.loadbalancer.org/blog/loadbalancer-org-with-lets-encrypt-quick-and-dirty)
  34. - [discourse.org](https://meta.discourse.org/t/setting-up-lets-encrypt/40709)
  35. - [Centminmod](https://centminmod.com/letsencrypt-acmetool-https.html)
  36. - [splynx](https://forum.splynx.com/t/free-ssl-cert-for-splynx-lets-encrypt/297)
  37. - [archlinux](https://www.archlinux.org/packages/community/any/acme.sh)
  38. - [opnsense.org](https://github.com/opnsense/plugins/tree/master/security/acme-client/src/opnsense/scripts/OPNsense/AcmeClient)
  39. - [CentOS Web Panel](http://centos-webpanel.com/)
  40. - [lnmp.org](https://lnmp.org/)
  41. - [more...](https://github.com/acmesh-official/acme.sh/wiki/Blogs-and-tutorials)
  42. # Tested OS
  43. | NO | Status| Platform|
  44. |----|-------|---------|
  45. |1|[![MacOS](https://github.com/acmesh-official/acme.sh/workflows/LetsEncrypt/badge.svg)](https://github.com/acmesh-official/acme.sh/actions?query=workflow%3ALetsEncrypt)|Mac OSX
  46. |2|[![Windows](https://github.com/acmesh-official/acme.sh/workflows/LetsEncrypt/badge.svg)](https://github.com/acmesh-official/acme.sh/actions?query=workflow%3ALetsEncrypt)|Windows (cygwin with curl, openssl and crontab included)
  47. |3|[![FreeBSD](https://github.com/acmesh-official/acme.sh/workflows/LetsEncrypt/badge.svg)](https://github.com/acmesh-official/acme.sh/actions?query=workflow%3ALetsEncrypt)|FreeBSD
  48. |4|[![Solaris](https://github.com/acmesh-official/acme.sh/workflows/LetsEncrypt/badge.svg)](https://github.com/acmesh-official/acme.sh/actions?query=workflow%3ALetsEncrypt)|Solaris
  49. |5|[![Ubuntu](https://github.com/acmesh-official/acme.sh/workflows/LetsEncrypt/badge.svg)](https://github.com/acmesh-official/acme.sh/actions?query=workflow%3ALetsEncrypt)| Ubuntu
  50. |6|NA|pfsense
  51. |7|NA|OpenBSD
  52. |8|[![Linux](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml/badge.svg)](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml)| Debian
  53. |9|[![Linux](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml/badge.svg)](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml)|CentOS
  54. |10|[![Linux](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml/badge.svg)](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml)|openSUSE
  55. |11|[![Linux](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml/badge.svg)](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml)|Alpine Linux (with curl)
  56. |12|[![Linux](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml/badge.svg)](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml)|Archlinux
  57. |13|[![Linux](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml/badge.svg)](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml)|fedora
  58. |14|[![Linux](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml/badge.svg)](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml)|Kali Linux
  59. |15|[![Linux](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml/badge.svg)](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml)|Oracle Linux
  60. |16|[![](https://acmesh-official.github.io/acmetest/status/proxmox.svg)](https://github.com/acmesh-official/letest#here-are-the-latest-status)| Proxmox: See Proxmox VE Wiki. Version [4.x, 5.0, 5.1](https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x,_5.0_and_5.1)#Let.27s_Encrypt_using_acme.sh), version [5.2 and up](https://pve.proxmox.com/wiki/Certificate_Management)
  61. |17|-----| Cloud Linux https://github.com/acmesh-official/acme.sh/issues/111
  62. |18|[![Linux](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml/badge.svg)](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml)|Mageia
  63. |19|-----| OpenWRT: Tested and working. See [wiki page](https://github.com/acmesh-official/acme.sh/wiki/How-to-run-on-OpenWRT)
  64. |20|[![Linux](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml/badge.svg)](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml)|Gentoo Linux
  65. |21|[![Linux](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml/badge.svg)](https://github.com/acmesh-official/acme.sh/actions/workflows/Linux.yml)|ClearLinux
  66. Check our [testing project](https://github.com/acmesh-official/acmetest):
  67. https://github.com/acmesh-official/acmetest
  68. # Supported CA
  69. - [ZeroSSL.com CA](https://github.com/acmesh-official/acme.sh/wiki/ZeroSSL.com-CA)(default)
  70. - Letsencrypt.org CA
  71. - [BuyPass.com CA](https://github.com/acmesh-official/acme.sh/wiki/BuyPass.com-CA)
  72. - [Pebble strict Mode](https://github.com/letsencrypt/pebble)
  73. - Any other [RFC8555](https://tools.ietf.org/html/rfc8555)-compliant CA
  74. # Supported modes
  75. - Webroot mode
  76. - Standalone mode
  77. - Standalone tls-alpn mode
  78. - Apache mode
  79. - Nginx mode
  80. - DNS mode
  81. - [DNS alias mode](https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mode)
  82. - [Stateless mode](https://github.com/acmesh-official/acme.sh/wiki/Stateless-Mode)
  83. # 1. How to install
  84. ### 1. Install online
  85. Check this project: https://github.com/acmesh-official/get.acme.sh
  86. ```bash
  87. curl https://get.acme.sh | sh -s email=my@example.com
  88. ```
  89. Or:
  90. ```bash
  91. wget -O - https://get.acme.sh | sh -s email=my@example.com
  92. ```
  93. ### 2. Or, Install from git
  94. Clone this project and launch installation:
  95. ```bash
  96. git clone https://github.com/acmesh-official/acme.sh.git
  97. cd ./acme.sh
  98. ./acme.sh --install -m my@example.com
  99. ```
  100. You `don't have to be root` then, although `it is recommended`.
  101. Advanced Installation: https://github.com/acmesh-official/acme.sh/wiki/How-to-install
  102. The installer will perform 3 actions:
  103. 1. Create and copy `acme.sh` to your home dir (`$HOME`): `~/.acme.sh/`.
  104. All certs will be placed in this folder too.
  105. 2. Create alias for: `acme.sh=~/.acme.sh/acme.sh`.
  106. 3. Create daily cron job to check and renew the certs if needed.
  107. Cron entry example:
  108. ```bash
  109. 0 0 * * * "/home/user/.acme.sh"/acme.sh --cron --home "/home/user/.acme.sh" > /dev/null
  110. ```
  111. After the installation, you must close the current terminal and reopen it to make the alias take effect.
  112. Ok, you are ready to issue certs now.
  113. Show help message:
  114. ```sh
  115. root@v1:~# acme.sh -h
  116. ```
  117. # 2. Just issue a cert
  118. **Example 1:** Single domain.
  119. ```bash
  120. acme.sh --issue -d example.com -w /home/wwwroot/example.com
  121. ```
  122. or:
  123. ```bash
  124. acme.sh --issue -d example.com -w /home/username/public_html
  125. ```
  126. or:
  127. ```bash
  128. acme.sh --issue -d example.com -w /var/www/html
  129. ```
  130. **Example 2:** Multiple domains in the same cert.
  131. ```bash
  132. acme.sh --issue -d example.com -d www.example.com -d cp.example.com -w /home/wwwroot/example.com
  133. ```
  134. 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.
  135. Second argument **"example.com"** is the main domain you want to issue the cert for.
  136. You must have at least one domain there.
  137. You must point and bind all the domains to the same webroot dir: `/home/wwwroot/example.com`.
  138. The certs will be placed in `~/.acme.sh/example.com/`
  139. The certs will be renewed automatically every **60** days.
  140. More examples: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert
  141. # 3. Install the cert to Apache/Nginx etc.
  142. After the cert is generated, you probably want to install/copy the cert to your Apache/Nginx or other servers.
  143. 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.
  144. **Apache** example:
  145. ```bash
  146. acme.sh --install-cert -d example.com \
  147. --cert-file /path/to/certfile/in/apache/cert.pem \
  148. --key-file /path/to/keyfile/in/apache/key.pem \
  149. --fullchain-file /path/to/fullchain/certfile/apache/fullchain.pem \
  150. --reloadcmd "service apache2 force-reload"
  151. ```
  152. **Nginx** example:
  153. ```bash
  154. acme.sh --install-cert -d example.com \
  155. --key-file /path/to/keyfile/in/nginx/key.pem \
  156. --fullchain-file /path/to/fullchain/nginx/cert.pem \
  157. --reloadcmd "service nginx force-reload"
  158. ```
  159. Only the domain is required, all the other parameters are optional.
  160. The ownership and permission info of existing files are preserved. You can pre-create the files to define the ownership and permission.
  161. Install/copy the cert/key to the production Apache or Nginx path.
  162. 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`.
  163. **Please take care: The reloadcmd is very important. The cert can be automatically renewed, but, without a correct 'reloadcmd' the cert may not be flushed to your server(like nginx or apache), then your website will not be able to show renewed cert in 60 days.**
  164. # 4. Use Standalone server to issue cert
  165. **(requires you to be root/sudoer or have permission to listen on port 80 (TCP))**
  166. Port `80` (TCP) **MUST** be free to listen on, otherwise you will be prompted to free it and try again.
  167. ```bash
  168. acme.sh --issue --standalone -d example.com -d www.example.com -d cp.example.com
  169. ```
  170. More examples: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert
  171. # 5. Use Standalone ssl server to issue cert
  172. **(requires you to be root/sudoer or have permission to listen on port 443 (TCP))**
  173. Port `443` (TCP) **MUST** be free to listen on, otherwise you will be prompted to free it and try again.
  174. ```bash
  175. acme.sh --issue --alpn -d example.com -d www.example.com -d cp.example.com
  176. ```
  177. More examples: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert
  178. # 6. Use Apache mode
  179. **(requires you to be root/sudoer, since it is required to interact with Apache server)**
  180. If you are running a web server, it is recommended to use the `Webroot mode`.
  181. Particularly, if you are running an Apache server, you can use Apache mode instead. This mode doesn't write any files to your web root folder.
  182. Just set string "apache" as the second argument and it will force use of apache plugin automatically.
  183. ```sh
  184. acme.sh --issue --apache -d example.com -d www.example.com -d cp.example.com
  185. ```
  186. **This apache mode is only to issue the cert, it will not change your apache config files.
  187. You will need to configure your website config files to use the cert by yourself.
  188. We don't want to mess with your apache server, don't worry.**
  189. More examples: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert
  190. # 7. Use Nginx mode
  191. **(requires you to be root/sudoer, since it is required to interact with Nginx server)**
  192. If you are running a web server, it is recommended to use the `Webroot mode`.
  193. 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.
  194. Just set string "nginx" as the second argument.
  195. It will configure nginx server automatically to verify the domain and then restore the nginx config to the original version.
  196. So, the config is not changed.
  197. ```sh
  198. acme.sh --issue --nginx -d example.com -d www.example.com -d cp.example.com
  199. ```
  200. **This nginx mode is only to issue the cert, it will not change your nginx config files.
  201. You will need to configure your website config files to use the cert by yourself.
  202. We don't want to mess with your nginx server, don't worry.**
  203. More examples: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert
  204. # 8. Automatic DNS API integration
  205. If your DNS provider supports API access, we can use that API to automatically issue the certs.
  206. You don't have to do anything manually!
  207. ### Currently acme.sh supports most of the dns providers:
  208. https://github.com/acmesh-official/acme.sh/wiki/dnsapi
  209. # 9. Use DNS manual mode:
  210. See: https://github.com/acmesh-official/acme.sh/wiki/dns-manual-mode first.
  211. If your dns provider doesn't support any api access, you can add the txt record by hand.
  212. ```bash
  213. acme.sh --issue --dns -d example.com -d www.example.com -d cp.example.com
  214. ```
  215. You should get an output like below:
  216. ```sh
  217. Add the following txt record:
  218. Domain:_acme-challenge.example.com
  219. Txt value:9ihDbjYfTExAYeDs4DBUeuTo18KBzwvTEjUnSwd32-c
  220. Add the following txt record:
  221. Domain:_acme-challenge.www.example.com
  222. Txt value:9ihDbjxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  223. Please add those txt records to the domains. Waiting for the dns to take effect.
  224. ```
  225. Then just rerun with `renew` argument:
  226. ```bash
  227. acme.sh --renew -d example.com
  228. ```
  229. Ok, it's done.
  230. **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.**
  231. **Please use dns api mode instead.**
  232. # 10. Issue ECC certificates
  233. `Let's Encrypt` can now issue **ECDSA** certificates.
  234. And we support them too!
  235. Just set the `keylength` parameter with a prefix `ec-`.
  236. For example:
  237. ### Single domain ECC certificate
  238. ```bash
  239. acme.sh --issue -w /home/wwwroot/example.com -d example.com --keylength ec-256
  240. ```
  241. ### SAN multi domain ECC certificate
  242. ```bash
  243. acme.sh --issue -w /home/wwwroot/example.com -d example.com -d www.example.com --keylength ec-256
  244. ```
  245. Please look at the `keylength` parameter above.
  246. Valid values are:
  247. 1. **ec-256 (prime256v1, "ECDSA P-256")**
  248. 2. **ec-384 (secp384r1, "ECDSA P-384")**
  249. 3. **ec-521 (secp521r1, "ECDSA P-521", which is not supported by Let's Encrypt yet.)**
  250. # 11. Issue Wildcard certificates
  251. It's simple, just give a wildcard domain as the `-d` parameter.
  252. ```sh
  253. acme.sh --issue -d example.com -d '*.example.com' --dns dns_cf
  254. ```
  255. # 12. How to renew the certs
  256. No, you don't need to renew the certs manually. All the certs will be renewed automatically every **60** days.
  257. However, you can also force to renew a cert:
  258. ```sh
  259. acme.sh --renew -d example.com --force
  260. ```
  261. or, for ECC cert:
  262. ```sh
  263. acme.sh --renew -d example.com --force --ecc
  264. ```
  265. # 13. How to stop cert renewal
  266. To stop renewal of a cert, you can execute the following to remove the cert from the renewal list:
  267. ```sh
  268. acme.sh --remove -d example.com [--ecc]
  269. ```
  270. The cert/key file is not removed from the disk.
  271. You can remove the respective directory (e.g. `~/.acme.sh/example.com`) by yourself.
  272. # 14. How to upgrade `acme.sh`
  273. acme.sh is in constant development, so it's strongly recommended to use the latest code.
  274. You can update acme.sh to the latest code:
  275. ```sh
  276. acme.sh --upgrade
  277. ```
  278. You can also enable auto upgrade:
  279. ```sh
  280. acme.sh --upgrade --auto-upgrade
  281. ```
  282. Then **acme.sh** will be kept up to date automatically.
  283. Disable auto upgrade:
  284. ```sh
  285. acme.sh --upgrade --auto-upgrade 0
  286. ```
  287. # 15. Issue a cert from an existing CSR
  288. https://github.com/acmesh-official/acme.sh/wiki/Issue-a-cert-from-existing-CSR
  289. # 16. Send notifications in cronjob
  290. https://github.com/acmesh-official/acme.sh/wiki/notify
  291. # 17. Under the Hood
  292. Speak ACME language using shell, directly to "Let's Encrypt".
  293. TODO:
  294. # 18. Acknowledgments
  295. 1. Acme-tiny: https://github.com/diafygi/acme-tiny
  296. 2. ACME protocol: https://github.com/ietf-wg-acme/acme
  297. ## Contributors
  298. ### Code Contributors
  299. This project exists thanks to all the people who contribute.
  300. <a href="https://github.com/acmesh-official/acme.sh/graphs/contributors"><img src="https://opencollective.com/acmesh/contributors.svg?width=890&button=false" /></a>
  301. ### Financial Contributors
  302. Become a financial contributor and help us sustain our community. [[Contribute](https://opencollective.com/acmesh/contribute)]
  303. #### Individuals
  304. <a href="https://opencollective.com/acmesh"><img src="https://opencollective.com/acmesh/individuals.svg?width=890"></a>
  305. #### Organizations
  306. Support this project with your organization. Your logo will show up here with a link to your website. [[Contribute](https://opencollective.com/acmesh/contribute)]
  307. <a href="https://opencollective.com/acmesh/organization/0/website"><img src="https://opencollective.com/acmesh/organization/0/avatar.svg"></a>
  308. <a href="https://opencollective.com/acmesh/organization/1/website"><img src="https://opencollective.com/acmesh/organization/1/avatar.svg"></a>
  309. <a href="https://opencollective.com/acmesh/organization/2/website"><img src="https://opencollective.com/acmesh/organization/2/avatar.svg"></a>
  310. <a href="https://opencollective.com/acmesh/organization/3/website"><img src="https://opencollective.com/acmesh/organization/3/avatar.svg"></a>
  311. <a href="https://opencollective.com/acmesh/organization/4/website"><img src="https://opencollective.com/acmesh/organization/4/avatar.svg"></a>
  312. <a href="https://opencollective.com/acmesh/organization/5/website"><img src="https://opencollective.com/acmesh/organization/5/avatar.svg"></a>
  313. <a href="https://opencollective.com/acmesh/organization/6/website"><img src="https://opencollective.com/acmesh/organization/6/avatar.svg"></a>
  314. <a href="https://opencollective.com/acmesh/organization/7/website"><img src="https://opencollective.com/acmesh/organization/7/avatar.svg"></a>
  315. <a href="https://opencollective.com/acmesh/organization/8/website"><img src="https://opencollective.com/acmesh/organization/8/avatar.svg"></a>
  316. <a href="https://opencollective.com/acmesh/organization/9/website"><img src="https://opencollective.com/acmesh/organization/9/avatar.svg"></a>
  317. # 19. License & Others
  318. License is GPLv3
  319. Please Star and Fork me.
  320. [Issues](https://github.com/acmesh-official/acme.sh/issues) and [pull requests](https://github.com/acmesh-official/acme.sh/pulls) are welcome.
  321. # 20. Donate
  322. Your donation makes **acme.sh** better:
  323. 1. PayPal/Alipay(支付宝)/Wechat(微信): [https://donate.acme.sh/](https://donate.acme.sh/)
  324. [Donate List](https://github.com/acmesh-official/acme.sh/wiki/Donate-list)