Nginx Proxy Manager
Nginx Proxy Manager's interface lets you choose neither the ACME server nor an EAB: its built-in issuance only talks to Let's Encrypt. The certificate is therefore obtained separately, then imported as a custom certificate.
1. Get the certificate
On the host, with acme.sh (see certbot, acme.sh, lego for details):
acme.sh
acme.sh --register-account --server https://certs.example.com/acme/directory \
--eab-kid eab_XXXXXXXXXXXXXXXX --eab-hmac-key CLE_HMAC -m ops@example.com
mkdir -p /var/lib/acme-webroot /opt/npm-certs
acme.sh --issue --server https://certs.example.com/acme/directory -d nas.home.example.com -w /var/lib/acme-webroot
acme.sh --install-cert -d nas.home.example.com \
--key-file /opt/npm-certs/nas.home.example.com.key \
--fullchain-file /opt/npm-certs/nas.home.example.com.pem2. Import it
- SSL Certificates → Add SSL Certificate → Custom.
- Key:
nas.home.example.com.key. Certificate:nas.home.example.com.pem. - In the Proxy Host, SSL tab, select this certificate.
Another route: let local-cert manage the key
Through the API, local-cert generates the key, renews on its own and exposes the current certificate. A scheduled script then only has to download the bundle and push it into Nginx Proxy Manager. See Other systems.