On most Linux VPSs, Certbot already installs an automatic renewal schedule. Your job is to verify that scheduler, confirm the certificate configuration, run sudo certbot renew --dry-run, and make sure the service reloads the renewed files. Add cron or a systemd timer only when your installation has neither.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
This guide covers packaged Certbot installations, nginx, Apache, webroot and DNS validation, custom daemons, testing, monitoring, and the failures that commonly interrupt unattended renewal.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What Certbot auto-renewal actually does
Certbot’s recurring command is sudo certbot renew. It examines every certificate managed on the VPS and renews only certificates that have entered Certbot’s renewal window; certificates that are not close to expiry are left unchanged. This makes the command safe to run repeatedly from cron or a systemd timer.
After a successful renewal, Certbot writes the new certificate into its managed storage and updates the stable paths under /etc/letsencrypt/live/. Services should reference those paths rather than a dated archive filename. A web server or other daemon must still reload its configuration before it can use the new key and certificate.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Most Certbot installations come with automatic renewals preconfigured. Installing a second scheduler without checking first can create duplicate runs, confusing logs, unnecessary validation attempts, and avoidable certificate-authority rate-limit exposure.
Prerequisites and safety checks
- Root or
sudoaccess to the VPS. - A certificate already issued and managed by Certbot, or a completed Certbot configuration for the domain.
- DNS records pointing the hostname at this VPS when using HTTP-01 or a web-server plugin.
- Port 80 reachable from the public internet for HTTP-01 validation. DNS-01 instead requires authority to create the required DNS records and enough time for them to propagate.
- A backup of
/etc/letsencrypt/before changing renewal configuration or hooks.
Do not hand-edit files in /etc/letsencrypt/renewal/ as a first resort. Those files describe the authenticator, certificate names, account details, and renewal options. If a change is necessary, back up the file, make the smallest edit possible, and immediately run a dry run.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →1. Identify the Certbot installation and existing scheduler
Use the package or installation method recommended for your Linux distribution. The scheduler’s unit name and log location depend on whether Certbot came from a distribution package, a snap package, or another supported method.
Inspect both scheduler families before creating anything:
sudo grep -R "certbot renew" /etc/crontab /etc/cron.* 2>/dev/null
systemctl list-timers --all | grep -i certbotThe first command searches the system crontab and periodic cron directories. The second lists systemd timers, including inactive ones. A packaged installation may use a timer whose name is not identical to the package name, so do not assume a particular unit exists.
If either command reveals an existing renewal job, keep that job and do not add another. To understand a timer that you found, inspect its associated service and recent execution state:
Recommended Free Tools
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
systemctl list-timers --all | grep -i certbot
systemctl status certbot.timer certbot.service 2>/dev/null
systemctl status snap.certbot.renew.timer snap.certbot.renew.service 2>/dev/nullSome of the units in the second command may not exist; the error is harmless. Use the unit name actually shown by systemctl list-timers. A cron installation may have no systemd timer at all.
2. Verify certificates and renewal files
List the certificates Certbot knows about and inspect its managed directories:
sudo certbot certificates
sudo ls -la /etc/letsencrypt/live/
sudo ls -la /etc/letsencrypt/renewal/certbot certificates shows each certificate name, covered domains, expiry date, and the certificate and key paths. The files in /etc/letsencrypt/live/ are normally symbolic links to the current version in the archive. Keep your web server pointed at fullchain.pem and privkey.pem in the live directory so a renewal changes the target without requiring you to rewrite the server configuration.
Each managed certificate normally has a matching configuration file in /etc/letsencrypt/renewal/. Check ownership and permissions, but do not make private keys world-readable. A compromised private key is equivalent to a compromised certificate identity; use the permissions supplied by your package and service rather than broadening access for convenience.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →3. Test the complete renewal path with a staging dry run
Run the exact command that unattended renewal will use, with the staging test option:
sudo certbot renew --dry-runThe dry run uses the Let’s Encrypt staging service by default. It exercises certificate discovery, the configured authenticator, challenge validation, and Certbot’s renewal processing without replacing your production certificate. A successful dry run is the essential precondition for relying on automation.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Read the complete output. A command that ends without an obvious fatal error is not enough if a certificate was skipped or a hook failed. Resolve every challenge, DNS, permission, firewall, and service-reload error reported by the test, then run the dry run again.
Do not use --force-renewal as a daily or hourly scheduler. Forced requests bypass the normal renewal-window check and can run into the certificate authority’s rate limits. The regular renew action is deliberately idempotent: repeated runs normally do nothing until renewal is appropriate.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute4. Add a scheduler only when none exists
If your package installed neither a cron entry nor a systemd timer, create one reliable schedule. The documented cron pattern runs twice per day and adds a random delay so many machines do not contact the certificate authority at exactly the same second:
SLEEPTIME=$(awk 'BEGIN{srand(); print int(rand()*(3600+1))}')
echo "0 0,12 * * * root sleep $SLEEPTIME && certbot renew -q" | sudo tee -a /etc/crontab >/dev/nullThis writes a root-owned system crontab entry that runs at midnight and noon, then sleeps for a random number of seconds from zero through 3,600 before invoking Certbot quietly. If you use a per-user crontab instead, omit the root field and call Certbot through an appropriate privileged mechanism; a certificate renewal generally needs root access.
Certbot’s current documented renewal decision is based on the remaining proportion of the certificate lifetime: certificates with less than one third of their lifetime left are eligible. For certificates whose lifetime is 10 days or less, the threshold is one half of the lifetime. Because the command checks this condition each time, twice-daily execution does not issue a new certificate twice daily.
Prefer the distribution’s native systemd timer when one is supplied. Do not run both the timer and the cron entry. If you write a custom systemd unit, include a service that runs certbot renew -q, a timer with two daily activations, and a randomized delay; otherwise use the package’s existing unit so updates continue to manage it.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Cron and systemd: what to choose
| Characteristic | Cron | systemd timer |
|---|---|---|
| How you find it | Search /etc/crontab and /etc/cron.*. |
Run systemctl list-timers --all. |
| Typical command | certbot renew -q, often twice daily with a random sleep. |
A service unit invokes certbot renew; the timer controls when. |
| Logs | System cron logging varies by distribution; Certbot logs are also under its log directory. | Use journalctl for the timer’s service unit. |
| Best practice | Use only when no packaged timer exists. | Use the timer supplied by the Certbot package when available. |
5. Point the service at stable certificate paths
Configure the daemon that terminates TLS to use the live-directory paths. An nginx server block typically contains:
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;Replace example.com with the certificate name used on your VPS. Apache uses equivalent certificate and private-key directives in its SSL virtual host. The important detail is not the directive spelling but that the service reads the stable live paths and can access the private key.
When the nginx or Apache Certbot plugin performed the original setup, Certbot can arrange the appropriate reload after a successful renewal. Verify this with a dry run rather than assuming it is present, especially if you later changed the virtual-host configuration or moved the service.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallReload a non-web daemon with a deploy hook
Mail, directory, proxy, and application daemons usually do not receive an automatic reload from a web-server plugin. Put an executable deploy hook in Certbot’s deploy-hook directory; Certbot runs files there only after a certificate has actually renewed:
sudo install -d -m 755 /etc/letsencrypt/renewal-hooks/deploy
sudo tee /etc/letsencrypt/renewal-hooks/deploy/reload-service.sh >/dev/null <<'EOF'
#!/bin/sh
SERVICE=postfix
systemctl reload "$SERVICE"
EOF
sudo chmod 755 /etc/letsencrypt/renewal-hooks/deploy/reload-service.shSet the SERVICE value to the daemon that consumes the certificate, such as postfix, dovecot, or slapd. Use the daemon’s documented reload action; some programs require a graceful reload command rather than a full restart. Keep the hook short, executable, and free of interactive prompts, because it runs unattended as root.
After creating or changing a hook, run sudo certbot renew --dry-run. Confirm that the hook is called and that the service accepts the resulting configuration. A successful certificate challenge with a failed reload is still an operational outage: the old certificate remains in memory until the daemon reloads.
6. Choose and maintain the validation method
HTTP-01 through a web server
HTTP-01 places a temporary challenge under the requested hostname and requires the certificate authority to fetch it over port 80. Check that the DNS A and AAAA records reach this VPS, that firewalls and cloud security groups allow inbound port 80, and that redirects or proxy rules do not prevent the challenge path from being served.
If a reverse proxy or CDN sits in front of the VPS, ensure it forwards the challenge request correctly. A site that works over HTTPS can still fail renewal when port 80 is blocked or when the proxy sends the request to the wrong backend.
Webroot authentication
The webroot method writes a challenge file into a directory already served by your web server. The configured webroot must match the virtual host for every renewed domain, and the web-server user must be able to read the generated file. Check filesystem permissions and any location rule that denies access to the challenge directory.
DNS-01 authentication
DNS-01 proves control by creating a special TXT record. It is useful for wildcard certificates and hosts that cannot expose port 80, but the renewal process needs credentials with permission to update DNS and must allow for provider propagation. Store API credentials with restrictive permissions and test that the plugin can create and remove records without human interaction.
7. Monitor scheduled runs and logs
Check the active timer and recent service output periodically, especially after package upgrades or firewall changes:
systemctl list-timers --all | grep -i certbot
sudo journalctl -u snap.certbot.renew.service --since "7 days ago"
sudo certbot renew --dry-runThe unit in the journalctl example is common for snap installations, but a non-snap package can use a different service name. Discover the actual name with systemctl list-timers --all and inspect that unit instead of copying a guessed name.
Certbot also keeps its own logs under /var/log/letsencrypt/ on typical installations. Look for the first challenge or hook error, not only the final summary. Record the certificate name, hostname, authenticator, and the exact time of failure so DNS or hosting changes can be correlated with the log.
Useful operational checks
- Confirm the certificate’s expiry with
sudo certbot certificatesand, when needed, with the public endpoint using your normal TLS inspection tool. - Verify the service is listening on the expected TLS port and loading the live-directory files.
- Check disk space and inode availability; Certbot needs to create temporary files and new archive versions.
- After a distribution or web-server upgrade, rerun the dry run and inspect whether the scheduler and deploy hooks still exist.
Common failures and precise fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| HTTP-01 challenge cannot be fetched | Port 80 blocked, DNS points elsewhere, or a proxy routes the challenge incorrectly. | Verify A/AAAA records, firewall and security-group rules, port-80 virtual-host routing, and access to the challenge path. |
| DNS-01 challenge times out or finds the wrong TXT record | Insufficient DNS API permissions or propagation delay. | Use a narrowly scoped API credential, confirm the plugin’s zone, wait for propagation, and rerun the dry run. |
| Permission denied in the webroot | The web-server account cannot read the generated challenge file or directory. | Correct ownership, mode, ACL, or the configured webroot; do not make the entire certificate directory publicly readable. |
| Renewal succeeds but clients see the old certificate | The daemon was not reloaded, or it reads a different certificate path. | Check the live-path directives, run the daemon’s configuration test, execute the appropriate reload, and verify the public endpoint again. |
| Timer appears active but no renewal occurs | Certificates are outside the renewal window, or the timer invokes a different Certbot installation. | Review the service output and run sudo certbot renew --dry-run; remove competing installations and schedulers only after identifying which one owns the certificates. |
| Dry run fails after manual renewal-file edits | An invalid option, authenticator, path, or credential reference in /etc/letsencrypt/renewal/. |
Restore the backup or repair the smallest incorrect setting, then repeat the staging dry run before touching production certificates. |
| Repeated forced renewals trigger rate-limit errors | --force-renewal was used instead of the normal renewal-window logic. |
Stop forced jobs, wait for the applicable limit to clear, and schedule only certbot renew. |
Security and maintenance practices
- Keep private keys protected and limit shell access to administrators who need it.
- Use DNS API credentials with the minimum zone permissions required for the selected authenticator.
- Back up
/etc/letsencrypt/securely, including renewal configuration and account data, but never publish the archive or private keys. - Keep only one authoritative Certbot installation and one scheduler for a given certificate set.
- After changing domains, virtual hosts, DNS, firewalls, or service units, run a staging dry run immediately.
- Use a deploy hook for every daemon that caches certificates in memory; updating files alone does not update a running process.
Completion checklist
sudo certbot certificateslists every hostname that should renew./etc/letsencrypt/live/contains the paths referenced by your TLS service.- Exactly one working cron entry or systemd timer invokes
certbot renew. sudo certbot renew --dry-runcompletes without challenge, permission, DNS, or hook errors.- nginx, Apache, or your other daemon reloads successfully after a real renewal.
- Timer status and logs are visible to the administrators responsible for the VPS.
Once these checks pass, unattended renewal is a repeatable maintenance task rather than an emergency performed on the certificate’s expiry day.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
