A small Windows program for someone who only needs two or three certificates. Use it for a NAS, a webcam, or a page you host yourself. You do not need scripts, and you do not need to install Certbot. It is for everyday personal use, not for a business.
It talks to Let's Encrypt (through the Certes library) and saves the certificate files next to the program.
- It issues a certificate to you.
- It lists the certificates this program has issued, so you can see them, open their folder, revoke one, or delete the local files.
- Manage Certificates has a Renew button. It asks Let's Encrypt for a new certificate using the choices saved when that certificate was issued. It does not open the issue form.
- It is portable. Unzip it and run
acm.exe. Nothing to install. - It is for home use. It is not a business or company product.
Releases are Windows only: win-x86, win-x64, and win-arm64. There is no Mac or Linux build.
- Open Releases.
- Download the zip for your PC. Most people want
ACMECertManager-vX.Y.Z-win-x64.zip. The other names arewin-x86andwin-arm64. - Unzip it. Open the
ACMECertManagerfolder and runacm.exe.
The zip already contains what the program needs to run. You do not install .NET, and you do not run an installer.
The program keeps its files in folders beside acm.exe:
plugins/for DNS plugin fileslogs/for the logcerts/for certificate filesstorage/for the list of certificates, account keys, and settings
To use a newer zip without losing what you already have:
- Close the program.
- Unzip the new zip into the same
ACMECertManagerfolder and allow it to replaceacm.exe. - Leave
plugins/,logs/,certs/, andstorage/in place.
If you delete the old folder first, you lose those files unless you copied them somewhere else.
Open Issue New Certificate, type the name (for example nas.example.com), and choose how Let's Encrypt checks that the name is yours.
- HTTP-01. The usual choice when this PC can answer on port 80 for a minute. Port 80 must be free. Stop anything else that is using it, such as another web server, then try again. The program may ask you to run it as Administrator. If this PC is not the one the internet reaches, you can instead have the program place the check file in a folder, or send it by FTP, SFTP, WebDAV, or a web address.
- TLS-ALPN-01. Use this when port 80 is not available but port 443 is. Port 443 must be free while the check runs. The program may ask you to run it as Administrator. This does not install the certificate into Windows, and it does not attach it to an IIS site.
- DNS-01. Use this for a wildcard name such as
*.example.com, or when ports 80 and 443 cannot be opened. You need a DNS plugin (see below). A wildcard name only works with DNS-01.
The program uses the real Let's Encrypt service unless you turn on the staging (test) option. Staging certificates are not trusted by browsers. You can also type a different ACME directory address if you already have one.
You can leave the key as RSA 2048 (RS256), or pick ECDSA P-256 (ES256) or ECDSA P-384 (ES384). Check Also create a PFX file (certificate.pfx) only if you want a .pfx file as well as the PEM files. The PFX file is saved with no password.
After it finishes, the certificate shows up under Manage Certificates. That list is only what this program has issued. It does not read the Windows certificate store.
Each issue is saved under certs/{name}/{MM-dd-yyyy}/ next to acm.exe. Example: certs/nas.example.com/10-04-2026/.
You get:
cert.pemchain.pemfullchain.pemprivkey.pemcertificate.pfx, only if you asked for a PFX file
Issuing the same name again makes a new dated folder. If you issue it twice on the same day, the second folder gets a -2 (then -3, and so on). Older files are left alone.
A wildcard name such as *.example.com is stored in a folder named wildcard.example.com. For DNS-01, the TXT record name drops a leading *., so the record is _acme-challenge.example.com, not _acme-challenge.*.example.com.
Manage Certificates can open that folder, revoke the certificate at Let's Encrypt (this needs privkey.pem), or delete the local files. Deleting local files does not revoke the certificate. The list itself is kept in storage/certificates.json.
DNS plugin passwords are stored as plain text in storage/dns-secrets.json. Keep that folder private.
HTTP deployment settings are saved with each certificate in storage/certificates.json so Renew can reuse them. That includes the username, password, bearer token, and additional header value, all as plain text. Keep that folder private.
You only need a plugin for DNS-01, including wildcard names.
- Download a plugin zip from ACMECertManager-DnsPlugins Releases.
- Put the DLL in the
pluginsfolder next toacm.exe. - Start the program, choose DNS-01, pick the plugin, and fill in the fields it asks for.
If you want to write your own plugin, see docs/PLUGIN_DEVELOPMENT.md.
On Manage Certificates, select a certificate and click Renew.
Renew uses the choices saved with that certificate: email, ACME directory, validation method, key type, whether to create a PFX file, and the HTTP deployment settings or DNS plugin id. It does not open the issue form. The previous certificate stays in the list. The new files go in a new dated folder under certs/ (a same-day renewal gets a -2 folder, then -3, and so on).
Certificates issued by an older version do not have those choices. Renew writes a log line naming what is missing and stops. Issue that name once with this version, and a later Renew can replay it.
DNS plugin secrets stay in storage/dns-secrets.json. Renew reads the saved secrets for that plugin and name. It does not show the plaintext warning again. If the plugin is not in the plugins folder, or no secrets are saved for that name, Renew writes a log line and stops.
HTTP deployment credentials come from storage/certificates.json, where they are saved as plain text when the certificate is issued.
Nothing renews on a schedule while the program is closed. The program also does not install the certificate into Windows or bind it in IIS. Copy the files onto the NAS, camera, or site yourself, the way that device asks you to.
This section is for people changing the program. The zip above is enough if you only want certificates.
- Windows 10 or 11, and the .NET 10 SDK.
- License: GPL-3.0. See LICENSE.
- Build and run:
dotnet build ACMECertManager.slnthendotnet run --project src/ACMECertManager.csproj. - A version tag shaped like
v1.2.3, pushed frommain, builds the three Windows zips and publishes them on Releases. - How to contribute: CONTRIBUTING.md.
- How to report a security problem: SECURITY.md.

