Repository navigation
CertMate #2344
Description
Activity
The CertMate script is ready for testing. Run it in the Proxmox VE shell (or on an Incus host) to create a container:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/certmate.sh)"There is no default login. The first page creates the administrator account and asks for the API token, which the install generated: grep API_BEARER_TOKEN /opt/certmate_data/.env
Keep a copy of /opt/certmate_data/.env off the container. CERTMATE_BACKUP_PASSPHRASE encrypts the backups, and SECRET_KEY must match for a backup to restore the API token.
CertMate listens on plain HTTP on port 8000 on every interface. To expose it beyond your LAN, put an HTTPS reverse proxy in front and set BEHIND_PROXY=true in /opt/certmate_data/.env, then run systemctl restart certmate.
Certificates, settings, backups and logs live in /opt/certmate_data and survive updates.Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Discord testing thread: https://discord.com/channels/1302816934508630047/1554934490852491397
Reacted by Prakhar BirlaA PR has been created for certmate: community-scripts/ProxmoxVE#17803
▶️ Testing resumed. Discord thread: https://discord.com/channels/1302816934508630047/1554934490852491397Merged with #17803 in ProxmoxVE
Files deleted with PR #2409
Name of the Script
CertMate
Script Type
CT (LXC Container)
Script path
No response
Where does it run?
Proxmox VE host
Does this script support arm64?
arm64 supported
📋 Script Details
#2338
New script: CertMate, a self-hosted TLS certificate lifecycle manager with ACME issuance/renewal (Let's Encrypt and other CAs), DNS-01 on 20+ providers, inventory, deployment hooks and a REST API. It is a Python/Flask app served by gunicorn.