📄️ Navigation
sslTrus clmBot usage guide navigation: Learn how clmBot works, supported systems and middleware, the difference between cloud push and scheduled pull for certificate updates, and quickly find pages for quick start, configuration reference, permission requirements, etc.
📄️ Quick Start
clmBot Quick Start Tutorial: Generate AccessKey/AccessSecret, download and upload clmBot to the server, execute 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 of clmBot: cloud push mode (the server receives push notifications, requiring port 8862/tcp to be open) and scheduled pull mode (crontab / Windows Task Scheduler periodically checks for updates), as well as instructions for setting the automatic certificate re-issuance period.
📄️ Installation Point Management
clmBot certificate installation point management: use discover-certificate to automatically scan certificates on the host 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
Reference for clmBot config.yaml: app access configuration, servers installation point fields, sub-fields for five certificate formats (pem/pfx/jks/iis/exchange), execution timing for before_script/after_script, and script template variables.
📄️ 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 configuration and after_script reload scripts, and 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 Deployment and Upgrade
clmBot service deployment and upgrade: use server --service to register clmBot as a systemd or Windows system service for auto-start on boot, configuration hot reload instructions, runtime log location and rotation policy, and use the update command to upgrade to the latest version.
🗃️ Historical Documents
2 items