Skip to main content

Configuring clmBot

Download clmBot and upload it to the server​

Software address: Download clmBot

Download clmBot

Download the clmBot corresponding to your system and upload it to the server.

clmBot configuration​

  1. Initialize clmBot. First, change the clmBot format to executable: #chmod 755 clm-bot-linux-amd64
  2. Login initialization: #./clm-bot-linux-amd64 login, and enter Access address, AccessKey, and AccessSecret in sequence, then press Enter.
    Where to generate AK/SK

    Go to Backend -> sslTrus CaaS service -> Product details -> Then click SSL certificate details -> Generate AK/SK

Generate AK/SK :::

After connecting, the following prompt will be returned.

Configure clmBot

Log in to the backend and go to clmBot. You will see a newly added clmBot node. Click Allow Access to activate clmBot.

Configuring clmBot

  1. Automatically scan certificates and storage paths on the server, command: ./clm-bot-linux-amd64 discover-certificate

After the command is executed, the found certificate information and path will be displayed. Enter Y to confirm adding it to the backend management.

Configure clmBot

Then you can see the relevant configuration in the config.yaml file in the current directory. Pay attention to the after_script section. This is the script executed after certificate renewal and needs to be modified according to your actual situation.

Configure clmBot

  1. Activate the node. Log in to the admin console and go to installation points and access points to see the newly added node information. After clicking activate, you can manage the node.

Configuring clmBot
Configuring clmBot

Certificate Renewal (Physical Machine/Cloud Host)​

Method 1: Remote control update​

  1. Start the clmBot server on the server with the command: ./clm-bot-linux-amd64 server -a="0.0.0.0:8862"

This command requires opening the 8862/tcp port and starting a server with mutual TLS authentication. If you cannot open the port, refer to Method 2.

Certificate Renewal (Physical Machine/Cloud Host)

  1. Log in to the admin console, go to the installation point, and click Push Certificate. The system will push the latest certificate to the server.

Certificate Renewal (Physical Machine/Cloud Host)

Method 2: Local Control Update​

  1. On the server side, add clmBot to the crontab scheduled tasks. The clmBot update command: cd /opt/clm-bot-demo && ./clm-bot-linux-amd64 update-certificate >> update.log (Fill in the actual path, and ensure that you cd to the installation directory)

Certificate Renewal (Physical Machine/Cloud Host)

The setting here is to check for certificate renewal updates at 3 a.m. every day.

Similarly, scheduled tasks can be configured in Windows, as shown in the following figure. After configuration, you can right-click the created task to run it, and check the logs in the installation directory to confirm whether the installation is correct:

Certificate Renewal (Physical Machine/Cloud Host)

Certificate Reissuance​

  1. In the sslTrus CaaS management console, switch to the SSL certificate details tab and set the automatic certificate reissue cycle.

Certificate Renewal (Physical Machine/Cloud Host)

Note

The effect of the current configuration: the backend will automatically reissue a new certificate 15 days before the certificate expires (in this case, every 30 days). clmbot executes certificate renewal at 3 a.m. every day. If it detects a new certificate in the backend, it will automatically fetch the new certificate to the server for replacement and restart the service to make the new certificate take effect.