Watch 1 Star 0 Fork 2

冷焰心 / acme.shShell

forked from Neilpang / 
Sign up for free
Explore and code with more than 2 million developers,Free private repositories !:)
Sign up
An ACME Shell script, a certbot client: spread retract

Clone or download
Notice: Creating folder will generate an empty file .keep, because not support in Git

An ACME Shell script: Build Status

  • An ACME protocol client written purely in Shell (Unix shell) language.
  • Full ACME protocol implementation.
  • Simple, powerful and very easy to use. You only need 3 minutes to learn it.
  • Bash, dash and sh compatible.
  • Simplest shell script for Let's Encrypt free certificate client.
  • Purely written in Shell with no dependencies on python or the official Let's Encrypt client.
  • Just one script to issue, renew and install your certificates automatically.
  • DOES NOT require root/sudoer access.

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


Twitter: @neilpangxa


Tested OS

NO Status Platform
1 Ubuntu
2 Debian
3 CentOS
4 Windows (cygwin with curl, openssl and crontab included)
5 FreeBSD
6 pfsense
7 openSUSE
8 Alpine Linux (with curl)
9 Archlinux
10 fedora
11 Kali Linux
12 Oracle Linux
13 Proxmox
14 ----- Cloud Linux
15 OpenBSD
16 Mageia
17 ----- OpenWRT: Tested and working. See wiki page
18 SunOS/Solaris
19 Gentoo Linux
20 Build Status Mac OSX

For all build statuses, check our daily build project:

Supported modes

  • Webroot mode
  • Standalone mode
  • Apache mode
  • DNS mode

1. How to install

1. Install online

Check this project:

curl | sh


wget -O - | sh

2. Or, Install from git

Clone this project and launch installation:

git clone
cd ./
./ --install

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

Advanced Installation:

The installer will perform 3 actions:

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

Cron entry example:

0 0 * * * "/home/user/"/ --cron --home "/home/user/" > /dev/null

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

Ok, you are ready to issue certs now.

Show help message:

root@v1:~# -h

2. Just issue a cert

Example 1: Single domain. --issue -d -w /home/wwwroot/

Example 2: Multiple domains in the same cert. --issue -d -d -d -w /home/wwwroot/

The parameter /home/wwwroot/ is the web root folder. You MUST have write access to this folder.

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

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

Generated/issued certs will be placed in ~/

The issued cert will be renewed automatically every 60 days.

More examples:

3. Install the issued cert to Apache/Nginx etc.

After you issue a cert, you probably want to install/copy the cert to your Apache/Nginx or other servers. You MUST use this command to copy the certs to the target files, DO NOT use the certs files in ~/ folder, they are for internal use only, the folder structure may change in the future.

Apache example: --installcert -d \
--certpath      /path/to/certfile/in/apache/cert.pem  \
--keypath       /path/to/keyfile/in/apache/key.pem  \
--fullchainpath /path/to/fullchain/certfile/apache/fullchain.pem \
--reloadcmd     "service apache2 force-reload"

Nginx example: --installcert -d \
--keypath       /path/to/keyfile/in/nginx/key.pem  \
--fullchainpath /path/to/fullchain/nginx/cert.pem \
--reloadcmd     "service nginx force-reload"

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

The ownership and permission info of existing files are preserved. You may want to precreate the files to have defined ownership and permission.

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

The cert will be renewed every **60** days by default (which is configurable). Once the cert is renewed, the Apache/Nginx service will be restarted automatically by the command: service apache2 restart or service nginx restart.

4. Use Standalone server to issue cert

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

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

More examples:

5. Use Standalone TLS server to issue cert

(requires you to be root/sudoer or have permission to listen on port 443 (TCP)) supports tls-sni-01 validation.

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

More examples:

6. Use Apache mode

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

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

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.

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

More examples:

7. Use DNS mode:

Support the dns-01 challenge. --issue --dns -d -d -d

You should get an output like below:

Add the following txt record:
Txt value:9ihDbjYfTExAYeDs4DBUeuTo18KBzwvTEjUnSwd32-c

Add the following txt record:
Txt value:9ihDbjxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Please add those txt records to the domains. Waiting for the dns to take effect.

Then just rerun with renew argument: --renew -d

Ok, it's finished.

8. Automatic DNS API integration

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

You don't have to do anything manually!

Currently supports:

  1. API
  2. API
  3. API
  4. API
  5. OVH, kimsufi, soyoustart and runabove API
  6. AWS Route 53
  7. API
  8. lexicon DNS API: (DigitalOcean, DNSimple, DNSMadeEasy, DNSPark, EasyDNS, Namesilo, NS1, PointHQ, Rage4 and Vultr etc.)
  9. API
  10. API
  11. nsupdate API
  12.阿里云) API
  13. ISPConfig 3.1 API
  14. API
  15. API

More APIs coming soon...

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 and contribute it to the project.

For more details: How to use DNS API

9. Issue ECC certificates

Let's Encrypt can now issue ECDSA certificates.

And we support them too!

Just set the length parameter with a prefix ec-.

For example:

Single domain ECC cerfiticate --issue -w /home/wwwroot/ -d --keylength ec-256

SAN multi domain ECC certificate --issue -w /home/wwwroot/ -d -d --keylength ec-256

Please look at the last parameter above.

Valid values are:

  1. ec-256 (prime256v1, "ECDSA P-256")
  2. ec-384 (secp384r1, "ECDSA P-384")
  3. ec-521 (secp521r1, "ECDSA P-521", which is not supported by Let's Encrypt yet.)

10. How to renew the issued certs

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

However, you can also force to renew any cert: --renew -d --force

or, for ECC cert: --renew -d --force --ecc

11. How to upgrade is in constant development, so it's strongly recommended to use the latest code.

You can update to the latest code: --upgrade

You can also enable auto upgrade: --upgrade --auto-upgrade

Then will be kept up to date automatically.

Disable auto upgrade: --upgrade --auto-upgrade 0

12. Issue a cert from an existing CSR

Under the Hood

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



  1. Acme-tiny:
  2. ACME protocol:
  3. Certbot:

License & Others

License is GPLv3

Please Star and Fork me.

Issues and pull requests are welcome.


  1. PayPal:

Donate List

Comments ( 0 )

You need to Sign in for post a comment

Help Search

183227_9af5e6a8_1826025 111910_4d91f001_1826025