HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
acmesh-official
acme.sh
Shell2016–2026
acmesh-official / acme.sh

acme.sh

A pure Unix shell script ACME client for SSL / TLS certificate automation

66Distinct people
94Mentions
2Explicit recommenders
48KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A pure Unix shell script ACME client for SSL / TLS certificate automation

GitHub

Where it is used

  • OpenWrt — OpenWrt uses acme.sh to provide ACME-based certificate issuance and renewal via its packaged acme-acmesh integration. The distro ships acme.sh so users can obtain HTTPS certificates on OpenWrt systems. Source

What people are saying

It’s “only” 7.1K LoC, but my favorite is the “acme.sh” script which is used to issue and renew certs from Lets Encrypt.…

xyst used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year94 dated mentions

Observed mentions: 2016-04-14 15:49:23 UTC to 2026-10-16 10:19:09 UTC.

0510152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 16 mentions; 2 submissions, 14 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC110
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC413
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC1019
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC615
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC16214
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC12111
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC10010
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC716
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC12210
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC707
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC909

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
🔐 acme.sh An ACME Protocol Client Written Purely in Shell ✨ Features 🐚 An ACME protocol client written purely in Shell (Unix shell) language 📜 Full ACME protocol implementation 🔑 Support ECDSA certificates 🌐 Support SAN and wildcard certificates ⚡ Simple, powerful and very easy to use — only 3 minutes to learn! 🔧 Compatible with Bash, dash and sh 🚫 No dependencies on Python 🔄 One script to issue, renew and install your certificates automatically 👤 DOES NOT require root/sudoer access 🐳 Docker ready 🌍 IPv6 ready 📧 Cron job notifications for renewal or error 💡 It's probably the easiest & smartest shell script to automatically issue & renew free certificates. 📚 Wiki • 🐳 Docker Guide • 🐦 Twitter 🌏 中文说明 🏆 Who Uses acme.sh? FreeBSD.org ruby-china.org Proxmox pfsense Loadbalancer.org discourse.org Centminmod splynx opnsense.org CentOS Web Panel lnmp.org more... 🖥️ Tested OS NO Status Platform 1 Mac OSX 2 Windows (cygwin with curl, openssl and crontab included) 3 FreeBSD 4 Solaris 5 Ubuntu 6 NA pfsense 7 OpenBSD 8 NetBSD 9 DragonFlyBSD 10 MidnightBSD 11 Omnios 12 OpenIndiana 13 Debian 14 openSUSE 15 Alpine Linux (with curl) 16 Archlinux 17 fedora 18 Kali Linux 19 Oracle Linux 20 Mageia 21 Gentoo Linux 22 ----- Cloud Linux #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 25 Haiku OS 26 Tribblix 27 GhostBSD 28 GNU Hurd 29 openEuler 30 HardenedBSD 31 OPNsense 🧪 Check our testing project 🖥️ The testing VMs are supported by vmactions.org 🏛️ Supported CA CA Status ZeroSSL.com CA ⭐ Default Letsencrypt.org CA ✅ Supported SSL.com CA ✅ Supported Google.com Public CA ✅ Supported Actalis.com CA ✅ Supported Pebble strict Mode ✅ Supported Any RFC8555-compliant CA ✅ Supported ⚙️ Supported Modes Mode Description 📁 Webroot mode Use existing webroot directory 🖥️ Standalone mode Built-in webserver on port 80 🔐 Standalone tls-alpn mode Built-in webserver on port 443 🪶 Apache mode Use Apache for verification ⚡ Nginx mode Use Nginx for verification 🌐 DNS mode Use DNS TXT records 🔗 DNS alias mode Use DNS alias for verification 📡 Stateless mode Stateless verification 📌 DNS persist mode Persistent DNS TXT record (draft-ietf-acme-dns-persist-01) 📖 Usage Guide 1️⃣ How to Install 📥 Install Online Check this project: https://github.com/acmesh-official/get.acme.sh curl https://get.acme.sh | sh -s email=my@example.com Or: wget -O - https://get.acme.sh | sh -s email=my@example.com 📦 Install from Git Clone this project and launch installation: git clone https://github.com/acmesh-official/acme.sh.git cd ./acme.sh ./acme.sh --install -m my@example.com 💡 You don't have to be root then, although it is recommended. 📚 Advanced Installation: https://github.com/acmesh-official/acme.sh/wiki/How-to-install The installer will perform 3 actions: Create and copy acme.sh to your home dir ($HOME): ~/.acme.sh/. All certs will be placed in this folder too. Create alias for: acme.sh=~/.acme.sh/acme.sh. Create daily cron job to check and renew the certs if needed. Cron entry example: 0 0 * * * "/home/user/.acme.sh"/acme.sh --cron --home "/home/user/.acme.sh" > /dev/null ⚠️ After the installation, you must close the current terminal and reopen it to make the alias take effect. ✅ You are ready to issue certs now! Show help message: acme.sh -h 🔏 Verify a Release Release tags from 3.1.6 on are signed with the maintainer's SSH key. The signing happens on the maintainer's machine, so the private key is never available to CI. The public half is allowed_signers in this repository. From a clone: git config gpg.ssh.allowedSignersFile allowed_signers git verify-tag 3.1.6 The signature covers the tag object, which pins the commit and therefore the whole tree, so a good signature verifies every file at that release and no separate tarball checksum is needed. Build a tarball from the verified tag: git archive --format=tar.gz --prefix=acme.sh-3.1.6/ 3.1.6 > acme.sh-3.1.6.tar.gz ⚠️ Tags up to 3.1.5 are unsigned. 2️⃣ Issue a Certificate Example 1: Single domain. acme.sh --issue -d example.com -w /home/wwwroot/example.com or: acme.sh --issue -d example.com -w /home/username/public_html or: acme.sh --issue -d example.com -w /var/www/html Example 2: Multiple domains in the same cert. acme.sh --issue -d example.com -d www.example.com -d cp.example.com -w /home/wwwroot/example.com 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. Second argument "example.com" 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/example.com. The certs will be placed in ~/.acme.sh/example.com/ 🔄 The certs will be renewed automatically every 30 days. 🔐 The certs will default to ECC certificates. 📚 More examples: https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert 3️⃣ Install the Certificate to Apache/Nginx After the cert is generated, you probably want to install/copy the cert to your Apache/Nginx or other servers. ⚠️ IMPORTANT: 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. 🪶 Apache Example: acme.sh --install-cert -d example.com \ --cert-file /path/to/certfile/in/apache/cert.pem \ --key-file /path/to/keyfile/in/apache/key.pem \ --fullchain-file /path/to/fullchain/certfile/apache/fullchain.pem \ --reloadcmd "service apache2 force-reload" ⚡ Nginx Example: acme.sh --install-cert -d example.com \ --key-file /pa
Read the full README on GitHub

What Hacker News says

12 sources
Assuming you are working on the dev machine, the process is as follows: 1. Buy a domain name. Certificates can only be issued if you have a real domain name. You can't get a certificate for "localhost" or "blah.localhost". You don't actually need to point this domain at your dev machine, you just need to own it. Let's call this domain "my-domain.com" 2. Follow the instructions for setting up the DNS-01 challenge. As a part of this, you'll need to provide credentials to allow LE to change your DNS records so it can renew the certificate automatically. Most registrars you can buy domains from will provide free DNS service and many will also provide API access to change DNS records. If this is the case, there's probably already support in LE for setup so you can just follow the instructions [here](https://github.com/acmesh-official/acme.sh/w
Read the rest
iki/dnsapi) to provide the needed credentials. 3. Once the setup is complete, you should have a certificate (public certificate chain + private key) issued by LE and it should also automatically renew. Edit your dev server's configuration to use to these issued files for HTTPS. 4. Add something in /etc/hosts (or equivalent in Windows) like: 127.0.0.1 my-domain.com 5. Now load your dev environment by visiting `https://my-domain.com` on your local machine. It should work now with no certificate errors (green padlock). Congrats! You now have HTTPS for local dev at no cost beyond owning a domain + you can still use this domain to serve a real website (say hosted with some cloud host). The domain _does not_ need to point to your dev environment. In fact your dev machine doesn't even need to be connected to the Internet (as long as you can handle the renewals). Advanced: Now, if you want `my-domain.com` to also be productive, say, to serve your blog hosted on say EC2 over HTTPS, you can just edit your renewal setup. Add a post-renewal script that copies (e.g. scp) the renewed keys over to your EC2. Now both your dev machine (local) and your "production" server (remote) have the same key. When you visit the domain locally, the /etc/hosts record circumvents DNS so you end up just hitting your local dev server which has the key info it needs to serve you HTTPS. When you visit the domain from a different machine, it would do a DNS query and end up hitting the remote instance. But since that instance also has the key info, it can also serve HTTPS. Now if you want your dev machine to also be able to hit production, you can (1) when you setup LE in step 2, set it up so that it issues "*.my-domain.com" instead. (2) In step 4, use `dev.my-domain.com` instead of `my-domain.com`. This way on your dev machine, hitting `dev.my-domain.com` gets you the local dev server with a green padlock, hitting `my-domain.com` gets you the remote server, also with a green padlock. Both servers are sharing a wildcard certificate. The interesting part about doing it like this is that you don't need "dev.my-domain.com" to actually be a real DNS record. From the internet, nobody would even know that that subdomain exists.
In Chrome may start restricting requests to private networks
> It's not always possible to get certificates from Let's Encrypt for local network only services. In a big corporate environment jumping through the hoops necessary to deploy keys or get things into a DMZ can be near impossible. You're not wrong, but if you can go through the paperwork to add a CNAME to external DNS, your team can use DNS validation to verify host record ownership for LE/ACME: * https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mo... * https://www.eff.org/deeplinks/2018/02/technical-deep-dive-se... * https://dan.langille.org/2019/02/01/acme-domain-alias-mode/ Seems not many people know about using dns-01 for internal-only hosts.
In Chrome may start restricting requests to private networks
> otherwise you have the DNS option which means giving the server access to modify the DNS records which is also unsafe should the box get compromised This is true, but the machine doing DNS modifications doesn't need to be accessible to any outside initiated connections at all. So if someone has the capacity to compromise such a computer, what would stop them from compromising your desktop computer or your laptop instead? But either way it would indeed be nice to have further limits on what the box could do. But I think LetsEncrypt does not need to change anything to make this possible. https://letsencrypt.org/docs/challenge-types/ The DNS verification works by creating a DNS TXT record named "_acme-challenge" with a TXT value on the domain you are verifying. So really what you want is for your DNS provider to implement into their API ac
Read the rest
cess keys that can be restricted so that the absolutely only thing the key is allowed to do is to create, change and delete the DNS TXT record named "_acme-challenge". Perhaps some DNS providers already make this possible? But the one I am using is only able to limit it to a ZONE, but not to a specific record type and not to a specific label. In fact I wish CloudFlare would allow such specific fine-grained permissions. But even if they did they'd probably make it part of the Enterprise plan and I am still not an Enterprise customer so. Edit: Meanwhile that I was writing this someone else posted a sibling comment about ACME DNS alias mode, which I had not heard of. https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mo... That's very close to good enough. Though it would still be nice if DNS providers made it possible to issue API access tokens that are limited to specific record type and specific label.
In Another free CA as an alternative to Let's Encrypt
> If you want to use the www auth you need to allow outbound connections to any IP Only for the time period when you're requesting the cert though: it does not have to be open to the entire Internet 24/7. While this may not satisfy your personal / particular level of security concern, but it is something worth keeping in mind. Using the dehydrated client as an example, the web server could be started and stopped (or the host's firewall rules altered) in the startup_hook() / exit_hook() functions, or the deploy_challenge() / clean_challenge() functions: * https://github.com/dehydrated-io/dehydrated/blob/master/docs... > otherwise you have the DNS option which means giving the server access to modify the DNS records which is also unsafe should the box get compromised. Are you aware of LE/ACME's "DNS alias" mode? * https://github.com/acmesh-
Read the rest
official/acme.sh/wiki/DNS-alias-mo... * https://www.eff.org/deeplinks/2018/02/technical-deep-dive-se... Let us say you want to get a cert for foo.example.com. Letting an ACME client change the value of that could be a risk, as you state. So what you can do is (manually) create a CNAME _acme-challenge.foo.example.com, and point that elsewhere, like _acme-challenge.foo.dnsauth.example.com. You then allow the ACME client to alter (just) the TXT records of _acme-challenge.foo.dnsauth. People have even written simple DNS server that allow for updating of records via a RESTful API, so you can server just the (e.g.) dnsauth sub-domain from it, leaving your main domain untouched (besides the initial CNAME addition): * https://github.com/joohoi/acme-dns There's also a CLI utility that can handle access the APIs of several dozen DNS companies so you don't have to roll your own if you want to server the sub-domain from your current provider: * https://github.com/AnalogJ/lexicon And you don't have to use a sub-domain, but something else entirely too: instead of dnsauth.example.com you can point the CNAME to example-dnsauth.com or example.org. So if your primary DNS provider doesn't have an API, you can use another one that does. The destination CNAME does not matter as long as you control and can update it.
In Another free CA as an alternative to Let's Encrypt
Inspired by this thread I just did this, except not with the wildcard. I have a droplet at Digital Ocean, so I used their DNS service. I configured some CNAME records for the local services, pointing to the internal names[1]. I then configured my PiHole with a local DNS CNAME record, pointing service.local.example.com to service.localdomain. Since my PiHole is not the DHCP server, I had to add a local DNS record for service.localdomain which matched the static IP that my router gives out. It seems the conditional forwarding done by PiHole happens earlier in the resolution process. I could then configure my services to use the DNS challenge for service.local.example.com, using the DO plugin for certbot[2] or just acme.sh[3], depending on what was available. I didn't get it to work immediately on Android devices, until I discovered that And
Read the rest
roid only uses IPv6 DNS servers if it has an IPv6 address, and I hadn't configured that in my router. So added the static ULA address of the PiHole lease to the DHCPv6 DNS server announcement[4]. Was a bit of fiddling since I'm a networking nub, but went smoother than I had feared. Not sure how to best distribute certificates though, if I had found a way I could let the router do all the renewals. [1]: Not sure if this is needed but didn't bother experimenting with removing it yet. [2]: https://certbot-dns-digitalocean.readthedocs.io/en/stable/ [3]: https://github.com/acmesh-official/acme.sh/wiki/dnsapi#20-us... [4]: https://openwrt.org/docs/techref/odhcpd#dhcp_section
In Increasing HTTPS Adoption

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.