<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Let's Encrypt on Daniel Zhang</title><link>https://zhangdapeng.dev/tags/lets-encrypt/</link><description>Recent content in Let's Encrypt on Daniel Zhang</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 16 Nov 2026 16:20:00 +0800</lastBuildDate><atom:link href="https://zhangdapeng.dev/tags/lets-encrypt/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing SSL Certificates with acme.sh: DNS Validation, Automatic Renewal, and Manual Deployment</title><link>https://zhangdapeng.dev/p/acme-sh-dns-certificate-manual-deployment/</link><pubDate>Mon, 16 Nov 2026 16:20:00 +0800</pubDate><guid>https://zhangdapeng.dev/p/acme-sh-dns-certificate-manual-deployment/</guid><description>&lt;img src="https://zhangdapeng.dev/p/acme-sh-dns-certificate-manual-deployment/cover.png" alt="Featured image of post Managing SSL Certificates with acme.sh: DNS Validation, Automatic Renewal, and Manual Deployment" /&gt;&lt;h2 id="1-background-issue-certificates-locally-and-deploy-them-manually"&gt;1. Background: Issue Certificates Locally and Deploy Them Manually
&lt;/h2&gt;&lt;p&gt;When managing SSL/TLS certificates with acme.sh, DNS-01 validation is a convenient way to obtain certificates from certificate authorities such as Let&amp;rsquo;s Encrypt.&lt;/p&gt;
&lt;p&gt;Unlike HTTP-01 validation, DNS-01 does not require a dedicated validation endpoint on your web server. It also allows you to issue certificates without running the certificate management process directly on your production server.&lt;/p&gt;
&lt;p&gt;My current workflow looks like this:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Install acme.sh on my local machine.&lt;/li&gt;
&lt;li&gt;Request a Let&amp;rsquo;s Encrypt certificate using DNS validation.&lt;/li&gt;
&lt;li&gt;Configure a DNS CNAME record to delegate the DNS validation process.&lt;/li&gt;
&lt;li&gt;Manually transfer the issued certificate files to a remote server.&lt;/li&gt;
&lt;li&gt;Configure Nginx or another web server to use the new certificates.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This approach keeps certificate management separate from the production environment. There is no need to install acme.sh on the remote server.&lt;/p&gt;
&lt;p&gt;However, it raises two important questions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Can the DNS CNAME validation record be deleted after the certificate has been issued?&lt;/li&gt;
&lt;li&gt;Is it necessary to keep the automatic renewal Cron job enabled when certificates are deployed manually?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Let&amp;rsquo;s look at both questions.&lt;/p&gt;
&lt;h2 id="2-can-you-delete-the-dns-cname-record-after-validation"&gt;2. Can You Delete the DNS CNAME Record After Validation?
&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;Yes, you can delete it, but you need to understand how this affects future renewals.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The purpose of DNS-01 validation is to prove that you control the domain name for which you are requesting a certificate.&lt;/p&gt;
&lt;p&gt;During the validation process, Let&amp;rsquo;s Encrypt checks a specific DNS TXT record to verify domain ownership.&lt;/p&gt;
&lt;p&gt;When using CNAME delegation, the validation process typically looks like this:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;_acme-challenge.example.com
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; | CNAME
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;_acme-challenge.validation.example.net
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; | TXT
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; DNS Verification
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; Certificate Issued
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The CNAME record redirects the original validation hostname to another DNS name where the required TXT record is maintained.&lt;/p&gt;
&lt;p&gt;Once the certificate has been successfully issued, the CA does not continuously check this CNAME record when visitors access your website.&lt;/p&gt;
&lt;p&gt;Therefore:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Deleting the CNAME record does not immediately invalidate an already-issued certificate.&lt;/li&gt;
&lt;li&gt;It does not affect normal HTTPS traffic.&lt;/li&gt;
&lt;li&gt;However, the next DNS-01 validation or renewal may fail because the original DNS delegation is no longer available.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="when-should-you-keep-the-cname-record"&gt;When Should You Keep the CNAME Record?
&lt;/h3&gt;&lt;p&gt;If you use acme.sh for automatic certificate renewal and want the entire process to run without manual intervention, you should keep the CNAME record permanently.&lt;/p&gt;
&lt;p&gt;During future renewals, acme.sh still needs to complete DNS validation to prove domain ownership.&lt;/p&gt;
&lt;p&gt;Removing the CNAME record may prevent this process from succeeding.&lt;/p&gt;
&lt;h3 id="when-is-it-safe-to-delete-the-cname-record"&gt;When Is It Safe to Delete the CNAME Record?
&lt;/h3&gt;&lt;p&gt;If you prefer to manage certificates manually, you can delete the CNAME record after successfully issuing a certificate.&lt;/p&gt;
&lt;p&gt;However, remember:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;You must restore the correct CNAME record before the next DNS validation or renewal attempt and allow time for DNS propagation.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Deleting the record does not eliminate the need for DNS configuration. It simply makes DNS record management a manual task.&lt;/p&gt;
&lt;h2 id="3-check-whether-acmesh-automatic-renewal-is-configured"&gt;3. Check Whether acme.sh Automatic Renewal Is Configured
&lt;/h2&gt;&lt;p&gt;During a typical installation, acme.sh automatically creates a Cron job to check certificate expiration and handle renewals.&lt;/p&gt;
&lt;p&gt;You can check whether this task exists by running:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;crontab -l
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If you see an entry similar to the following:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="m"&gt;56&lt;/span&gt; &lt;span class="m"&gt;0&lt;/span&gt; * * * &lt;span class="s2"&gt;&amp;#34;/root/.acme.sh&amp;#34;&lt;/span&gt;/acme.sh --cron --home &lt;span class="s2"&gt;&amp;#34;/root/.acme.sh&amp;#34;&lt;/span&gt; &amp;gt; /dev/null
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;It means that an automatic renewal check has been configured.&lt;/p&gt;
&lt;p&gt;This task typically runs once a day and checks whether any managed certificates need renewal.&lt;/p&gt;
&lt;p&gt;It is important to understand that several independent processes are involved:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Cron:&lt;/strong&gt; Periodically triggers the renewal check.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;acme.sh:&lt;/strong&gt; Determines whether a certificate needs renewal and performs the renewal.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;DNS validation:&lt;/strong&gt; Proves domain ownership during certificate issuance or renewal.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Certificate deployment:&lt;/strong&gt; Installs the renewed certificate in the actual production environment.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These processes are related, but they are not the same thing.&lt;/p&gt;
&lt;p&gt;Having automatic renewal enabled does not automatically update certificates on a remote server.&lt;/p&gt;
&lt;h2 id="4-do-you-need-automatic-renewal-when-issuing-certificates-locally"&gt;4. Do You Need Automatic Renewal When Issuing Certificates Locally?
&lt;/h2&gt;&lt;p&gt;This is the most important consideration for my particular setup.&lt;/p&gt;
&lt;p&gt;My certificate management workflow looks like this:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Local Machine
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; acme.sh
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; DNS Validation
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; Certificate Issued
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; Manual Download / Copy
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; Remote Server
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; Nginx / HTTPS
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;In this architecture, local certificate renewal and remote certificate deployment are not connected.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;acme.sh runs its daily renewal check locally.&lt;/li&gt;
&lt;li&gt;The certificate reaches its renewal threshold.&lt;/li&gt;
&lt;li&gt;acme.sh successfully obtains a renewed certificate.&lt;/li&gt;
&lt;li&gt;The new certificate is stored locally.&lt;/li&gt;
&lt;li&gt;The remote server continues using the previously deployed certificate.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This creates a potential problem:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The certificate on your local machine may already be renewed, while your production server is still using the old certificate.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Without an automated deployment mechanism, local automatic renewal alone cannot guarantee that your production HTTPS service continues using an up-to-date certificate.&lt;/p&gt;
&lt;h3 id="option-1-fully-manual-certificate-management"&gt;Option 1: Fully Manual Certificate Management
&lt;/h3&gt;&lt;p&gt;If you prefer a simple setup and do not want acme.sh running automatic renewal checks in the background, you can remove its Cron job.&lt;/p&gt;
&lt;p&gt;Run:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;acme.sh --uninstall-cronjob
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Then verify that the task has been removed:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;crontab -l
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;You can now manage certificate renewals manually.&lt;/p&gt;
&lt;p&gt;For example, to renew a certificate:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;acme.sh --renew -d example.com
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If you need to force a new issuance, you can use:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;acme.sh --renew -d example.com --force
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;For normal certificate maintenance, avoid using &lt;code&gt;--force&lt;/code&gt; unnecessarily because it can trigger additional certificate issuance.&lt;/p&gt;
&lt;p&gt;With this approach:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You do not need to keep the DNS CNAME record permanently.&lt;/li&gt;
&lt;li&gt;You can disable the automatic renewal Cron job.&lt;/li&gt;
&lt;li&gt;You are responsible for monitoring certificate expiration dates.&lt;/li&gt;
&lt;li&gt;You must restore the DNS validation records before the next renewal.&lt;/li&gt;
&lt;li&gt;You manually deploy the renewed certificates to your remote server.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This approach works well for personal projects with a small number of certificates, provided you actively monitor their expiration dates.&lt;/p&gt;
&lt;h3 id="option-2-automatic-renewal-with-manual-deployment"&gt;Option 2: Automatic Renewal with Manual Deployment
&lt;/h3&gt;&lt;p&gt;Another option is to keep the automatic renewal Cron job enabled.&lt;/p&gt;
&lt;p&gt;This allows acme.sh to renew certificates locally without requiring you to initiate the renewal manually.&lt;/p&gt;
&lt;p&gt;However, there are still a few things to consider:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The DNS CNAME record must remain available.&lt;/li&gt;
&lt;li&gt;New certificates can be generated automatically.&lt;/li&gt;
&lt;li&gt;Remote servers still need manual certificate deployment.&lt;/li&gt;
&lt;li&gt;You must periodically verify that local and remote certificates are synchronized.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This approach reduces manual certificate issuance work, but it does not solve the remote deployment problem.&lt;/p&gt;
&lt;h2 id="5-further-optimization-automatically-deploy-certificates-over-ssh"&gt;5. Further Optimization: Automatically Deploy Certificates over SSH
&lt;/h2&gt;&lt;p&gt;If you want a fully automated workflow, consider using an acme.sh Deploy Hook.&lt;/p&gt;
&lt;p&gt;For example, you can use SSH to deploy renewed certificates to a remote server.&lt;/p&gt;
&lt;p&gt;acme.sh supports deployment hooks that handle certificate installation after successful issuance or renewal. The exact deployment configuration depends on the selected hook and its supported options.&lt;/p&gt;
&lt;p&gt;The overall workflow becomes:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;Local Machine
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; acme.sh
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; Automatic DNS Validation
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; Certificate Renewal
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; SSH Deploy
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; Remote Server
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; |
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; v
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; Nginx Reload
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;With this approach:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;A local Cron job periodically checks certificate expiration.&lt;/li&gt;
&lt;li&gt;When renewal is required, acme.sh performs DNS validation.&lt;/li&gt;
&lt;li&gt;A new certificate is issued automatically.&lt;/li&gt;
&lt;li&gt;The certificate is transferred to the remote server through SSH.&lt;/li&gt;
&lt;li&gt;The certificate files are updated on the server.&lt;/li&gt;
&lt;li&gt;Nginx is reloaded to activate the new certificate.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This requires some additional configuration, including SSH keys, remote file permissions, and deployment hooks.&lt;/p&gt;
&lt;p&gt;For a simple Nginx setup, you can also write a custom deployment script to synchronize certificate files and reload the web server.&lt;/p&gt;
&lt;p&gt;One important detail: uploading new certificate files is not enough. You must also ensure that Nginx actually reloads and starts using the renewed certificate.&lt;/p&gt;
&lt;h2 id="6-conclusion-choose-a-certificate-management-strategy-that-fits-your-workflow"&gt;6. Conclusion: Choose a Certificate Management Strategy That Fits Your Workflow
&lt;/h2&gt;&lt;p&gt;For individual developers managing certificates with acme.sh, the best approach depends on how much automation is actually needed.&lt;/p&gt;
&lt;p&gt;Here is a comparison of the three approaches:&lt;/p&gt;
&lt;table&gt;
	&lt;thead&gt;
			&lt;tr&gt;
					&lt;th&gt;Management Strategy&lt;/th&gt;
					&lt;th&gt;Keep CNAME&lt;/th&gt;
					&lt;th&gt;Automatic Renewal&lt;/th&gt;
					&lt;th&gt;Automatic Deployment&lt;/th&gt;
			&lt;/tr&gt;
	&lt;/thead&gt;
	&lt;tbody&gt;
			&lt;tr&gt;
					&lt;td&gt;Fully manual&lt;/td&gt;
					&lt;td&gt;Not required permanently&lt;/td&gt;
					&lt;td&gt;No&lt;/td&gt;
					&lt;td&gt;No&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Automatic renewal + manual deployment&lt;/td&gt;
					&lt;td&gt;Yes&lt;/td&gt;
					&lt;td&gt;Yes&lt;/td&gt;
					&lt;td&gt;No&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Automatic renewal + SSH deployment&lt;/td&gt;
					&lt;td&gt;Yes&lt;/td&gt;
					&lt;td&gt;Yes&lt;/td&gt;
					&lt;td&gt;Yes&lt;/td&gt;
			&lt;/tr&gt;
	&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;For my current setup:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;I use acme.sh locally to issue certificates.&lt;/li&gt;
&lt;li&gt;DNS validation is used to verify domain ownership.&lt;/li&gt;
&lt;li&gt;Certificates are manually deployed to remote servers.&lt;/li&gt;
&lt;li&gt;acme.sh does not need to run on the production servers.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Therefore, if I continue using a fully manual management approach, I can remove the local automatic renewal Cron job and delete the DNS CNAME validation record after successfully issuing the certificate.&lt;/p&gt;
&lt;p&gt;However, one important thing to remember is:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The DNS validation record must be configured again before the next certificate issuance or renewal.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If the number of certificates grows or manual maintenance becomes inconvenient, I can consider using an SSH Deploy Hook to connect certificate renewal and remote deployment into a fully automated workflow.&lt;/p&gt;
&lt;p&gt;Ultimately, certificate management does not have to be fully automated. What matters is keeping certificate issuance, renewal, and deployment properly synchronized.&lt;/p&gt;
&lt;p&gt;Otherwise, you may end up with a renewed certificate on your local machine while your production server continues serving an outdated one.&lt;/p&gt;</description></item></channel></rss>