I am aware of Caddy's automated renewal and Longting WAF's automated renewal, including services like acme.sh, and I have used them as well.
The tools mentioned above generally suffer from the following issues:
- Inability to automate CDN vendor certificate configuration, or poor compatibility.
- It cannot be guaranteed that the network environment will remain stable for issuing certificates.
- It is impossible to guarantee the security of automated scripts.
- Managing multiple certificates can be complex and time-consuming.
While Acme does mention support for Alibaba Cloud in its documentation, this is actually a patch implemented by individual developers. The support period was also relatively short, and the actual use experience presented some problems. Using shell commands always gives a feeling of insecurity.
I won't discuss the panel-type devices; I don't like using them.
Based on the above information, the current SSL-bot is self-implemented. Since the certificate validity period has been shortened by 3 months, communities like v2ex, primarily consisting of programmers (although they claim to be a community of creators), are constantly discussing this issue and seeking better ways.
To ensure business scalability and security, the SSL-bot implemented independently will inevitably have some issues. It requires continuous operation and iteration to approach perfection. However, due to limited personal resources, this is the only feasible approach. Please understand.