{ "componentChunkName": "component---src-templates-issues-tsx", "path": "/issues/8", "result": {"data":{"issuesJson":{"id":"d715f0dc-879b-5946-93ce-5f93046bf0b8","title":"acmesh-official/acme.sh: 实现了 acme 协议，可以从 ZeroSSL，Let's Encrypt 等 CA 生成免费的证书。","number":8,"bodyHTML":"
\n



\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Reposacmesh-official/acme.sh
Views\"views\"
Stars\"stars\"
Forks\"forks\"
License\"license\"
UpdatedAt\"last-commit\"
CreatedAt\"create-at\"
\n\n

\"\"

\n\n
\n

An ACME Shell script: acme.sh

\n

\"FreeBSD\"
\n\"OpenBSD\"
\n\"NetBSD\"
\n\"MacOS\"
\n\"Ubuntu\"
\n\"Windows\"
\n\"Solaris\"
\n\"DragonFlyBSD\"
\n\"Omnios\"

\n

\"Shellcheck\"
\n\"PebbleStrict\"
\n\"DockerHub\"

\n


\n\"Join
\n\"Docker
\n\"Docker

\n\n

It's probably the easiest & smartest shell script to automatically issue & renew the free certificates.

\n

Wiki: https://github.com/acmesh-official/acme.sh/wiki

\n

For Docker Fans: acme.sh 💕 Docker

\n

Twitter: @neilpangxa

\n

中文说明

\n

Who:

\n\n

Tested OS

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NOStatusPlatform
1\"MacOS\"Mac OSX
2\"Windows\"Windows (cygwin with curl, openssl and crontab included)
3\"FreeBSD\"FreeBSD
4\"Solaris\"Solaris
5\"Ubuntu\"Ubuntu
6NApfsense
7\"OpenBSD\"OpenBSD
8\"NetBSD\"NetBSD
9\"DragonFlyBSD\"DragonFlyBSD
10\"Omnios\"Omnios
11\"Linux\"Debian
12\"Linux\"CentOS
13\"Linux\"openSUSE
14\"Linux\"Alpine Linux (with curl)
15\"Linux\"Archlinux
16\"Linux\"fedora
17\"Linux\"Kali Linux
18\"Linux\"Oracle Linux
19\"Linux\"Mageia
10\"Linux\"Gentoo Linux
11\"Linux\"ClearLinux
22-----Cloud Linux acmesh-official/acme.sh#111
23-----OpenWRT: Tested and working. See wiki page
24\"\"Proxmox: See Proxmox VE Wiki. Version 4.x, 5.0, 5.1, version 5.2 and up
\n

Check our testing project:

\n

https://github.com/acmesh-official/acmetest

\n

Supported CA

\n\n

Supported modes

\n\n

1. How to install

\n

1. Install online

\n

Check this project: https://github.com/acmesh-official/get.acme.sh

\n
curl https://get.acme.sh | sh -s email=my@example.com
\n

Or:

\n
wget -O -  https://get.acme.sh | sh -s email=my@example.com
\n

2. Or, Install from git

\n

Clone this project and launch installation:

\n
git clone https://github.com/acmesh-official/acme.sh.git\ncd ./acme.sh\n./acme.sh --install -m my@example.com
\n

You don't have to be root then, although it is recommended.

\n

Advanced Installation: https://github.com/acmesh-official/acme.sh/wiki/How-to-install

\n

The installer will perform 3 actions:

\n
    \n
  1. Create and copy acme.sh to your home dir ($HOME): ~/.acme.sh/.
    \nAll certs will be placed in this folder too.
    2. \n
  2. Create alias for: acme.sh=~/.acme.sh/acme.sh.
    3. \n
  3. Create daily cron job to check and renew the certs if needed.
    4. \n
\n

Cron entry example:

\n
0 0 * * * \"/home/user/.acme.sh\"/acme.sh --cron --home \"/home/user/.acme.sh\" > /dev/null
\n

After the installation, you must close the current terminal and reopen it to make the alias take effect.

\n

Ok, you are ready to issue certs now.

\n

Show help message:

\n
root@v1:~# acme.sh -h
\n

2. Just issue a cert

\n

Example 1: Single domain.

\n
acme.sh --issue -d example.com -w /home/wwwroot/example.com
\n

or:

\n
acme.sh --issue -d example.com -w /home/username/public_html
\n

or:

\n
acme.sh --issue -d example.com -w /var/www/html
\n

Example 2: Multiple domains in the same cert.

\n
acme.sh --issue -d example.com -d www.example.com -d cp.example.com -w /home/wwwroot/example.com
\n

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.

\n

Second argument \"example.com\" is the main domain you want to issue the cert for.
\nYou must have at least one domain there.

\n

You must point and bind all the domains to the same webroot dir: /home/wwwroot/example.com.

\n

The certs will be placed in ~/.acme.sh/example.com/

\n

The certs will be renewed automatically every 60 days.

\n

More examples: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert

\n

3. Install the cert to Apache/Nginx etc.

\n

After the cert is generated, you probably want to install/copy the cert to your Apache/Nginx or other servers.
\nYou 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.

\n

Apache example:

\n
acme.sh --install-cert -d example.com \\\n--cert-file      /path/to/certfile/in/apache/cert.pem  \\\n--key-file       /path/to/keyfile/in/apache/key.pem  \\\n--fullchain-file /path/to/fullchain/certfile/apache/fullchain.pem \\\n--reloadcmd     \"service apache2 force-reload\"
\n

Nginx example:

\n
acme.sh --install-cert -d example.com \\\n--key-file       /path/to/keyfile/in/nginx/key.pem  \\\n--fullchain-file /path/to/fullchain/nginx/cert.pem \\\n--reloadcmd     \"service nginx force-reload\"
\n

Only the domain is required, all the other parameters are optional.

\n

The ownership and permission info of existing files are preserved. You can pre-create the files to define the ownership and permission.

\n

Install/copy the cert/key to the production Apache or Nginx path.

\n

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.

\n

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.

\n

4. Use Standalone server to issue cert

\n

(requires you to be root/sudoer or have permission to listen on port 80 (TCP))

\n

Port 80 (TCP) MUST be free to listen on, otherwise you will be prompted to free it and try again.

\n
acme.sh --issue --standalone -d example.com -d www.example.com -d cp.example.com
\n

More examples: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert

\n

5. Use Standalone ssl server to issue cert

\n

(requires you to be root/sudoer or have permission to listen on port 443 (TCP))

\n

Port 443 (TCP) MUST be free to listen on, otherwise you will be prompted to free it and try again.

\n
acme.sh --issue --alpn -d example.com -d www.example.com -d cp.example.com
\n

More examples: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert

\n

6. Use Apache mode

\n

(requires you to be root/sudoer, since it is required to interact with Apache server)

\n

If you are running a web server, it is recommended to use the Webroot mode.

\n

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.

\n

Just set string \"apache\" as the second argument and it will force use of apache plugin automatically.

\n
acme.sh --issue --apache -d example.com -d www.example.com -d cp.example.com
\n

This apache mode is only to issue the cert, it will not change your apache config files.
\nYou will need to configure your website config files to use the cert by yourself.
\nWe don't want to mess with your apache server, don't worry.

\n

More examples: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert

\n

7. Use Nginx mode

\n

(requires you to be root/sudoer, since it is required to interact with Nginx server)

\n

If you are running a web server, it is recommended to use the Webroot mode.

\n

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.

\n

Just set string \"nginx\" as the second argument.

\n

It will configure nginx server automatically to verify the domain and then restore the nginx config to the original version.

\n

So, the config is not changed.

\n
acme.sh --issue --nginx -d example.com -d www.example.com -d cp.example.com
\n

This nginx mode is only to issue the cert, it will not change your nginx config files.
\nYou will need to configure your website config files to use the cert by yourself.
\nWe don't want to mess with your nginx server, don't worry.

\n

More examples: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert

\n

8. Automatic DNS API integration

\n

If your DNS provider supports API access, we can use that API to automatically issue the certs.

\n

You don't have to do anything manually!

\n

Currently acme.sh supports most of the dns providers:

\n

https://github.com/acmesh-official/acme.sh/wiki/dnsapi

\n

9. Use DNS manual mode:

\n

See: https://github.com/acmesh-official/acme.sh/wiki/dns-manual-mode first.

\n

If your dns provider doesn't support any api access, you can add the txt record by hand.

\n
acme.sh --issue --dns -d example.com -d www.example.com -d cp.example.com
\n

You should get an output like below:

\n
Add the following txt record:\nDomain:_acme-challenge.example.com\nTxt value:9ihDbjYfTExAYeDs4DBUeuTo18KBzwvTEjUnSwd32-c\n\nAdd the following txt record:\nDomain:_acme-challenge.www.example.com\nTxt value:9ihDbjxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\n\nPlease add those txt records to the domains. Waiting for the dns to take effect.
\n

Then just rerun with renew argument:

\n
acme.sh --renew -d example.com
\n

Ok, it's done.

\n

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.

\n

Please use dns api mode instead.

\n

10. Issue ECC certificates

\n

Just set the keylength parameter with a prefix ec-.

\n

For example:

\n

Single domain ECC certificate

\n
acme.sh --issue -w /home/wwwroot/example.com -d example.com --keylength ec-256
\n

SAN multi domain ECC certificate

\n
acme.sh --issue -w /home/wwwroot/example.com -d example.com -d www.example.com --keylength ec-256
\n

Please look at the keylength parameter above.

\n

Valid values are:

\n
    \n
  1. ec-256 (prime256v1, \"ECDSA P-256\", which is the default key type)
    2. \n
  2. ec-384 (secp384r1, \"ECDSA P-384\")
    3. \n
  3. ec-521 (secp521r1, \"ECDSA P-521\", which is not supported by Let's Encrypt yet.)
    4. \n
  4. 2048 (RSA2048)
    5. \n
  5. 3072 (RSA3072)
    6. \n
  6. 4096 (RSA4096)
    7. \n
\n

11. Issue Wildcard certificates

\n

It's simple, just give a wildcard domain as the -d parameter.

\n
acme.sh  --issue -d example.com  -d '*.example.com'  --dns dns_cf
\n

12. How to renew the certs

\n

No, you don't need to renew the certs manually. All the certs will be renewed automatically every 60 days.

\n

However, you can also force to renew a cert:

\n
acme.sh --renew -d example.com --force
\n

or, for ECC cert:

\n
acme.sh --renew -d example.com --force --ecc
\n

13. How to stop cert renewal

\n

To stop renewal of a cert, you can execute the following to remove the cert from the renewal list:

\n
acme.sh --remove -d example.com [--ecc]
\n

The cert/key file is not removed from the disk.

\n

You can remove the respective directory (e.g. ~/.acme.sh/example.com) by yourself.

\n

14. How to upgrade acme.sh

\n

acme.sh is in constant development, so it's strongly recommended to use the latest code.

\n

You can update acme.sh to the latest code:

\n
acme.sh --upgrade
\n

You can also enable auto upgrade:

\n
acme.sh --upgrade --auto-upgrade
\n

Then acme.sh will be kept up to date automatically.

\n

Disable auto upgrade:

\n
acme.sh --upgrade --auto-upgrade 0
\n

15. Issue a cert from an existing CSR

\n

https://github.com/acmesh-official/acme.sh/wiki/Issue-a-cert-from-existing-CSR

\n

16. Send notifications in cronjob

\n

https://github.com/acmesh-official/acme.sh/wiki/notify

\n

17. Under the Hood

\n

Speak ACME language using shell, directly to \"Let's Encrypt\".

\n

TODO:

\n

18. Acknowledgments

\n
    \n
  1. Acme-tiny: https://github.com/diafygi/acme-tiny
    2. \n
  2. ACME protocol: https://github.com/ietf-wg-acme/acme
    3. \n
\n

Contributors

\n

Code Contributors

\n

This project exists thanks to all the people who contribute.
\n

\n

Financial Contributors

\n

Become a financial contributor and help us sustain our community. [Contribute]

\n

Individuals

\n

\n

Organizations

\n

Support this project with your organization. Your logo will show up here with a link to your website. [Contribute]

\n


\n
\n
\n
\n
\n
\n
\n
\n
\n

\n

19. License & Others

\n

License is GPLv3

\n

Please Star and Fork me.

\n

Issues and pull requests are welcome.

\n

20. Donate

\n

Your donation makes acme.sh better:

\n
    \n
  1. PayPal/Alipay(支付宝)/Wechat(微信): https://donate.acme.sh/
    2. \n
\n

Donate List

","updatedAt":"2025-05-21T15:47:36Z","upvoteCount":null,"author":{"login":"eryajf","avatarUrl":"https://avatars.githubusercontent.com/u/33259379?u=e4a4090a38ac2473aaed4ef9945233636776c6c3&v=4","url":"https://github.com/eryajf"},"category":null,"labels":{"edges":[{"node":{"name":"更多","color":"25B472"}},{"node":{"name":"证书管理","color":"34a405"}},{"node":{"name":"acmesh-official","color":"5d8693"}}]},"comments":{"edges":[]}}},"pageContext":{"number":8,"previous":{"title":"beyondgrep/ack3: ack 是一个代码搜索工具，类似于 grep，但针对搜索大型源代码树的程序员进行了优化。","number":7},"next":{"title":"nektos/act: 本地运行 GitHub Actions","number":9}}}, "staticQueryHashes": ["151096407","2861350382"]}