📄️ Navigation
sslTrus clmBot usage guide navigation: Learn how clmBot works, supported systems and middleware, differences between cloud push and scheduled pull certificate update methods, and quickly find pages such as quick start, configuration reference, and permission requirements.
📄️ Quick Start
clmBot quick start tutorial: generate AccessKey/AccessSecret, download and upload clmBot to the server, run login to connect, activate the node in the admin console, automatically discover server certificates and complete the first certificate update.
📄️ Certificate update methods
Configuration methods for the two certificate update modes in clmBot: cloud push mode (the server receives pushes and must open 8862/tcp) and scheduled pull mode (crontab / Windows Task Scheduler periodically checks for updates), as well as instructions for setting the certificate automatic re-issuance cycle.
📄️ Installation Point Management
clmBot certificate installation point management: use discover-certificate to automatically scan certificates on the local machine and in Docker containers, add-server to manually add installation points, sync-server to sync to the cloud and calibrate subscription IDs, setup for the local web configuration page, and query-certificate to view certificate information.
📄️ Configuration Reference
clmBot config.yaml configuration reference: app access configuration, servers installation point fields, subfields for pem/pfx/jks/iis/exchange certificate formats, before_script/after_script execution timing, and script template variable descriptions.
📄️ Configuration Examples
clmBot configuration examples: server configuration snippets for nginx and Apache using PEM certificates, Tomcat using JKS or PEM certificates, corresponding clmBot installation point configurations and after_script reload scripts, as well as configuration methods for custom services using PFX certificates.
📄️ Runtime Permission Requirements
Describes the runtime account permission configuration required by the principle of least privilege when running clmBot in middleware scenarios such as nginx, Apache, Tomcat, and IIS, including certificate directory read/write permissions, service reload command authorization, and Linux sudoers configuration examples.
📄️ Service-Based Deployment and Upgrade
clmBot service-based deployment and upgrade: use server --service to register clmBot as a systemd or Windows system service for automatic startup on boot, configuration hot reload instructions, runtime log locations and rotation policies, and use the update command to upgrade to the latest version.
📄️ clmBot Certificate Push
By installing the lightweight clmBot client, achieve automated deployment and renewal of SSL certificates on intranet servers without opening inbound ports.
📄️ clmBot Runtime Permission Requirements
Explains the runtime account permission configuration required for running clmBot under middleware scenarios such as nginx, Apache, Tomcat, and IIS following the principle of least privilege, including certificate directory read/write permissions, service reload command authorization, and Linux sudoers configuration examples.