Proxmox VE
Proxmox ships with an ACME client. It accepts a custom directory and EAB: the node obtains and renews its certificate without any extra tool.
| Value | Where to find it | In this guide |
|---|---|---|
| ACME directory | fixed for each instance | https://certs.example.com/acme/directory |
| Key ID (kid) | Keys & access → EAB credentials | eab_XXXXXXXXXXXXXXXX |
| HMAC key | shown only once, at creation | CLE_HMAC |
1. Register the account
From the command line on the node:
pvenode
pvenode acme account register local-cert ops@example.com \
--directory https://certs.example.com/acme/directoryThe command detects that the server requires an EAB and asks in turn for the Key ID (eab_XXXXXXXXXXXXXXXX) and then the HMAC key.
From the web interface: Datacenter → ACME → Accounts → Add, directory Custom, paste the URL, then fill in the EAB fields.
2. Declare the name and order
pvenode
pvenode config set --acme account=local-cert,domains=nas.home.example.com
pvenode acme cert orderFrom the web interface: node → System → Certificates → ACME section: choose the local-cert account, add the domain with type HTTP, then Order Certificates Now.
The pveproxy service restarts with the new certificate. Renewal is handled by the pve-daily-update timer.
Good to know
- In a cluster, the ACME account is shared; the domain configuration and the order are done node by node, each with its own name.
- Proxmox Backup Server and Proxmox Mail Gateway follow the same logic with
proxmox-backup-manager acme …andpmgconfig acme ….